VeriRoute Intel API

API keyHTTPSPhone

Open documentation ↗

Overview

CNAM caller ID, carrier/LRN lookup and spam scoring for North American phone numbers

VeriRoute Intel is a phone API. Requests are authenticated with an API key. It is served over HTTPS.

At a glance

Authentication: API key
HTTPS: Yes
CORS: Unknown
Category: Phone

Questions

Does the VeriRoute Intel API need an API key?

Yes. The VeriRoute Intel API uses API key authentication; the documentation explains how to get credentials.

Does the VeriRoute Intel API support HTTPS?

Yes, the VeriRoute Intel API is served over HTTPS.

What are alternatives to the VeriRoute Intel 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