How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

SendPulse Tags API

Endpoints related to Tags.

SendPulse Tags API is one of 85 APIs that SendPulse publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Tags. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 8 operations across 6 paths, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 9 base URLs: https://api.sendpulse.com, https://api.sendpulse.com/edu/public/v1, https://api.sendpulse.com/messenger, https://api.sendpulse.com/instagram, https://api.sendpulse.com/live-chat, https://api.sendpulse.com/telegram, https://api.sendpulse.com/tiktok, https://api.sendpulse.com/viber/chatbots, https://api.sendpulse.com/whatsapp.

8 operations 6 paths 15 schemas 1 DELETE1 GET5 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.sendpulse.com
Authentication
HTTP Bearer, OAuth 2.0, OAuth 2.0
Resource Areas
1

Authentication & Security 3

SendPulse Tags API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (API Key) (apiKey). It supports OAuth 2.0 (oauth2) using the clientCredentials flow. It supports OAuth 2.0 (outh2) 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.
  • oauth2 — OAuth 2.0 Client Credentials flow for temporary access tokens.
  • outh2 — OAuth 2.0 Client Credentials flow for temporary access tokens.

Paths & Operations 8

Across 6 paths, the API surfaces 8 operations — 1 DELETE, 1 GET, 5 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Tags 8

Endpoints related to Tags.

GET
/tags
Get a list of tags
getTags → 200401403
POST
/tags
Create a tag
createTag body → 200401403
PUT
/tags/{id}
Update a tag
updateTag 1 param body → 200401403
DELETE
/tags/{id}
Delete a tag
deleteTag 1 param → 200401403
POST
/tags/pin/email
Assign tag to email
pinTagToEmail body → 200401403
POST
/tags/pin/phone
Assign tag to phone
pinTagToPhone body → 200401403
POST
/tags/unpin/email
Unassign tag from email
unpinTagFromEmail body → 200401403
POST
/tags/unpin/phone
Unassign tag from phone
unpinTagFromPhone body → 200401403

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are TagQueueResponse (8 properties), Tag_2 (6 properties), Tag_6 (4 properties), Tag_5 (4 properties). Each schema is shown below with its type and property counts.

TagPinUnpinPhoneRequest
object
2 properties 2 required
Tag
object
3 properties
TagQueueResponse
object
8 properties
TagUpdateRequest
object
2 properties 2 required
TagListResponse
object
3 properties
TagCreateRequest
object
2 properties 2 required
TagPinUnpinEmailRequest
object
2 properties 2 required
Tag_2
object
6 properties
Tag_3
object
4 properties
Tag_4
object
4 properties
Tag_5
object
4 properties
Tag_6
object
4 properties
Tag_7
object
4 properties
Tag_8
object
4 properties
Tag_9
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sendpulse-tags-api-openapi.yml Raw ↑

Other APIs SendPulse publishes across the network.

SendPulse Account API
SendPulse Attachments API
SendPulse Automation Flows API
SendPulse Balance API
SendPulse Blacklist API
SendPulse Board attributes API
SendPulse Bots API
SendPulse Bounces API
SendPulse Campaigns API
SendPulse Chats API
SendPulse Checklist Items API
SendPulse Company API
Where this information came from

This is an independent, third-party profile of SendPulse Tags 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.