Exact Online REST API URL Builder for Accounts, Items, Orders and Invoices
The Exact Online REST API follows an OData style pattern: a regional host, a division number, a service and entity name, and query options such as $select and $filter. This builder assembles those parts so you can test requests in a REST client before writing integration code.
Fill in
Comma separated property names of the entity.
Use single quotes for text values.
Exact returns a page at a time and a __next link for more.
Step 1: find your current division
GET https://start.exactonline.nl/api/v1/current/Me?$select=CurrentDivision Authorization: Bearer YOUR_ACCESS_TOKEN Accept: application/json
Step 2: query the entity
GET https://start.exactonline.nl/api/v1/1234567/crm/Accounts?$select=ID,Code,Name,City,Country&$filter=Country eq 'NL'&$top=60 Authorization: Bearer YOUR_ACCESS_TOKEN Accept: application/json
Step 3: follow paging
# The response contains d.results and, when more rows exist, d.__next. # Call the __next URL as is, with the same Authorization header. # For large exports use the bulk or sync services instead of paging the standard endpoint.
Verify property names against the Exact Online REST API reference for your entity and your app registration scopes. Access tokens expire after a short period and must be refreshed with the refresh token; Exact also applies daily and per-minute API limits per company, so cache results and avoid polling.
Connect Exact Online to a private AI layer
Optional: talk to us about read-only connectors for natural language questions over your Exact data.
Optional. The tool and every export work without this. No spam.
How to use the generator
Select the regional host that matches your Exact Online environment, enter your division number, pick an entity and adjust the select, filter and top fields. The output shows two calls: the first retrieves your current division from the Me endpoint, the second queries the entity. Paste either into Postman, curl or your integration tool, replace the token placeholder and send. Once the shape is right, move the call into your Power Automate flow, middleware or script.
URL anatomy
A typical URL has the form host, /api/v1/, the division, the service folder, then the entity. The service folder groups entities, for example crm for Accounts, logistics for Items, salesorder for SalesOrders and salesinvoice for SalesInvoices. Query options follow after a question mark. $select keeps the payload small, $filter narrows rows on the server, and $top controls the page size. Property names are case sensitive.
- Use $select every time to reduce payload and rate limit pressure.
- Quote text values with single quotes in $filter.
- Dates and GUIDs have their own literal syntax in filters; check the reference.
- Prefer the sync and bulk services for full loads.
Authentication and limits
Exact Online uses OAuth 2.0. You register an app in the Exact App Center, obtain an authorization code, exchange it for an access token and a refresh token, and refresh before the access token expires. Because refresh tokens rotate, the integration must store the newest one safely. The platform also limits requests per company per day and per minute, so design the integration to batch, cache and back off on a rate limit response.
Common mistakes
The most frequent problem is querying the wrong division, which returns empty or unexpected results. Others are using the wrong regional host for the environment, forgetting to follow the paging link, and filtering on a property that is not filterable. If a call returns an authorization error, check that your app has the scopes and that the user has access to the division.
Frequently Asked Questions
What is a division in Exact Online?
A division is an administration or company file inside Exact Online. API URLs include the division number, so one integration can read several companies by switching it. The Me endpoint returns the current division of the authenticated user.
Why do I only get 60 rows back?
Exact returns data in pages. The response carries a next link when more rows exist, and your code must follow it. For complete loads, use the dedicated bulk or sync services, which are designed for large volumes.
Can I write data with the same URL pattern?
Yes, POST, PUT and DELETE are supported on many entities with the same base pattern, but write calls need the correct scopes, a valid JSON body and care with required fields. Test in a copy of the administration first.
Does this tool call the API for me?
No. It only builds the request text in your browser. No token or data is sent anywhere, so you stay in control of credentials. Execute the request in your own client.
Need Exact data available to a private AI or reporting layer? Netray builds read-only connectors and can ground answers in your Exact, Visma or other ERP data on infrastructure you control.
Related Tools
Priority ERP OData REST URL Builder
Build Priority ERP OData URLs with host, tenant, company, entity, $filter, $select, $expand and $top, ready to paste into a REST client.
Country & TaxEuropean E-Invoicing Formats by Country Reference
Which e-invoice format or network applies in each European country, with the syntax behind it, for ERP output planning.
ERP Migration & SelectionERP Localization Gap Register Worksheet
Log each country requirement, how the ERP covers it, the effort in days and the cost, and see the total gap cost at a glance.
Compliance & ContractsGDPR ERP Data Migration Checklist
A practical checklist for handling personal data safely when you migrate to or implement a new ERP in the EU.
More Developer Tools tools
See all- SAP Sales Order ABAP SELECT Generator (VBAK, VBAP, VBFA)
- SAP Sales Order Create BAPI ABAP Generator (BAPI_SALESORDER_CREATEFROMDAT2)
- SAP ABAP Open Items SELECT Generator
- SAP ACDOCA SQL Query Generator
- SAP QM Inspection Lot ABAP SELECT Generator
- SAP Quality Notification Pareto SQL Query Generator
- SAP QM Usage Decision BAPI Skeleton
- ABAP Custom Exception Class Generator
- ABAP Unit Test Class Generator