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

Textmagic Contacts API

Manage contacts in the address book.

Textmagic Contacts API is one of 11 APIs that Textmagic 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 6 operations across 5 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://rest.textmagic.com/api/v2.

6 operations 5 paths 7 schemas 1 DELETE3 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://rest.textmagic.com/api/v2
Authentication
API Key, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

Textmagic Contacts API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-TM-Username (TmUsername). An API key is passed in the header as X-TM-Key (TmKey). By default, every request must be authenticated.

  • TmUsername — Your Textmagic account username.
  • TmKey — Your Textmagic API key, generated in the account settings.

Paths & Operations 6

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

Contacts 6

Manage contacts in the address book.

GET
/contacts
Get all contacts
getContacts 2 params → 200
POST
/contacts/normalized
Add a new contact
createContact body → 201400
GET
/contacts/{id}
Get the details of a specific contact
getContact 1 param → 200404
DELETE
/contacts/{id}
Delete a contact
deleteContact 1 param → 204
PUT
/contacts/{id}/normalized
Edit a contact
updateContact 1 param body → 200
GET
/contacts/search
Find contacts by given criteria
searchContacts 3 params → 200

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Contact (9 properties), ContactRequest (6 properties), ContactListEntity (5 properties), ContactList (4 properties). Each schema is shown below with its type and property counts.

ContactListEntity
object
5 properties
Country
object
2 properties
ResourceLink
object
2 properties
ContactRequest
object
6 properties 2 required
Error
object
3 properties
Contact
object
9 properties
ContactList
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

textmagic-contacts-api-openapi.yml Raw ↑

Other APIs Textmagic publishes across the network.

Textmagic Bulk API
Textmagic Chats API
Textmagic Lists API
Textmagic Messages API
Textmagic Numbers API
Textmagic Replies API
Textmagic Schedules API
Textmagic Sender IDs API
Textmagic Stats API
Textmagic Templates API
Where this information came from

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