sinch-number-lookup-api

Look up E.164 phone number details including carrier, line type, SIM swap, and reassigned-number status.

9|4|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/sinch/skills --skill sinch-number-lookup-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sinch-number-lookup-api
Source: https://github.com/sinch/skills/tree/main/skills/sinch-number-lookup-api
Command: npx skills add https://github.com/sinch/skills --skill sinch-number-lookup-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide per-number intelligence to determine carrier, line type, porting status, SIM swap, VoIP likelihood, and reassigned-number status so teams can prevent fraud, route messages/calls correctly, and improve verification decisions.

Core Features & Use Cases

  • Carrier & Line Type Detection: Identify carrier name, mobile country/network codes, and whether a number is Mobile, Landline, VoIP, or other to choose the correct channel.
  • Risk & Fraud Signals: Detect recent SIM swaps and VoIP likelihood to block or escalate risky verification attempts.
  • Reassigned Number Detection (RND): Check disconnects relative to a contact date to clean lists and avoid sending to reassigned numbers.
  • Use Cases: Fraud checks before verification, pre-send hygiene for marketing lists, routing decisions for voice vs SMS, and enriching contact records.

Quick Start

Request a lookup for +12025550134 including LineType and SimSwap using your chosen SDK or a direct HTTP POST to the lookup endpoint.

Frequently Asked Questions about sinch-number-lookup-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect a recent SIM swap for phone number fraud prevention?

To detect a SIM swap, perform a phone number lookup by sending an HTTP POST request with the SimSwap feature parameter for an E.164 number. The response returns the recent swap status to help block risky verification attempts.

What is reassigned number detection and when do I need it for contact hygiene?

Reassigned number detection checks disconnects relative to a contact date to identify if a number was reassigned. You need it for contact hygiene to clean marketing lists and avoid sending messages to new device owners.

How can I identify carrier and line type to route SMS vs voice calls?

Carrier and line type detection identifies whether an E.164 number is mobile, landline, or VoIP, and returns the carrier name and network codes. You use this intelligence to route SMS or voice calls through the correct channel.

Can I use Node.js or Python SDKs for number lookup, or do I need direct HTTP calls?

You can use either Node.js or Python SDKs for number lookup. For other programming languages, you can make direct HTTP POST calls to the lookup endpoint to retrieve carrier, line type, and fraud detection signals.

Does VoIP detection require explicit parameters in a phone validation request?

VoIP detection requires the explicit VoIPDetection feature parameter in the phone validation request. You must specify this along with the E.164 number to return the VoIP likelihood for fraud checks.

What are the limitations of phone validation for bulk marketing list cleaning?

A key limitation is that this phone validation accepts one E.164 number per request. To clean bulk marketing lists, you must process numbers individually rather than submitting batch lists for carrier detection and contact hygiene.