Pushing via API

Push people and company records to Primer over HTTP with an API key.

Beta — opened on request. Contact [e-mail] to request access.

You can send people and company records to Primer over HTTP — useful for pushing records continuously from your own systems rather than dropping files.

Endpoints

• POST https://primer-platform.api.sayprimer.com/ingest/people

• POST https://primer-platform.api.sayprimer.com/ingest/companies

Authenticate with your API key:

Authorization: Bearer <API key>

Request body

Send JSON — a single record object, an array of records, or an object with a records array. Use the canonical people or company fields; extra fields are accepted and stored. Two optional top-level fields:

• dataset — names the dataset the records belong to (default from_api).

• id_field — which field identifies a record (default id).

Limits

• 600 requests per minute per organization

• 50,000 records per request

• 10 MB maximum request body

Response

On success the endpoint returns 202 Accepted with the number of records accepted:

{ "accepted": 1234 }

Reading your data back out

The ingest endpoints above write records into Primer. To read your Primer data programmatically, Primer also offers a read-only interface over the same account data — audiences and related records — as an MCP server you can connect an MCP client (such as Claude) to.

The MCP server is Beta (gated behind the disco-mcp feature flag) and read-only — it exposes data, it doesn't change anything in Primer. Contact [e-mail] to have it enabled and for connection details.

There's no CSV or file export of an audience's records — you can't download the people or companies in an audience. You put an audience to work by syncing it to a destination, and read your data back through the MCP server above. (A conversion report is a separate, exportable aggregate — that's a report, not the audience's member list.)