1. Verdicts
CallerAPI Documentation
  • Quickstart
  • Use cases
    • For carriers (MNOs/MVNOs)
    • CPaaS platforms
    • Cloud communications providers
    • SIP trunking providers
    • PBX/Cloud PBX
    • UCaaS vendors
  • Account
    • Balance and email
      GET
  • Spam protection
    • Voice firewall
      • Get started
      • Quickstart
        • What you get
        • Before you start
        • Test with a recording
        • Connect your switch
        • Switch notes
        • Twilio and Telnyx
        • Send text instead of audio
      • Verdicts
        • Read a verdict
        • What to do with a verdict
        • Block a caller
        • Events and webhooks
      • Honeypot
        • Hand a call over
        • Audio, events, and limits
      • Reference
        • Endpoints
        • Errors
        • Limits and thresholds
        • Production checklist
      • REST
        • What this deployment can do
        • List the verdict categories
        • List the honeypot personas
        • Score a transcript or a recording
        • List your recent sessions
        • Get one session with verdict and intel
        • Twilio voice URL for a screened number
        • Preview the Twilio TwiML
        • Telnyx voice URL for a screened number
        • Twilio voice URL for a honeypot number
        • Telnyx voice URL for a honeypot number
      • WebSocket
        • Live scam filter stream
        • Honeypot stream
    • Daily spam reports
      • Webhook
        • Subscribe to daily reports
        • Unsubscribe from daily reports
        • List webhook subscriptions
        • Manual dispatch of reports
        • Test webhook
      • REST
        • Fetch daily spam reports
    • 15 days spam CSV snapshot
      GET
    • Spam score + HLR
      GET
  • Mobile SDK
    • Get started
    • Quickstart
      • What you get
      • Get your keys
      • Android
      • iOS
      • Flutter
      • React Native
      • Check it works
    • Call screening
      • What each platform can do
      • Android call screening
      • iOS prerequisites
      • iOS add the extension
      • iOS test on device
    • Reference
      • Methods
      • Errors
      • Limits and billing
      • Troubleshooting
  • Data partners
    • Partner tems & docs
    • Upload spam reports
    • Upload contacts
  • Fraud prevention
    • Ported date
    • Porting history
    • Online presence
    • KYC user identity
  • Schemas
    • Spam protection
      • Spam score request
      • Business info
      • Carrier info
      • Complaint (without number)
      • Daily spam reports request
      • Complaint (with phone)
  1. Verdicts

Block a caller

With report=true the server files the caller as a complaint at the end of the session. That block applies across CallerAPI. Turn it on only after you have watched verdicts on your own traffic. See The first 30 days.

When a number is filed#

All of these must be true:
1.
The final score clears the threshold. The filter files at 0.85 (scam). The honeypot and Score a transcript or a recording file at 0.8.
2.
The category names a fraud. none, Advertising, Surveys, Hang Up, and No Subject Provided are never filed. Other needs a score of 0.85 on every product.
3.
There is at least one number to file: from in E.164 with a leading +, or a callback number the caller gave.
One complaint is filed per number. The numbers are the caller and every callback_number in the intel. The complaint subject is the category. The comment holds the summary and the intel, so an analyst sees why the number is there.
reported and reported_numbers in session.ended tell you what was filed.

What blocking does#

Spam score + HLR returns is_spam: true and reputation: SPAM for the number. A verified business keeps reputation: VERIFIED and still shows the complaint.
The CallerAPI SIP firewall declines the number with 603.
The mobile SDK block lists include it.
The spam reports feed carries it.
A call that is unwanted but not fraud does not block a number.

Where to set it#

PathHow
Plain WebSocketreport=true on the URL or in params of the start message.
Twilio or Telnyx&report=true on the voice URL.
HoneypotDefault true. Set report=false to turn it off.
Scan"report": true in the body, with from.

Dispute a block#

Every filed complaint carries the session_id in its comment. A subscriber or a business that disputes a block gets the transcript and the verdict from Get one session. If the verdict is wrong, contact us with the session_id. We remove the complaint.
Modified at 2026-09-18 16:56:59
Previous
What to do with a verdict
Next
Events and webhooks
Built with