Lately, we have started implementing new API features as separate "microservices". Each such API fulfills a specific purpose.
The motivation behind those separate APIs (and the reason to use them!) might be that:
To explore the available endpoints and their functionality, use Erply API call "getServiceEndpoints". Replace "\<accountnumber>" with your actual Erply account number, a three- to six-digit code. This call, contrary to others, does not require authentication:
curl -X POST -d clientCode=<accountnumber> -d request=getServiceEndpoints https://<accountnumber>.erply.com/api/ | jq .
The response looks as follows:
If you do not have the "jq" tool installed, just omit the vertical bar and everything after that ("| jq .") — you will get a plain, not pretty-printed, JSON response.
Alternatively, to have a quick look, you can also load it in browser:
If you start building an integration that uses these APIs, your integration MUST follow the same procedure at the beginning of every session:
Erply uses many data centers around the world and there are many instances of those services deployed. The returned URLs are specific to your account, and furthermore — can change without prior notice!