# Coevera Developers > Developer documentation for the Coevera CRM API: REST and GraphQL, webhooks, the MCP > server for AI assistants, and the integration platforms. Every page is also served as > Markdown at its URL with `.md` in place of the trailing slash. - Site: https://developers.coevera.com/ (the home page as Markdown: https://developers.coevera.com/index.md) - Publisher: Coevera, https://www.coevera.com - A verified page states how: behaviour (run against a live sandbox) or schema (checked against the specification). - Full text of every page below, in one file: https://developers.coevera.com/llms-full.txt ## Get started - [Quickstart: your first API call](https://developers.coevera.com/get-started/quickstart.md): Create an API application in Coevera, copy its credentials and list your accounts, in REST or GraphQL, with cURL, TypeScript or Python. (behaviour) - [Authentication](https://developers.coevera.com/get-started/authentication.md): Integrations authenticate as an API application, with its user name and password over HTTP Basic. OAuth 2.0 is used only by Coevera's AI connectors. (behaviour) - [Regions and base URLs](https://developers.coevera.com/get-started/regions-and-base-urls.md): Every Coevera space lives in one of four regions. Its base URLs name the region and the space, and the discovery endpoint finds them from the space ID alone. (behaviour) - [Permissions and scopes](https://developers.coevera.com/get-started/permissions-and-scopes.md): What an API application may read and change, on the Records, Administration and Misc tabs; how OAuth scopes map to them; and what a missing permission answers. (schema) - [Plans and limits](https://developers.coevera.com/get-started/plans-and-limits.md): The monthly API call limit of each Coevera plan, page sizes, file sizes and what the API answers when it limits a client. (behaviour) - [REST or GraphQL?](https://developers.coevera.com/get-started/rest-or-graphql.md): The Coevera API has a REST and a GraphQL interface over the same data. How they differ in paths and naming, and which business actions only GraphQL has. (schema) - [Tools and downloads](https://developers.coevera.com/get-started/tools.md): The OpenAPI file, the Postman collection and the GraphQL schema for the Coevera API, your space's own OpenAPI document, and how to use them in Postman and Insomnia. (behaviour) ## Concepts - [Data model](https://developers.coevera.com/concepts/data-model.md): How Coevera records fit together. Entities and their plural paths, owners and sales units, the relation rows that link records, and where your own fields and entities are described. (schema) - [Glossary: UI and API names](https://developers.coevera.com/concepts/glossary.md): The names the Coevera app shows next to the names the API uses, for the entities and fields whose names differ, and why integrations key on API names. (schema) - [Fields and custom fields](https://developers.coevera.com/concepts/fields-and-custom-fields.md): Read an entity's fields and dropdown options from the Fields endpoint, create custom fields, and update dropdown options without deleting the ones you leave out. (schema) - [Custom entities](https://developers.coevera.com/concepts/custom-entities.md): Custom entities have API names that start with CE_. Use them like built-in entities, find their names in the Entities endpoint, and read their fields from your space's own spec. (schema) - [Querying and the query builder](https://developers.coevera.com/concepts/querying.md): Narrow a list with filter and filter-op, order it with order-by, and return only the fields you need with load-only and expand. Build the request below, in REST and GraphQL. (behaviour) - [Pagination](https://developers.coevera.com/concepts/pagination.md): Lists return one page at a time. Ask for up to 100 records with first, then follow page_info.end_cursor with after until has_next_page is false. Cursors must be URL-encoded. (behaviour) - [Dates and time zones](https://developers.coevera.com/concepts/dates-and-time-zones.md): Date and date-time fields, the space REST writes between date and time, and the Timezone header that returns date-times in your own zone. (behaviour) - [Batch operations](https://developers.coevera.com/concepts/batch-operations.md): Create, update, delete or restore many records in one call. By default one invalid item fails the whole batch; with rollback-method=1 a batch can succeed in part. (behaviour) - [Validation](https://developers.coevera.com/concepts/validation.md): Relax server-side validation on a write with the validation-level bit flags. Which bits are public, what each does, and how to add them up. (behaviour) - [Errors](https://developers.coevera.com/concepts/errors.md): Every REST error has the same JSON shape. Branch on the numeric code, not on the message or the HTTP status alone; a missing permission answers 400, not 403. (behaviour) - [Rate limits and retries](https://developers.coevera.com/concepts/rate-limits-and-retries.md): What the API answers when it throttles a client, how to retry with Retry-After and back-off, and where the monthly API call limits of each plan are stated. (schema) ## Recipes - [Recipes overview](https://developers.coevera.com/recipes/overview.md): Every recipe on this site, a complete program for one job, with the time it takes, its APIs and languages, and when it was last verified. (behaviour) - [Create an account with contacts](https://developers.coevera.com/recipes/create-account-with-contacts.md): Create an account, add its contacts in one batch with per-item results, and read them back, in REST or GraphQL, in cURL, TypeScript or Python. (behaviour) - [Create an opportunity](https://developers.coevera.com/recipes/create-opportunity.md): Create an opportunity in the first step of a pipeline, linked to an account and a contact, set a custom field, and read the errors of a refused write, in REST or GraphQL. (behaviour) - [Products and line items](https://developers.coevera.com/recipes/products-and-line-items.md): Create a product category and a product, set its list price, and add it to an opportunity as a line item with a price and a quantity, in REST or GraphQL. (behaviour) - [Attach a document](https://developers.coevera.com/recipes/attach-document.md): Upload a file as base64 and attach it to an account, in two calls through CloudObjects or in one through CloudObjectRelations, in REST or GraphQL. (behaviour) - [Merge duplicates](https://developers.coevera.com/recipes/merge-duplicates.md): Merge a duplicate account into the record you keep, choose the field values that win, and see what happens to the secondary record and its relations, in REST or GraphQL. (behaviour) - [Lead from a web form](https://developers.coevera.com/recipes/lead-from-web-form.md): Turn a form submission into a lead from your own server, with the visitor's details in the quick fields, an owner and a lead source, in REST or GraphQL. (behaviour) - [Two-way contact sync](https://developers.coevera.com/recipes/two-way-contact-sync.md): Push contacts from another system with a webhook skip key, pull every contact changed since the last round, deletions included, and tell people's edits from integration writes. (behaviour) - [Build a webhook receiver](https://developers.coevera.com/recipes/webhook-receiver.md): A webhook receiver in TypeScript or Python that verifies signatures, answers fast, skips duplicates and survives retries, with a self-test and a cURL script to send it deliveries. (behaviour) - [Pipeline report](https://developers.coevera.com/recipes/pipeline-report.md): Read every opportunity in a pipeline with filters, expand and cursor pagination together, and total the value and weighted value per step, in REST or GraphQL. (behaviour) - [Lead lifecycle (GraphQL)](https://developers.coevera.com/recipes/lead-lifecycle.md): Create a lead, qualify it into an opportunity, move the opportunity to the next step and change its owner, with the GraphQL actions that REST does not have. (behaviour) ## Webhooks - [Webhooks overview](https://developers.coevera.com/webhooks/overview.md): Get a signed POST when records change instead of polling. Register a webhook through the API, choose from 138 events, and verify every delivery. (behaviour) - [Webhook events catalogue](https://developers.coevera.com/webhooks/events.md): Every event a webhook can subscribe to, generated from the API's own list: 138 events across 26 entities, with the GraphQL name of each. (schema) - [Filtering and options](https://developers.coevera.com/webhooks/filtering-and-options.md): Narrow and shape what a webhook delivers with its options, from filter and on-field-change to load-only, chunk_size and skip_keys. (behaviour) - [Security and signatures](https://developers.coevera.com/webhooks/security-and-signatures.md): Prove that a delivery came from Coevera and was not changed on the way. Check a signature in your browser, then do the same in your receiver. (schema) - [Delivery and retries](https://developers.coevera.com/webhooks/delivery-and-retries.md): When a delivery counts as delivered, how it is retried for about 24 hours, when a webhook is disabled without notice, and what to answer so it is not. - [Testing locally](https://developers.coevera.com/webhooks/testing-locally.md): Test a webhook receiver on your machine with signed test deliveries, replays of real ones and the signature checker, and use a tunnel for real deliveries. (behaviour) - [API webhooks vs Automatizer webhooks](https://developers.coevera.com/webhooks/api-vs-automatizer-webhooks.md): Coevera has two separate ways to call a URL when something happens. They are set up, signed and retried differently; this is how to choose. (schema) ## AI & MCP - [MCP server and AI connectors](https://developers.coevera.com/ai/overview.md): Let Claude, ChatGPT or another MCP client read and update a Coevera space through the Coevera MCP server, with the user's permissions and consent. - [Activate a connector](https://developers.coevera.com/ai/activation.md): The AI connectors are not self-serve. A space admin requests one in the Automation Hub, and Coevera Customer Success approves and activates it. - [Connect Claude](https://developers.coevera.com/ai/connect-claude.md): Four steps. An admin requests the Claude Connector and Coevera activates it; the user adds the server in Claude, signs in and approves the scopes. - [Connect ChatGPT](https://developers.coevera.com/ai/connect-chatgpt.md): Four steps. An admin requests the ChatGPT Connector and Coevera activates it; the user adds the server in ChatGPT, signs in and approves the scopes. - [Custom MCP connector](https://developers.coevera.com/ai/custom-connector.md): Connect any other MCP client through the MCP Connector tile. Coevera issues the client ID and secret; you add your client's redirect URLs. - [OAuth and scopes](https://developers.coevera.com/ai/oauth-and-scopes.md): How the AI connectors sign in with OAuth 2.0 and PKCE, the 15 scopes the MCP server requires, what each grants, and what OAuth cannot grant. - [Hosting and your data](https://developers.coevera.com/ai/hosting-and-data.md): Where the MCP server runs, where your CRM data stays, which logs it keeps, and the path file uploads and exports take. For IT and security reviews. - [Filters and pagination](https://developers.coevera.com/ai/filters-and-pagination.md): MCP tools filter with their own JSON syntax and page with limit and a cursor, and global_search takes a text. The REST API uses filter and filter-op parameters and first and after. - [Limits and errors](https://developers.coevera.com/ai/limits-and-errors.md): The MCP server's HTTP statuses, tool error codes, rate limits and per-call limits, and where they differ from the REST API. - [MCP changelog](https://developers.coevera.com/ai/mcp-changelog.md): Changes to the Coevera MCP server that clients and agents can see, by server version, newest first. Separate from the API changelog. - [Build agents on the API](https://developers.coevera.com/ai/build-agents-on-the-api.md): When to build your own agent or automation on the REST or GraphQL API instead of the MCP server, and how it authenticates. - [Use these docs with AI](https://developers.coevera.com/ai/use-the-docs-with-ai.md): Every page of this site is also served as plain Markdown, and llms.txt lists them all, so an assistant or a coding agent can read the docs directly. ## Integrations - [Integration platforms](https://developers.coevera.com/integrations/overview.md): Choose between Zapier, the Microsoft Power Platform connector and the Coevera API, by what each covers, how it signs in and where it stops. - [Zapier](https://developers.coevera.com/integrations/zapier.md): The Coevera app on Zapier, with its 16 triggers, 17 actions, 9 searches and 7 search-or-create steps, how it signs in, and where it stops. - [Microsoft Power Platform](https://developers.coevera.com/integrations/power-platform.md): The Coevera connector for Power Automate, Power Apps, Copilot Studio and Logic Apps covers five record types by ID and has no triggers. ## Changelog - [API changelog](https://developers.coevera.com/changelog/api.md): Every change that affects integrations through the REST API, GraphQL and webhooks since release 6.0, newest first, with the breaking changes first and what to do about them. (behaviour) - [Versioning and deprecation](https://developers.coevera.com/changelog/versioning-and-deprecation.md): The API has one version, v100. Changes ship with the monthly release and are announced in its changelog entry; there is no fixed deprecation notice period. (behaviour) ## Support - [Support and status](https://developers.coevera.com/support/support-and-status.md): How to reach Coevera support about the API, what to send so a question can be answered, and how to tell an outage from a problem in your integration. (behaviour) - [Troubleshooting](https://developers.coevera.com/support/troubleshooting.md): The failures integrations meet most often, from 401 and 400 with code 50 to 429, batches with failed items, archived and deleted records, and encoding traps, each with its fix. (behaviour) - [Migrating from Pipeliner](https://developers.coevera.com/support/migrating-from-pipeliner.md): Coevera was formerly Pipeliner CRM. What the rename changes for integrations (hosts, names and documentation) and what keeps working without a change. (behaviour) ## API reference - [API reference index](https://developers.coevera.com/llms-reference.txt): every REST entity and GraphQL repository page, and the OpenAPI, Postman and SDL files - [REST API reference](https://developers.coevera.com/reference/rest.md): Every entity of the Coevera CRM REST API, with its operations, fields and examples in seven languages, grouped into families. - [GraphQL API reference](https://developers.coevera.com/reference/graphql.md): The public GraphQL schema of the Coevera CRM: one page per repository with its queries, mutations and types, including the business actions REST does not have. - [Error codes](https://developers.coevera.com/reference/errors.md): Every error code the Coevera CRM API can return, with its name, HTTP status and description, generated from the API's source for each release.