Fulcrum ERP API: authentication, endpoints and example calls

How to make your first Fulcrum API call

1. 1Ask a Fulcrum admin to confirm API access is enabled for your tenant and to create credentials or a token with the permissions you need.
2. 2Store the token in a secrets manager or environment variable. Never place it in front-end code or a shared spreadsheet.
3. 3Open the Fulcrum developer documentation and find the resource you need (items, sales orders, customers). Note the base URL, version segment and request shape.
4. 4Send a simple read request first, for example a list of items, with the header Authorization: Bearer plus your token and Accept: application/json.
5. 5Page through results using the paging parameters in the docs rather than requesting everything at once.
6. 6Write one record in a sandbox or low-risk area, such as creating a test customer, before automating anything that touches production orders.
7. 7Add retry with backoff for 429 and 5xx responses, and log the request id of every failure.
8. 8Run the integration under a dedicated service user so audit trails show it clearly.

What you can usually do with it

curl -s -X POST 'https://<fulcrum-api-host>/api/items/list' \
  -H 'Authorization: Bearer <TOKEN>' \
  -H 'Content-Type: application/json' \
  -d '{"take": 50, "skip": 0}'

When the API is not enough

Common pitfalls

• !Hard-coding an endpoint version and not checking release notes when Fulcrum updates it.
• !Using a personal login for the integration, which breaks when that person is removed.
• !Pulling all records on every run instead of paging and filtering by modified date.
• !Treating HTTP 200 as proof of success without checking the response body for validation messages.
• !Writing to released orders in ways the UI would block.