Lists and updates

The contacts, leads, lead journey, and activities lists return data, next_page_url, and previous_page_url. Make your initial request without a page parameter, then follow next_page_url verbatim to fetch each subsequent page until next_page_url is null:

curl --fail-with-body \
  --header "Authorization: Bearer $NMC_API_KEY" \
  'https://api.nomissedconversions.com/v1/leads?limit=100'

Load the next page

Keep your query filters and limit unchanged as you follow next_page_url or previous_page_url. Whenever you change a filter or limit, omit page and start again from the first page. Keep in mind that list results reflect live data, so new records can arrive and existing records can be edited while you walk through pages.

The paged lists return results newest first, and the webhook endpoints list returns every endpoint at once:

• Contacts and leads: Sorted by creation time descending, then id descending.
• Activities: Sorted by occurrence time descending, then id descending.
• Webhook endpoints: One unpaged data list, sorted by creation time ascending (oldest first), then id ascending.

See the API reference for lead journey ordering and each endpoint’s available filter parameters.

Check for updates

Endpoints that support updated_since return records updated at or after that timestamp. When polling for changes:

1. Start each check slightly before your previous check finished so concurrent writes aren’t missed.
2. Fetch every page of results and upsert records by id, replacing your local copy whenever the same record appears again.
3. Save your new checkpoint timestamp only after all pages in the run have succeeded.

updated_since only tracks changes to that resource’s own public fields. For instance, an activity can be updated (such as when a call finishes or a transcript becomes ready) without updating its lead’s or contact’s timestamp. Poll every resource type your integration depends on, or subscribe to webhook events instead.

If you use webhooks to keep a local database in sync, you can fetch the record from the API when an event arrives so a delayed or out-of-order webhook never overwrites newer data.