Twilio - Notify API

by twilio.com

HTTP BasicHTTPSPhone

Overview

This is the public Twilio REST API.

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

At a glance

Authentication: HTTP Basic
HTTPS: Yes
CORS: Unknown
Category: Phone
Base URL: https://notify.twilio.com
Version: 1.42.0
Endpoints: 15
OpenAPI: Specification ↗
Spec updated: 2023-04-20

Make a first request

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

cURL

curl -X GET "https://notify.twilio.com/v1/Credentials" \
  -H "Accept: application/json" \
  -H "Authorization: Basic BASE64_USER_PASSWORD"

JavaScript

const response = await fetch("https://notify.twilio.com/v1/Credentials", {
  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://notify.twilio.com/v1/Credentials",
    headers={
    "Accept": "application/json",
    "Authorization": "Basic BASE64_USER_PASSWORD",
    },
    timeout=30,
)
print(response.json())

Endpoints

Method	Path	What it does
GET	`/v1/Credentials`	ListCredential
POST	`/v1/Credentials`	CreateCredential
GET	`/v1/Credentials/{Sid}`	FetchCredential
POST	`/v1/Credentials/{Sid}`	UpdateCredential
DELETE	`/v1/Credentials/{Sid}`	DeleteCredential
GET	`/v1/Services`	ListService
POST	`/v1/Services`	CreateService
GET	`/v1/Services/{ServiceSid}/Bindings`	ListBinding
POST	`/v1/Services/{ServiceSid}/Bindings`	CreateBinding
GET	`/v1/Services/{ServiceSid}/Bindings/{Sid}`	FetchBinding
DELETE	`/v1/Services/{ServiceSid}/Bindings/{Sid}`	DeleteBinding
POST	`/v1/Services/{ServiceSid}/Notifications`	CreateNotification
GET	`/v1/Services/{Sid}`	FetchService
POST	`/v1/Services/{Sid}`	UpdateService
DELETE	`/v1/Services/{Sid}`	DeleteService

Questions

Does the Twilio - Notify API need an API key?

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

Does the Twilio - Notify API support HTTPS?

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

How many endpoints does the Twilio - Notify API have?

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

What are alternatives to the Twilio - Notify 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 →

Twilio - Accounts

Phone

This is the public Twilio REST API.

HTTP Basic13 endpoints

ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management

Phone

ETSI GS MEC 010-2 - Part 2: Application lifecycle, rules and requirements management described using OpenAPI.

No auth16 endpoints

Twilio - Api

Phone

This is the public Twilio REST API.

HTTP Basic199 endpoints

Mobility API

Phone

Transit API can be used to obtain time-aggregated data representing moving the people between various spatial points within the Czech Republic. Having A - 'from' and B - 'to' points, the API can return count of people traveling from A to B or people that are from A and traveling to B, etc. The mobility data is based on moving mobile stations in O2 mobile network.

No auth2 endpoints