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 Compliance API

The Compliance API from SendPulse — 2 operation(s) for compliance.

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

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

This API exposes 6 operations across 2 paths. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.sendpulse.com.

6 operations 2 paths 0 schemas 2 DELETE2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 2

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

Paths & Operations 6

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

Compliance 6
POST
/sms/black_list
Add phone numbers to the blacklist
addSmsBlacklist body → 200401403
DELETE
/sms/black_list
Remove a phone number from the blacklist
removeSmsBlacklist body → 200401403
GET
/sms/black_list
Get a list of contacts in the blacklist
getSmsBlacklist → 200401403
GET
/v2/viber-service/phone-exception
Get a list of contacts in the blacklist
getViberBlacklist 2 params → 200401403
POST
/v2/viber-service/phone-exception
Add phone number to the blacklist
addViberBlacklist body → 200401403
DELETE
/v2/viber-service/phone-exception
Remove a phone number from the blacklist
removeViberBlacklist body → 200401403

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sendpulse-compliance-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 Compliance 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.