This page is for MYOB Acumatica consultants
Check all changes in a test environment before taking them live. Make sure all related features still work as expected and that your data is unaffected.
API licences are used to give third-party software access to your MYOB Acumatica site. API licences are assigned to special user accounts, which allow you to limit their access like you would with real users (for example you can restrict an API user to the same data a Warehouse User or Payroll User licence has access to).
There are two API licences in MYOB Acumatica:
- Full User API — A free licence with limited API calls, restricted to a single user
- Full Access API — A paid licence with unlimited API calls across many named users
While the number of calls and users is different, both licences can access the entire MYOB Acumatica system and maintain concurrent logins with a single API user.
When to get a paid licence
For any business critical integrations or if you have more than one integration, we recommend you use the paid Full Access API licence.
The free Full User API licence is only suitable for light integrations used for occasional reporting or testing purposes.
We also recommend you lock down the API licence for each individual integration via role management, to limit access permissions to the third-party developer based on what that specific integration needs via role management).
Comparison between the paid free API licenses
Full User API | Full Access API | |
Cost | Free | Paid |
Calls per day | 1500 | Unlimited |
Named API users | 1 | 100 |
Concurrent logins per user | Subject to reasonable use | Unrestricted |
System access | Full | Full |
API requests
An API request is basically a query to MYOB Acumatica to search, retrieve, update, delete and create new entities in MYOB Acumatica Business. A single HTTP request of any type(POST, PUT, GET, DELETE), regardless of the payload, counts as a request. The following types of actions broadly create an API request:
- POST –to log in and log out of a site
- GET - to search and retrieve entities defined in the endpoint
- PUT – To create new entities or update existing ones
- DELETE – to delete existing entities
API request examples
Retrieving
GET request returns 50 records | This counts as 1 API request |
Your search is specific and only returns single product | This constitutes as 1 request. If you make 200 of such requests, that will amount to 200 requests. |
Updating/creating
Your single PUT request to update/create contains 50 products and it runs 10 times every month | 1 batch x 10 updates/month = 10 requests per month |
6 batches of 100 products (600 products in total) being updated 10 times every month |
6 batches x 10 updates/month = 60 requests |
Deleting
Deleting 40 products. | Since Deletion is per record, this action will result in 40 requests being made. |
Login/logout
Login | 1 API request |
Logout | 1 API request |
Polling (to check if something has changed in system)
Request every minute to see if a record has changed | 1 GET Request x 60minutes x 24 hours = 1440 requests |