The SalenGo API is an interface for accessing your SalenGo account data using HTTPS and JSON.
The API makes it easy to create web and desktop applications that integrate with your account.
Some potential application ideas:
- Billing for your application or service
- Custom import tools (SalesForce, Gmail, CSV, etc.)
- Revenue analysis
What’s an API and What is it for?
API (Application Programming Interface) is a way for third party developers to integrate the SalenGo functionalities into other applications, allowing them to send invoices without the need to visit the SalenGo website.
SalenGo API uses an aproach based on RESTful and accepts JSON as request format.
As an example, let’s say you have an online store, and need to invoice your clients after each successful purchase, normally you had to develop all the code to manage the creation and sending of the invoice (with all the underlying logic, ex:managing clients, products, taxes, invoice numbering…), using our API you just need to include in your application a little piece of code responsible to make a JSON request and calling an URL using HTML GET.
How can I start?
- If you don’t have any account on your platform, register for one (you can try it for free)
- Get your unique access token key under My Account / API
- Start integrating the API Calls into your application
- Start sending invoices from your app
API Service URL
The SalenGo API has a single point of entry:
Please note the use of https:// in the URL above.
All SalenGo API communication is encrypted over HTTPS. Any non-secure requests are automatically rejected, so we recommend establishing a test connection with the secure API entry point before sending sensitive data.
By default, all accounts have a request limit of 5000 API requests per day.
Additionally, a maximum of 100 results will be returned for list methods, regardless of the value sent with the per_page parameter.
If you wish to to change these values, please contact our helpdesk support.
- All SalenGo API requests are composed of light-weight JSON delivered as an HTTP POST request to the endpoint URL.
- All JSON should be UTF-8 encoded.
- Date and time values are of the form YYYY-MM-DD HH:MM:SS.
- Booleans are either 1 (true) or 0 (false).
- Fields denoting percentages are passed as whole values, not decimals (e.g. 5 for five percent).
All responses are wrapped in a top-level response element. The status attribute will let you know whether the request succeeded or failed.
- Successful response
- Unsuccessful response
- In the case of a failure response, the response body will contain one or more error messages.