> For the complete documentation index, see [llms.txt](https://support.sayprimer.com/primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.sayprimer.com/primer/primer-support-review/section-connections/datasets/pushing-via-api.md). # Pushing via API Push people and company records to Primer over HTTP with an API key. > **Beta** — opened on request. Contact 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 ``` ## 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](/primer/primer-support-review/section-connections/datasets/importing-a-csv.md); 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: ```json { "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 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](/primer/primer-support-review/section-connections/integrations/connecting-a-destination.md), 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.) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://support.sayprimer.com/primer/primer-support-review/section-connections/datasets/pushing-via-api.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.