Business Caller ID tells a terminating switch whether the calling number is presented by the business that registered it. You ask at INVITE, before the phone rings. The answer is proof. It is not a reputation score.A lookup keyed on the number returns the same name to a spoofer as it does to the owner. This check does not. The owner announces each call with a publish token. A spoofer cannot mint that announcement.The business pays 2 credits for each announcement. Verify is free for the telco. When the verdict is verified, the telco receives 1 credit. Do not put a business API key on the switch.Falcon verifies this by default when a CallerAPI key is set. If the switch can inject headers, Falcon sets X-Falcon-BCID, X-Falcon-BCID-Name, and Remote-Party-ID.Pick your path#
Path 1: verify inbound calls#
Your switch sends the calling number and the called number. You get a verdict and a recommended action.Path 2: announce outbound calls#
Your dialler announces the call as it dials. Do not put the publish token in a SIP header.What you need#
1.
A CallerAPI account. Register the calling number on the dashboard. It stays waiting until review. 2.
Your API key from that dashboard. Use it in the x-auth header for verify and for logos. Do not put this key on a dialler.
3.
For path 2, a dialler token from the same dashboard. It is shown once. Put it on the system that places the call. Announce costs 2 credits.
What this is not#
Spam score + HLR can return a business name. That is a name on a number. It is not proof that this call came from that business. Modified at 2026-09-21 18:56:17
