Skip to content

Twilio - Messaging API

by twilio.com

HTTP BasicHTTPSPhone
Open documentation ↗

Overview

This is the public Twilio REST API.

Twilio - Messaging is a phone API from twilio.com. Requests are authenticated with HTTP Basic auth. It is served over HTTPS. Its OpenAPI description documents 45 endpoints.

At a glance

Authentication
HTTP Basic
HTTPS
Yes
CORS
Unknown
Category
Phone
Base URL
https://messaging.twilio.com
Version
1.42.0
Endpoints
45
Spec updated
2023-04-20

Make a first request

Replace the placeholders; the documentation says exactly where credentials go.

cURL
curl -X GET "https://messaging.twilio.com/v1/Deactivations" \
  -H "Accept: application/json" \
  -H "Authorization: Basic BASE64_USER_PASSWORD"
JavaScript
const response = await fetch("https://messaging.twilio.com/v1/Deactivations", {
  method: "GET",
  headers: {
    "Accept": "application/json",
    "Authorization": "Basic BASE64_USER_PASSWORD",
  },
});
const data = await response.json();
console.log(data);
Python
import requests

response = requests.request(
    "GET",
    "https://messaging.twilio.com/v1/Deactivations",
    headers={
    "Accept": "application/json",
    "Authorization": "Basic BASE64_USER_PASSWORD",
    },
    timeout=30,
)
print(response.json())

Endpoints

MethodPathWhat it does
GET/v1/DeactivationsFetch a list of all United States numbers that have been deactivated on a specific date.
GET/v1/LinkShortening/Domains/{DomainSid}/CertificateFetchDomainCertV4
POST/v1/LinkShortening/Domains/{DomainSid}/CertificateUpdateDomainCertV4
DELETE/v1/LinkShortening/Domains/{DomainSid}/CertificateDeleteDomainCertV4
GET/v1/LinkShortening/Domains/{DomainSid}/ConfigFetchDomainConfig
POST/v1/LinkShortening/Domains/{DomainSid}/ConfigUpdateDomainConfig
POST/v1/LinkShortening/Domains/{DomainSid}/MessagingServices/{MessagingServiceSid}CreateLinkshorteningMessagingService
DELETE/v1/LinkShortening/Domains/{DomainSid}/MessagingServices/{MessagingServiceSid}DeleteLinkshorteningMessagingService
GET/v1/LinkShortening/MessagingService/{MessagingServiceSid}/DomainConfigFetchDomainConfigMessagingService
GET/v1/ServicesListService
POST/v1/ServicesCreateService
POST/v1/Services/PreregisteredUsa2pCreateExternalCampaign
GET/v1/Services/UsecasesFetchUsecase
GET/v1/Services/{MessagingServiceSid}/Compliance/Usa2pListUsAppToPerson
POST/v1/Services/{MessagingServiceSid}/Compliance/Usa2pCreateUsAppToPerson
GET/v1/Services/{MessagingServiceSid}/Compliance/Usa2p/UsecasesFetchUsAppToPersonUsecase
GET/v1/Services/{MessagingServiceSid}/Compliance/Usa2p/{Sid}FetchUsAppToPerson
DELETE/v1/Services/{MessagingServiceSid}/Compliance/Usa2p/{Sid}DeleteUsAppToPerson
GET/v1/Services/{ServiceSid}/AlphaSendersListAlphaSender
POST/v1/Services/{ServiceSid}/AlphaSendersCreateAlphaSender
GET/v1/Services/{ServiceSid}/AlphaSenders/{Sid}FetchAlphaSender
DELETE/v1/Services/{ServiceSid}/AlphaSenders/{Sid}DeleteAlphaSender
GET/v1/Services/{ServiceSid}/PhoneNumbersListPhoneNumber
POST/v1/Services/{ServiceSid}/PhoneNumbersCreatePhoneNumber
GET/v1/Services/{ServiceSid}/PhoneNumbers/{Sid}FetchPhoneNumber
DELETE/v1/Services/{ServiceSid}/PhoneNumbers/{Sid}DeletePhoneNumber
GET/v1/Services/{ServiceSid}/ShortCodesListShortCode
POST/v1/Services/{ServiceSid}/ShortCodesCreateShortCode
GET/v1/Services/{ServiceSid}/ShortCodes/{Sid}FetchShortCode
DELETE/v1/Services/{ServiceSid}/ShortCodes/{Sid}DeleteShortCode
GET/v1/Services/{Sid}FetchService
POST/v1/Services/{Sid}UpdateService
DELETE/v1/Services/{Sid}DeleteService
GET/v1/Tollfree/VerificationsListTollfreeVerification
POST/v1/Tollfree/VerificationsCreateTollfreeVerification
GET/v1/Tollfree/Verifications/{Sid}FetchTollfreeVerification
POST/v1/Tollfree/Verifications/{Sid}UpdateTollfreeVerification
GET/v1/a2p/BrandRegistrationsListBrandRegistrations
POST/v1/a2p/BrandRegistrationsCreateBrandRegistrations
POST/v1/a2p/BrandRegistrations/{BrandRegistrationSid}/SmsOtpCreateBrandRegistrationOtp
GET/v1/a2p/BrandRegistrations/{BrandSid}/VettingsListBrandVetting
POST/v1/a2p/BrandRegistrations/{BrandSid}/VettingsCreateBrandVetting
GET/v1/a2p/BrandRegistrations/{BrandSid}/Vettings/{BrandVettingSid}FetchBrandVetting
GET/v1/a2p/BrandRegistrations/{Sid}FetchBrandRegistrations
POST/v1/a2p/BrandRegistrations/{Sid}UpdateBrandRegistrations

Questions

Does the Twilio - Messaging API need an API key?

Yes. The Twilio - Messaging API uses HTTP Basic authentication; the documentation explains how to get credentials.

Does the Twilio - Messaging API support HTTPS?

Yes, the Twilio - Messaging API is served over HTTPS.

How many endpoints does the Twilio - Messaging API have?

Its OpenAPI description lists 45 endpoints in version 1.42.0. All of them are shown on this page.

What are alternatives to the Twilio - Messaging API?

Other Phone APIs include Twilio - Accounts, ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management, Twilio - Api, Mobility API, Telnyx API.

Compare alternatives →

Listed from APIs.guru (CC0).