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

SMSAPI Blacklist API

The Blacklist API from SMSAPI — 2 operation(s) for blacklist.

SMSAPI Blacklist API is one of 11 APIs that SMSAPI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 3 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against 2 base URLs: https://api.smsapi.com, https://api.smsapi.eu.

3 operations 2 paths 3 schemas 1 DELETE1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://api.smsapi.com/sms.do
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

SMSAPI Blacklist API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — OAuth 2.0 bearer token generated in the SMSAPI customer panel (API Tokens).

Paths & Operations 3

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

Blacklist 3
GET
/blacklist/phone_numbers
List blacklisted phone numbers.
listBlacklist → 200
POST
/blacklist/phone_numbers
Add a phone number to the blacklist.
addBlacklistNumber body → 201
DELETE
/blacklist/phone_numbers/{phoneNumber}
Remove a phone number from the blacklist.
removeBlacklistNumber 1 param → 204

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are BlacklistCollection (2 properties), BlacklistEntry (2 properties), BlacklistInput (1 property). Each schema is shown below with its type and property counts.

BlacklistEntry
object
2 properties
BlacklistInput
object
1 property 1 required
BlacklistCollection
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

smsapi-blacklist-api-openapi.yml Raw ↑

Other APIs SMSAPI publishes across the network.

SMSAPI 2FA API
SMSAPI Contacts API
SMSAPI HLR API
SMSAPI MMS API
SMSAPI Profile API
SMSAPI Sender Names API
SMSAPI Short URLs API
SMSAPI SMS API
SMSAPI Subusers API
SMSAPI VMS API
Where this information came from

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