SendPulse CRM Public API is one of 19 APIs that SendPulse publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include CRM, Sales, Deals, and Pipelines. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes
191 operations
across 131 paths,
organized into 45 resource areas,
and defines 71 schemas.
It is described by OpenAPI 3.1.2, at version 0.1.0.
Requests are made against a single base URL, https://api.sendpulse.com/crm/v1.
191 operations131 paths71 schemas39 DELETE48 GET66 POST38 PUT
Metadata
The identity and technical contract details declared by the specification.
Specification
OpenAPI 3.1.2
API Version
0.1.0
Base URL
https://api.sendpulse.com/crm/v1
Authentication
HTTP Bearer, OAuth 2.0, OAuth 2.0
Resource Areas
45
Authentication & Security 3
SendPulse CRM Public API declares
3 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (API Key) (apiKey).
It supports OAuth 2.0 (outh2) using the clientCredentials flow.
It supports OAuth 2.0 (oauth2) using the clientCredentials flow.
By default, every request must be authenticated.
apiKey — Static API Key authentication. A long-lived token generated manually in the SendPulse account settings.
Across 131 paths, the API surfaces 191 operations — 39 DELETE, 48 GET, 66 POST, 38 PUT. They span 45 resource areas, including Users, Pipelines, Pipeline Steps, Deals, Deal notes, Deal contacts, Deal Attributes, Deal attribute Value, and 37 more. Each is listed below with its method, path, parameters, and response codes.
Users 1
GET
/users
Get a list of team members
getUsers→ 200
Pipelines 4
POST
/pipelines
Create new pipeline
createPipelinebody→ 201
GET
/pipelines
Get a list of pipelines
getPipelines→ 200
GET
/pipelines/{pipelineId}
Get information about a pipeline by ID
getPipelineById1 param→ 200
PUT
/pipelines/{pipelineId}
Update information about a pipeline by its ID
updatePipeline1 parambody→ 200
Pipeline Steps 4
POST
/pipelines/{pipelineId}/steps
Create a new pipeline step
createPipelineStep1 parambody→ 200
GET
/pipelines/{pipelineId}/steps
Get pipeline steps
getPipelineSteps1 param→ 200
PUT
/pipelines/{pipelineId}/steps/{stepId}
Update a pipeline step
updatePipelineStep2 paramsbody→ 200
DELETE
/pipelines/{pipelineId}/steps/{stepId}
Delete a pipeline step
deletePipelineStep2 params→ 204
Deals 6
POST
/deals/get-list
Get deals list
getDealsListbody→ 200
POST
/deals
Create a new deal
createDealbody→ 200
GET
/deals/{dealId}
Get information about the deal by ID
getDeal1 param→ 200
PUT
/deals/{dealId}
Update information about a deal by its ID
updateDealById1 parambody→ 200
DELETE
/deals/{dealId}
Delete a deal by its ID
deleteDeal1 param→ 204
POST
/deals/{dealId}/change-pipeline
Change the pipeline of a deal by its ID.
changeDealPipeline1 parambody→ 200
Deal notes 4
GET
/deals/{dealId}/comments
Get a list of deal notes
getDealComments1 param→ 200
POST
/deals/{dealId}/comments
Add a note to a deal
addDealComment1 parambody→ 200
PUT
/deals/{dealId}/comments/{commentId}
Update a note to a deal
updateDealComment2 paramsbody→ 200
DELETE
/deals/{dealId}/comments/{commentId}
Remove a note from the deal
deleteDealComment2 params→ 204
Deal contacts 3
GET
/deals/{dealId}/contacts
Get a list of contacts in a deal
getDealContacts1 param→ 200
POST
/deals/{dealId}/contacts/{contactId}
Add a contact to a deal
addContactToDeal2 params→ 201
DELETE
/deals/{dealId}/contacts/{contactId}
Delete a contact from a deal
removeDealContact2 params→ 204
Deal Attributes 4
GET
/pipelines/{pipelineId}/attributes
Get deal attributes list
listPipelineAttributes1 param→ 200
POST
/pipelines/{pipelineId}/attributes
Create a deal attribute
createPipelineAttribute1 parambody→ 200
PUT
/pipelines/{pipelineId}/attributes/{attributeId}
Update a deal attribute
updatePipelineAttribute2 paramsbody→ 200
DELETE
/pipelines/{pipelineId}/attributes/{attributeId}
Delete a deal attribute
deletePipelineAttribute2 params→ 204
Deal attribute Value 4
GET
/deals/{dealId}/attributes
Get deal attribute values by ID
getDealAttributeValues1 param→ 200
POST
/deals/{dealId}/attributes
Add a attribute value to deal by deal ID
addDealAttribute1 parambody→ 200
GET
/deals/attributes/{pipelineId}
List of all deal attribute values by pipeline
listDealAttributesByPipeline1 param→ 200
PUT
/deals/{dealId}/attributes/{attributeId}
Update the deal attribute value
updateDealAttributeValue2 paramsbody→ 200
Deal attributes 1
DELETE
/deals/{dealId}/attributes/{attributeId}
Remove the deal attribute
deleteDealAttribute2 params→ 204
Messengers types 1
GET
/messenger-types
Get a list of messengers
getMessengerTypes→ 200
Payments 6
GET
/payments/all
Get a list of payments by user
getAllPayments→ 200
GET
/payments/deals/{dealId}
Get a list of payments by dealId
getDealPayments→ 200
GET
/payments/contacts/{contactId}
Get a list of payments by contactId
getPaymentsByContactId→ 200
POST
/payments
Create payment
createPaymentbody→ 201
POST
/payments/{paymentId}/approve
Approve manual payment.
approvePayment1 param→ 200
POST
/payments/{paymentId}/cancel
Cancel manual payment
cancelPayment1 param→ 200
Contacts 17
POST
/contacts/get-list
Get contacts list
getContactsListbody→ 200
POST
/contacts/get-list-by-email
Search contacts by email
getContactListByEmailbody→ 200
POST
/contactsdeprecated
(Deprecated). Use POST /contacts/create instead to create a new contact
The contract defines 71 schemas that model the data the API accepts and returns. The most detailed are Tasks (29 properties), Deal (22 properties), Contact (19 properties), DealDetailed (19 properties). Each schema is shown below with its type and property counts.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of SendPulse CRM Public API, published by
API Evangelist. We do not operate, host, resell, or
support these APIs, and we are not affiliated with or endorsed by the company unless stated above.
Everything here is built from publicly available information — the company's own site,
developer portal, documentation, public repositories, and the specifications it publishes for public use.
Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's
public API artifacts, scored against a published rubric. They are not certifications,
endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and
you do not need to justify the request. A removed company is recorded as unrated, never scored
zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy → On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.