Getting started
Create an API key, sign requests, and make a first call.
Overview
API documentation
Practical, source-verified guidance for integrating with the Fieldmotion CRM API.
Start with the workflow
The Fieldmotion API is a collection of form-encoded calls under /a/. It uses function-style routes such as Customers_list, not a separate REST resource layer. Begin with authentication, then choose a workflow guide or an endpoint page.
Short polling
Build a recoverable change-polling loop with checkpoints and overlap.
Customer APIs
Search, synchronize, retrieve, create, organize, archive, and delete customers with source-verified endpoint guidance.
What these pages cover
Endpoint pages explain the business purpose, real request and response shapes, authentication and permissions, tenant and deletion scope, important errors, side effects, and behavior that is easy to miss. They also show where CRM1 and CRM2 use a call so that you can compare a live browser request with the documented contract.
Wire contract
For a compact, machine-readable inventory of routes and schemas, use the generated OpenAPI documentation. The pages here provide the workflow and behavioral context that a generated contract cannot.