.DkNUKaKx_ZLAT4m.webp?dpl=dpl_Crv6NFYc4gRVqEEsmHdUK26mPGZB){kind=small}
Connectors / Security and compliance · HTTP Connector
Automate CallerAPI with Tray.ai
Upload spam reports in CallerAPI. Connect CallerAPI to the rest of your security and compliance stack with Tray.ai.
Thanks — someone from our team will be in touch soon.
What can you do with CallerAPI on Tray.ai?
CallerAPI is a spam call protection service that scores phone numbers for spam risk, supplies spam number lists, and checks porting and identity data. Tray.ai connects to CallerAPI through the HTTP Connector, so your workflows can call the CallerAPI API alongside the rest of your stack.
- Get a spam score for each inbound lead's phone number before your CRM assigns it to a rep.
- Get a ported date for a phone number before your fraud team approves an account change.
- Fetch daily spam reports and load them into your data warehouse for the security team.
- Connects through
- HTTP Connector
- Authentication
- An API key in a request header
Set it up
Connect CallerAPI to Tray.ai
Each step uses CallerAPI's own API details, from its documentation.
Step 1
Save CallerAPI's API key
Save the key as a Tray.ai authentication. The HTTP Client puts it in the request header, read from $.auth. The key stays out of the workflow and out of the logs.
Step 2
Import a request from CallerAPI's docs
Add an HTTP Client step and paste a cURL example from CallerAPI's API docs. Tray.ai fills in the method, URL, headers, and query.
Step 3
Start with “Get a spam score”
It's one of 14 documented actions, under Phone numbers. The response comes back as data the next step can map into your other apps.
Step 4
Hand it to an AI agent
Wrap “Get a ported date” and “Get porting history” in workflows, and Tray.ai's Agent Gateway for MCP publishes them as governed tools Claude and other AI agents can call.
What the CallerAPI API covers
4 resources and 14 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Connecting it takes a few clicks: here's how.
Phone numbers
- Get a spam score
- Get a ported date
- Get porting history
- Check online presence
Spam reports
- Fetch daily spam reports
- Download a spam CSV snapshot
- Upload spam reports
Report webhooks
- Subscribe a webhook
- Unsubscribe a webhook
- List webhook subscriptions
- Test a webhook
Voice firewall sessions
- List recent sessions
- Get a session
- Score a call recording
Checked against CallerAPI's own documentation on 2026-10-22
How Tray.ai makes this work
CallerAPI plugs into the whole Tray.ai platform
Intelligent Integration
Integrate and automate across 9,000+ apps, databases, APIs, and services with visual workflows, error handling, and observability.
Learn more →Agent Builder
Build AI agents that read, write, and take action in CallerAPI — with guardrails, audit, and human-in-the-loop.
Learn more →Agent Gateway for MCP
Expose CallerAPI actions as governed MCP tools — observable, rate-limited, authenticated.
Learn more →Tray Helix
Build apps on CallerAPI data with your AI assistant, then deploy, run, and govern them on Tray.ai.
Learn more →More security and compliance apps on Tray.ai
Dedicated connectors and other apps Tray.ai reaches in the same category. See every security and compliance connector →
Frequently asked questions
What can a Tray.ai workflow do in CallerAPI?
+
The CallerAPI API documents 14 actions across 4 resources (Phone numbers, Spam reports, Report webhooks, Voice firewall sessions). For example: Get a spam score; Fetch daily spam reports; Subscribe a webhook. A workflow can make any documented call through the HTTP Connector.
How does Tray.ai authenticate with CallerAPI?
+
The CallerAPI API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.
See CallerAPI working against your stack.
We'll walk through a tailored demo with your systems plugged in.
Thanks — someone from our team will be in touch soon.