Aimsio API (1.0.0)
Aimsio provides a set of API endpoints and supported actions to facilitate communication with external software platforms / ERPs.
Each Aimsio account can access two server options: sandbox
and portal
sandbox
is the test environment we used to implement and test configuration changes for an account before live deployment.portal
is the live environment where accounts store their live transactions
Our API utilizes basic username and password authentication to access the API.
If you already have an Admin username set up for your account inside Aimsio, this can be used for API authentication. However, the best practice would be to set up a separate user for integration purposes and keep this set of credentials private only to the developer.
Aimsio users also require specific permissions to access our API. Please contact our support/integration team so they can enable the required permissions.
We currently limit API calls after calls exceed more than 10 calls per second. If our API receives too many requests (ie: if the queue takes longer than 5 seconds to return the call), the request will timeout.
Up to 10 parallel calls are permitted. We do not limit the number of sequential calls. If your organization requires more headroom to complete calls to our API, please get in touch with us.
For most entities with GET requests supported, there are two endpoints we supported:
GET all objects of that type
GET one speficic object based on its unique identifier (GUID/Id)
When you send a GET all request, the system will return an JSON array, and each JSON contains the following properties:
dtype
: The object typeguid/id
: Unique identifier of the object, generated by the Aimsio systemupdatedAt
: Object's last update timestamp in epoch millseconds
Using the returned Guid or ID, you can then query each specific object from the GET single request.
To upload data, please review the object properties and example requests for each POST endpoint.
For our Master Data
endpoints, you can create/edit new entries into Aimsio system.
For some other endpoints like Invoice
or Timecard
, we don't allow POSTing new entries, but updating status of existing entries are supported.
Object types like NRBs or Crew/Equipment records are included in the JobOrder
GET response, but have to be POSTed through their own endpoints.
Crew records:
Employee
endpointEquipment records:
Equipment
endpointNRB records:
NRB
endpoint
https://api.aimsio.com/_mock/aimsio_api/
https://sandbox.aimsio.com/
https://portal.aimsio.com/