.png)
Updated November 4, 2026. First published July 30, 2024. Checked against the public AIMS360 API documentation and the AIMS360 open API page.
What is the AIMS360 open API?
An API (application programming interface) is a published set of requests one program can send another. Your Shopify store, a 3PL's warehouse system or a script your developer writes can ask AIMS360 for data, or send data in, without anyone exporting a spreadsheet.
The AIMS360 API is a RESTful web service. Requests carry a JSON body or query string parameters, and responses come back as JSON. It is documented publicly as a Postman collection at api.aims360.io, titled AIMS360 Fashion ERP API, and the documentation links to a downloadable OpenAPI document. A developer can generate typed code from that file instead of writing every call by hand.
It is not read-only. An integration can place an order, update a customer or record a shipment, within the permissions of the AIMS360 login it signs in as.
The API is also what several AIMS360 products run on: Live Excel workbooks, the Claude, ChatGPT and Grok connections, the Shopify connection, the 3PL exchange and the QuickBooks sync each have their own endpoint groups. See the AIMS360 open API page for the full module list and the authentication details.
What can you connect through the AIMS360 API?
Start from the job you want done, then find the module. These are the common requests from apparel and consumer brands and their developers. Module names come from the public collection; endpoint counts change as the API grows, so plan around the modules, not the numbers.
| What you want to do | API modules involved | Typical direction |
|---|---|---|
| Send web, marketplace or portal orders into AIMS360 | Orders, Customers, References | Into AIMS360 |
| Publish available stock to a store, marketplace or portal | Inventory management, Styles | Out of AIMS360 |
| Keep a product catalog in sync | Styles, Colors, Price sheets, Codes | Out of AIMS360 |
| Check order status and tracking for a customer portal | Orders, Pick tickets, Shipping integration | Out of AIMS360 |
| Send an order confirmation or invoice as a PDF from your own app | Orders, Invoices (calls added in May 2026) | Out of AIMS360 |
| Track production a factory or decorator is running | WIP (cut tickets, vendor POs, garment dye) | Both ways |
| Run a warehouse dashboard or move stock between bins | WMS, Inventory management | Both ways |
| Exchange orders and shipments with a third-party warehouse | 3PL, Pick tickets | Both ways |
| Process returns from a returns app | RMA, Invoices | Into AIMS360 |
| Feed a BI tool or data warehouse | Reports, Aqua (ExportData) | Out of AIMS360 |
The five uses in the first version of this article, customer data, styles, inventory, orders and order status, all still apply.
Which AIMS360 apps and integrations are already built?
Before anyone writes code, check whether the connection already exists. Built-in integrations are maintained by AIMS360 and set up during implementation, so they cost less to own than a custom build. The integrations directory lists them by category.
| Category | Examples | How it connects |
|---|---|---|
| Shopify and DTC | Shopify and Shopify Plus, Shopify POS, Amazon, Faire | The AIMS360 app on the Shopify App Store; marketplace connections |
| Wholesale platforms | JOOR, NuORDER, Brandboom | Each platform's own API |
| Sales rep ordering | RemoteLink for iPad | AIMS360's own app, installed from Apple's App Store |
| Retailer EDI | 350+ retailers | Built-in EDI, no separate EDI provider |
| 3PL warehouses | 3PL integrations | Order and shipment exchange, including EDI 940 and 945 |
| Accounting | QuickBooks and Xero | Two-way accounting sync |
| AI assistants | Claude, ChatGPT, Grok | MCP servers built on the API |
| Reporting | Power BI, Live Excel | Read-only database access or the API |
How do you get access to the AIMS360 API documentation and keys?
The documentation is public, so a developer can read it before you sign anything. Access to your own data needs a few things set up first, in this order.
- Confirm the API is on your plan
API access depends on your plan. Ask your implementation manager or account team before you scope the build.
- Pick the login the API runs as
Designate one AIMS360 login for API calls. An admin or primary account is the safe choice, because deleting that login stops every report, dashboard and integration running under it.
- Check its email validation and permissions
The login must be email validated, and its module permissions decide what the API can see and change. Short or empty responses are almost always a permissions gap.
- Copy the ID and secret keys
The AIMS360 License screen, opened from your initials at the top right, shows the ID and the primary and secondary secret keys. Only the primary admin, or AIMS360 support, can regenerate a key, because a new key breaks every integration using the old one.
- Request a bearer token
Server-to-server code posts the ID, secret and the login's credentials to the token endpoint and sends the returned bearer token on every call. An app acting for a signed-in person uses the authorization code flow instead.
- Use your regional base URL
AIMS360 runs tenants in East US and West US. The token details call tells you which region your company is on, and the regional URL answers fastest.
- Build against the sandbox first
Test on the sandbox and test environment with a handful of styles and customers, then point the finished integration at the live company.
Should you use the API or direct database access?
AIMS360 also offers read-only ODBC and OLEDB access to a company's own SQL database. The two get confused, and they suit different jobs.
| Open API | Direct database (ODBC or OLEDB) | |
|---|---|---|
| What it is | A REST service with documented requests, responses and permissions | A connection your own tools open to your SQL database |
| Read or write | Both, within the API login's permissions | Read only |
| Credentials | Bearer token from the ID and secret keys | Server name, login and password issued by support |
| When the system changes | Covered by the 90-day deprecation policy | Table structures can change with releases |
| Best for | Integrations, apps and automations others depend on | An analyst pulling tables into a BI tool |
If other people will depend on what you build, use the API. For raw tables in your own BI tool, database access is quicker.
Does AIMS360 integrate with Clover POS?
Not as a built-in integration. As of November 2026 Clover is not on the AIMS360 integrations pages, and there is no Clover connector to switch on. That question comes up often enough here to deserve a straight answer.
There are two practical routes. The first is the one AIMS360 supports out of the box for stores: Shopify POS, where each store is a location tied to its own AIMS360 warehouse and customer account, and register sales import as paid orders. The second is a custom build on the open API. Clover publishes its own Orders API, so a developer can move store sales into AIMS360 orders and push available stock back to Clover's items. Scope that build like any integration: which records move, which way, how often, and who maintains it when either side changes.
The same goes for any system without a listed connector: if it has an API, it can be connected. Whether it should be is a cost and maintenance question.
What should an apparel ERP's API integrations include?
Every ERP vendor says it has an API. These questions separate a usable one from a checkbox, and they apply to AIMS360 too.
| Question to ask | Why it matters | AIMS360 answer |
|---|---|---|
| Is the documentation public? | You can judge it before you buy | Yes, at api.aims360.io |
| Can it write, or only read? | Orders, receipts and returns need to go in | Read and write |
| Does it cover production and warehouse? | Apparel brands live on WIP and bins | WIP, WMS, pick tickets and 3PL modules |
| Is it sized by style, color and size? | Inventory feeds must match the size grid | Inventory is kept at style, color and size |
| Is there a spec file? | Generated code saves weeks | OpenAPI document available |
| What happens when it changes? | Silent changes break integrations | At least 90 days' notice for major removals |
| Is there a test environment? | You should not test on live data | Sandbox and test environment |
| Do the vendor's own products use it? | A strong sign it is maintained | Live Excel, MCP, Shopify, 3PL, QuickBooks |
For a wider comparison, see which apparel ERPs offer an MCP server and how apparel ERPs connect to a 3PL.
What is the AIMS360 Aqua API?
Aqua is the reporting side of the API. Its ExportData endpoint returns AIMS360 data as JSON for business intelligence tools such as Power BI, Tableau, Looker, Domo or Excel, and for moving large histories into your own data warehouse. Aqua views can also run on a schedule.
If the goal is a dashboard rather than an integration, look at Live Excel, Power BI on AIMS360 and the built-in BI tool before writing code. The older Aqua API article covers the reporting use in more depth.
AIMS360 API: frequently asked questions
Yes. AIMS360 has a REST API that accepts and returns JSON. The public documentation at api.aims360.io covers 33 modules and roughly 790 endpoints as of September 2026, including styles, customers, orders, pick tickets, inventory, warehouse, work in process, invoices, returns and reports. An OpenAPI document can be downloaded from the documentation.
At api.aims360.io, published as a Postman collection titled AIMS360 Fashion ERP API. Anyone can read it. Calling the API against your own company needs a designated API login, its ID and secret keys from the AIMS360 License screen, and API access on your plan.
Both. The collection includes GET, POST, PUT, PATCH and DELETE methods, so an integration can create orders, update customers, record receipts and process returns as well as read data. The permissions on the API login set the limit of what it can see and change.
With a bearer token. Server-to-server code posts the ID, the secret key and the API login's credentials to the token endpoint and sends the returned token on every call. An app that acts for a signed-in person uses an authorization code flow and exchanges the code for a token.
Not as a separate store. The AIMS360 app for Shopify is on the Shopify App Store, free to install and listed since January 2016. The RemoteLink order-writing app for sales reps is on Apple's App Store. Other integrations, such as JOOR, NuORDER, EDI retailers, 3PLs and accounting, are set up inside AIMS360 during implementation.
Not as a built-in integration. Clover is not on the AIMS360 integrations pages as of November 2026. Stores can run on Shopify POS, which AIMS360 supports out of the box, or a developer can connect Clover through the AIMS360 open API and Clover's own Orders API as a custom build.
API access depends on your plan. Ask your implementation manager or account team which plan you are on and whether the API is enabled before you scope an integration.
Yes. AIMS360 offers a sandbox and test environment with a copy of your data. Test with a few styles and customers, then connect the finished integration to the live company.
AIMS360 gives at least 90 days' notice before discontinuing or removing major API features, names the API and version affected and, where one exists, points to a replacement. Shorter notice can apply if a security risk or a legal or third-party requirement forces a change. Newer calls carry a date as their version.
To build an integration, yes, or a partner who builds them. Many brands never need one, because Shopify, JOOR, NuORDER, EDI, 3PLs, accounting, Power BI, Live Excel and the AI assistants are already built. Check the integrations directory before you commission custom work.
AIMS360 is not affiliated with Clover, Shopify or Apple; their names are trademarks of their owners. Module and endpoint counts come from the public AIMS360 API documentation as of September 2026 and change as the API grows.
