# Fulcrum ERP API: authentication, endpoints and example calls > Source: https://netray.co/erp-help/fulcrum-erp-api-authentication-endpoints-examples > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer Fulcrum exposes a REST API over HTTPS that returns JSON. You authenticate with a bearer token issued from your Fulcrum account, then call resource endpoints for items (parts), sales orders, customers, jobs and inventory. Build against the current developer documentation Fulcrum publishes, because endpoint names and versions are updated there first. ## Kind how-to ## System job-shop-erp ## Erp Fulcrum (Fulcrum Pro) ## Module Public API / Integrations ## Query fulcrum erp api ## Alternate Queries - fulcrum pro api documentation - fulcrum erp api authentication - fulcrum api sales orders parts - fulcrum erp integration ## Applies To Fulcrum Pro cloud tenants. Access to the API and the token tools depends on your plan and user permissions, so ask your Fulcrum admin or account manager if you do not see the option. ## Steps ### How to make your first Fulcrum API call **Items:** - Ask a Fulcrum admin to confirm API access is enabled for your tenant and to create credentials or a token with the permissions you need. - Store the token in a secrets manager or environment variable. Never place it in front-end code or a shared spreadsheet. - Open the Fulcrum developer documentation and find the resource you need (items, sales orders, customers). Note the base URL, version segment and request shape. - Send a simple read request first, for example a list of items, with the header Authorization: Bearer plus your token and Accept: application/json. - Page through results using the paging parameters in the docs rather than requesting everything at once. - Write one record in a sandbox or low-risk area, such as creating a test customer, before automating anything that touches production orders. - Add retry with backoff for 429 and 5xx responses, and log the request id of every failure. - Run the integration under a dedicated service user so audit trails show it clearly. ## Sections ### Authentication and permissions **Body:** Fulcrum uses token-based authentication. The token represents a user or an integration, and what it can read or write follows the permissions of that identity. Create a dedicated integration identity rather than borrowing a person's login, because people leave and their tokens go with them. Always call over HTTPS and treat the token like a password. Rotate it on a schedule and when anyone with access leaves. ### What you can usually do with it **Body:** Typical integrations are pulling sales orders and jobs into reporting, pushing orders from a web store or customer portal, syncing parts and customers with a CRM, reading inventory and shipments for a warehouse tool, and feeding quality or traceability data to another system. Check the documentation for which operations exist as read, create, update or delete for each resource. Not every resource supports every verb, and some fields are read-only once an order is released. **Code:** curl -s -X POST 'https:///api/items/list' \ -H 'Authorization: Bearer ' \ -H 'Content-Type: application/json' \ -d '{"take": 50, "skip": 0}' ### Integration patterns that hold up **Body:** - Prefer incremental sync using a last-modified filter when the API offers one, with a full reconciliation once a night. This avoids missing changes if a run fails. - Make writes idempotent. Store your system's reference on the Fulcrum record (an external number field) so a retried request does not create a duplicate sales order. - Keep business rules in one place. If the API creates orders and Fulcrum workflows also act on them, agree which side owns status changes. ### When the API is not enough **Body:** For a one-off bulk load, an import tool or CSV process may be faster and safer than scripting thousands of calls. For analytics, many teams extract data on a schedule into a warehouse rather than querying the live API. If you need natural-language questions over Fulcrum data without sending it to an outside service, an assistant can sit on top of the API or an extract and run on your own hardware. ## 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. ## Ai Angle A grounded assistant can use the Fulcrum API as a read-only data source: it turns a question such as 'which jobs are late for customer X' into the right list calls, shows the request it made, and answers from the returned records. For shops that must keep data inside their own network, the language model runs on local GPUs and only the API token and tenant data cross your boundary under your rules. Write actions, like creating an order, stay behind human approval. ## Faq ### Does Fulcrum have a public API? **Answer:** Yes. Fulcrum publishes a REST-style API with developer documentation, and customers use it for order, item and customer integrations. Availability and limits depend on your plan, so confirm with Fulcrum. ### How do I authenticate to the Fulcrum API? **Answer:** Use a bearer token issued from your tenant, sent in the Authorization header over HTTPS. Create it for a dedicated integration user and store it in a secrets manager. ### Can I create sales orders through the API? **Answer:** Order creation is a common integration use. Check the current documentation for required fields and rules, and test with a non-production customer before automating. ### Are there rate limits? **Answer:** Expect limits on any cloud API. Build retry with exponential backoff for 429 responses and avoid polling every few seconds when a nightly or hourly sync is enough. ## Search terms fulcrum erp api, fulcrum pro api, fulcrum api documentation, fulcrum api authentication, fulcrum sales order api, fulcrum integration, fulcrum erp parts api, job shop erp api --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json