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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Neutrino API

Neutrino API Telephony API

APIs for live telephony

Documentation Provider Profile APIs.io OpenAPI GitHub

Neutrino API Telephony API is one of 7 APIs that Neutrino API publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against 7 base URLs: https://neutrinoapi.net, https://aws.neutrinoapi.net, https://gcp.neutrinoapi.net, https://neutrinoapi.com, https://eu.neutrinoapi.net, https://aus.neutrinoapi.net, https://usa.neutrinoapi.net.

5 operations 5 paths 6 schemas 2 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.7.2
Base URL
https://neutrinoapi.net/
Authentication
API Key, API Key
Contact
Neutrino API
Resource Areas
1

Authentication & Security 2

Neutrino API Telephony API declares 2 security schemes for authenticating requests. An API key is passed in the header as user-id (user-id). An API key is passed in the header as api-key (api-key). By default, every request must be authenticated.

  • user-id — Your user ID
  • api-key — One of your API keys

Paths & Operations 5

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

Telephony 5

APIs for live telephony

POST
/sms-verify
SMS Verify
SMSVerify body → 200400403500default
POST
/phone-playback
Phone Playback
PhonePlayback body → 200400403500default
GET
/hlr-lookup
HLR Lookup
HLRLookup 2 params → 200400403500default
GET
/verify-security-code
Verify Security Code
VerifySecurityCode 2 params → 200400403500default
POST
/phone-verify
Phone Verify
PhoneVerify body → 200400403500default

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are HLRLookupResponse (25 properties), SMSVerifyResponse (3 properties), PhoneVerifyResponse (3 properties), PhonePlaybackResponse (2 properties). Each schema is shown below with its type and property counts.

VerifySecurityCodeResponse
object
Structure of verify-security-code
1 property 1 required
APIError
object
For non-200 responses this contains specific API error details
2 properties 2 required
PhoneVerifyResponse
object
Structure of phone-verify
3 properties 3 required
SMSVerifyResponse
object
Structure of sms-verify
3 properties 3 required
HLRLookupResponse
object
Structure of hlr-lookup
25 properties 25 required
PhonePlaybackResponse
object
Structure of phone-playback
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

neutrino-api-telephony-api-openapi.yml Raw ↑

Other APIs Neutrino API publishes across the network.

Neutrino API Data Tools API
AE Profile APIs.io
Neutrino API E Commerce API
AE Profile APIs.io
Neutrino API Geolocation API
AE Profile APIs.io
Neutrino API Imaging API
AE Profile APIs.io
Neutrino API Security and Networking API
AE Profile APIs.io
Neutrino API WWW API
AE Profile APIs.io
#Telephony
← Back to N APIs
API Details
ID
neutrino-api:neutrino-api-telephony-api
Base URL
https://neutrinoapi.net/
Docs
https://www.neutrinoapi.com/api/
Provider
Neutrino API
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=neutrino-api-telephony-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/neutrino-api-telephony-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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