--- title: Migrating from Pipeliner description: Coevera was formerly Pipeliner CRM. What the rename changes for integrations (hosts, names and documentation) and what keeps working without a change. canonical: https://developers.coevera.com/support/migrating-from-pipeliner/ section: support verification: behaviour lastVerified: 2026-10-15 publisher: Coevera --- # Migrating from Pipeliner **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}.api.coevera.com` | The documented host. Use it. | | `{region}.coevera.com` | Answers the same API. | | `{region}.api.pipelinersales.com` | Former host. Answers the same API. | | `{region}.pipelinersales.com` | 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 1. **The host.** Replace `{region}.api.pipelinersales.com` or `{region}.pipelinersales.com` with `{region}.api.coevera.com`; the region and the rest of the URL stay the same. 2. **Discovery.** The [discovery endpoint](/get-started/regions-and-base-urls/#find-a-spaces-region) answers with URLs on the domain of the host you ask: ask a `pipelinersales.com` host and `region_url` and the endpoints come back on `pipelinersales.com`. Ask a `coevera.com` host. 3. **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 at `https://{region}.api.coevera.com/api/v100/app/space/{space_id}/graphql/public`; see [REST or GraphQL?](/get-started/rest-or-graphql/). 4. **Links to the documentation.** This site replaces developers.pipelinersales.com: | Former page | Now | | --------------------------------- | ----------------------------------------------------------------------------------------------------------------- | | Quick Start | [Quickstart](/get-started/quickstart/) | | About the API | [Regions and base URLs](/get-started/regions-and-base-urls/) | | Authentication | [Authentication](/get-started/authentication/) and [Permissions and scopes](/get-started/permissions-and-scopes/) | | Understanding the CRM Concept | [Data model](/concepts/data-model/) and [Glossary](/concepts/glossary/) | | Fields | [Fields and custom fields](/concepts/fields-and-custom-fields/) | | API parameters | [Querying](/concepts/querying/) and [Validation](/concepts/validation/) | | Dates | [Dates and time zones](/concepts/dates-and-time-zones/) | | Pagination | [Pagination](/concepts/pagination/) | | Bulk create, update, delete | [Batch operations](/concepts/batch-operations/) | | Webhooks | [Webhooks overview](/webhooks/overview/) and the [events catalogue](/webhooks/events/) | | Create Account, Create Contact | [Create an account with contacts](/recipes/create-account-with-contacts/) | | Create Opportunity | [Create an opportunity](/recipes/create-opportunity/) | | Create Product, Product Line Item | [Products and line items](/recipes/products-and-line-items/) | | Create Custom Entity Record | [Custom entities](/concepts/custom-entities/) | | Upload Document | [Attach a document](/recipes/attach-document/) | | Merging Accounts/Contacts | [Merge duplicates](/recipes/merge-duplicates/) | | The REST reference (ReDoc) | [REST API reference](/reference/rest/) and its [downloads](/reference/downloads/) | | The GraphQL reference | [GraphQL reference](/reference/graphql/) | ## 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.5.2`, and `Pipeliner-Wa-Version` | | The OpenAPI document the API serves (`…/openapi.json`) | The title `Pipeliner Cloud API`, and `servers` on `{region}.api.pipelinersales.com` | | URLs of stored files | The host `storage.api.pipelinersales.com` | | Sign-in to the CRM, and the consent screen of the AI connectors | A redirect through `accounts.pipelinersales.com` | | 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](/integrations/power-platform/) | The Zapier app is listed as Coevera; see [Zapier](/integrations/zapier/). ## Limits - Which host spelling stays long term, other than `{region}.api.coevera.com`, has not been announced.