Information
- OpenAPI version:
3.1.2
Overview
NMC customer API 2026-10-01
Section titled “NMC customer API 2026-10-01”Use a business API key to read and update data for one business. NMC checks authentication and business access on every request. All timestamps use RFC 3339 format, and every response includes X-Request-ID, Cache-Control: no-store, and X-Content-Type-Options: nosniff.
Authenticated requests are limited to 120 per minute per business, shared across all API keys for that business. Rate-limit headers report the limit, remaining requests, and reset time, and 429 responses include Retry-After.
The contacts, leads, lead journey, and activities lists use live cursor pagination. Follow next_page_url or previous_page_url without changing filters or limit, and omit page to start from the first page whenever you change filters or limit. /webhook_endpoints returns every endpoint in one response, oldest first. Unknown, repeated, or empty query parameters are rejected. The updated_since filter is inclusive and advances only when a resource’s own public fields change; when polling, overlap your time windows and upsert records by ID.
Writes are safe to retry: Lead and contact updates set target values directly (the latest update wins), form submissions deduplicate by submission ID, and creating a webhook endpoint with a URL the business already has updates and returns that endpoint.
Authentication
Section titled “Authentication”businessAPIKey
Section titled “businessAPIKey”Business API key passed in the Authorization header as Bearer nmc_live_
Security scheme type: http