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

The Contacts API from SMSAPI — 4 operation(s) for contacts.

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

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

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

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

9 operations 4 paths 6 schemas 2 DELETE3 GET2 POST2 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.smsapi.com/sms.do
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

SMSAPI Contacts 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 9

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

Contacts 9
GET
/contacts
List contacts
listContacts 3 params → 200
POST
/contacts
Create a contact
createContact body → 201
GET
/contacts/{contactId}
Get a contact
getContact 1 param → 200
PUT
/contacts/{contactId}
Update a contact
updateContact 1 param body → 200
DELETE
/contacts/{contactId}
Delete a contact
deleteContact 1 param → 204
GET
/contacts/groups
List contact groups
listContactGroups → 200
POST
/contacts/groups
Create a contact group
createContactGroup body → 201
PUT
/contacts/{contactId}/groups/{groupId}
Assign a contact to a group
assignContactToGroup 2 params → 200
DELETE
/contacts/{contactId}/groups/{groupId}
Remove a contact from a group
removeContactFromGroup 2 params → 204

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Contact (7 properties), Group (4 properties), ContactInput (4 properties), GroupInput (2 properties). Each schema is shown below with its type and property counts.

GroupCollection
object
2 properties
Contact
object
7 properties
ContactInput
object
4 properties 1 required
ContactCollection
object
2 properties
GroupInput
object
2 properties 1 required
Group
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

smsapi-contacts-api-openapi.yml Raw ↑

Other APIs SMSAPI publishes across the network.

SMSAPI Blacklist 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
SMSAPI 2 FA API
Where this information came from

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