API introduction
Create a business API key and make your first authenticated request.
The NMC customer API lets your server read a business’s records, update leads
and contacts, submit forms, and manage webhook endpoints so your server can
receive events. All requests use the base URL
https://api.nomissedconversions.com/v1 and authenticate with a business API
key rather than dashboard sign-in tokens.
Create a key
Section titled “Create a key”Anyone with account access can create and manage keys in the business’s Settings → API access (invited clients cannot manage keys):
- Open Settings → API access for the business you want to connect and create a named key.
- Copy the key secret as soon as it appears. NMC shows the secret only once and can’t display it again later.
- Store the key in your server’s secret manager or environment configuration. Never include business API keys in browser code, mobile apps, or source control.
Each key grants full customer API access to one business. Create a separate key for every service or integration so you can revoke one key without disrupting the others.
Make a read request
Section titled “Make a read request”Export NMC_API_KEY in your shell or server environment, then fetch the
business record:
curl --fail-with-body \ --header "Authorization: Bearer $NMC_API_KEY" \ https://api.nomissedconversions.com/v1/businessBefore sending any write requests, check the returned id, name,
website_url, and currency_code to confirm your key points to the business
you expect.
Rotate or remove a key
Section titled “Rotate or remove a key”To replace a key without downtime:
- Create a new key in Settings → API access, deploy it to your server, and confirm a read request succeeds.
- Find the old key, choose Remove, and confirm Remove key.
Once removed, the old key stops working immediately, and any further requests or retries using it will fail.
Build the integration
Section titled “Build the integration”- Limits and errors: Rate limits, request size limits, and HTTP error codes.
- Lists and updates: Cursor pagination and polling
with
updated_since. - Retrying requests: Safely retrying updates, form submissions, and webhook endpoint creation.
- Webhooks: Receiving and verifying real-time event notifications.
- API reference: Complete endpoint, request, and response schemas.