Primemgr for developers: the API, webhooks and AI assistants
Build on a REST API over your workspace, get signed webhooks when things happen, and connect AI assistants over MCP. Included on the Team plan and above.
Updated
Connect Primemgr to the rest of your business. API keys are created in Settings → API keys and are available on the Team plan and above.
The REST API
- JSON over HTTPS at /api/v1, described in full by the OpenAPI document at /api/v1/openapi.json.
- Contacts, sites, assets, quotes, work orders, bookings, invoices, payments, items, services, suppliers, purchase orders, service agreements, time entries, leads and opportunities.
- Authenticate with an API key as a bearer token. A key can only do what its permissions allow, and every request is logged where you can see it.
- Send an Idempotency-Key header with a write, and a retried request is not applied twice.
- Up to 600 requests a minute per key.
Webhooks
Add an endpoint in Settings → Webhooks and choose the events it receives. Each delivery is signed: check the webhook-signature header, an HMAC-SHA256 over the webhook-id, webhook-timestamp and body, and refuse old timestamps so a delivery cannot be replayed. Failed deliveries are retried, with the same webhook-id each time so you can ignore a repeat.
AI assistants (MCP)
An MCP endpoint at /api/mcp lets an AI assistant use the same API with the same key and the same permissions: look up a customer, list open jobs, draft a quote.
Calendar feeds
Each person can subscribe to their own schedule as a private calendar feed in any calendar app.
Importing your data
Bring customers and other records in from a CSV or Excel file in Settings → Data, with a preview before anything is saved and an undo afterwards.