SupportMigrating from Pipeliner
Migrating from Pipeliner
Coevera was formerly Pipeliner CRM. What the rename changes for integrations (hosts, names and documentation) and what keeps working without a change.
Answer
Pipeliner CRM is now Coevera, and the API is the same: same paths, v100, entities, fields and credentials. Use https://{region}.api.coevera.com. The former {region}.api.pipelinersales.com hosts still answer with the same credentials, and no date has been announced for them to stop. Some names still carry the former brand, such as the Pipeliner-Api-Version header.
Coevera was called Pipeliner CRM, and its developer documentation lived at developers.pipelinersales.com. The product and the API kept everything but the name, so an integration built for Pipeliner keeps working; this page lists what to update and where the former name still shows.
What keeps working
The API did not change with the name:
- the same paths and the same version,
/api/v100/…; - the same entities, fields, parameters and error codes;
- the same API applications, user names and passwords;
- every host spelling below, with the same credentials:
| Host | Status |
|---|---|
{region}. |
The documented host. Use it. |
{region}. |
Answers the same API. |
{region}. |
Former host. Answers the same API. |
{region}. |
Former host. Answers the same API. |
No date has been announced for the pipelinersales.com hosts to stop answering. Move to
{region}.api.coevera.com when you next touch the integration's configuration.
What to update
-
The host. Replace
{region}.api.pipelinersales.comor{region}.pipelinersales.comwith{region}.api.coevera.com; the region and the rest of the URL stay the same. -
Discovery. The discovery endpoint answers with URLs on the domain of the host you ask: ask a
pipelinersales.comhost andregion_urland the endpoints come back onpipelinersales.com. Ask acoevera.comhost. -
The GraphQL schema. The former documentation pointed at
crm.pipelinersales.com/api/v100/app/graphql/schema.json, which is the CRM's internal app schema. Integrations use the public schema athttps://{region}.api.coevera.com/api/v100/app/space/{space_id}/graphql/public; see REST or GraphQL?. -
Links to the documentation. This site replaces developers.pipelinersales.com:
Former page Now Quick Start Quickstart About the API Regions and base URLs Authentication Authentication and Permissions and scopes Understanding the CRM Concept Data model and Glossary Fields Fields and custom fields API parameters Querying and Validation Dates Dates and time zones Pagination Pagination Bulk create, update, delete Batch operations Webhooks Webhooks overview and the events catalogue Create Account, Create Contact Create an account with contacts Create Opportunity Create an opportunity Create Product, Product Line Item Products and line items Create Custom Entity Record Custom entities Upload Document Attach a document Merging Accounts/Contacts Merge duplicates The REST reference (ReDoc) REST API reference and its downloads The GraphQL reference GraphQL reference
Where the former name still shows
Integrations meet the former name in a few places. None of them needs a change on your side:
| Where | What you see |
|---|---|
| Response headers | Pipeliner-Api-Version, the API release such as 6., and Pipeliner-Wa-Version |
The OpenAPI document the API serves (…/) |
The title Pipeliner Cloud API, and servers on {region}. |
| URLs of stored files | The host storage. |
| Sign-in to the CRM, and the consent screen of the AI connectors | A redirect through accounts. |
| The API Application dialog in the CRM | The hint under Email: "Email can be used by your Pipeliner applications & processes" |
| Microsoft Power Platform | The connector is listed as Pipeliner CRM (Preview); see Microsoft Power Platform |
The Zapier app is listed as Coevera; see Zapier.
Limits
- Which host spelling stays long term, other than
{region}.api.coevera.com, has not been announced.