# CallerAPI integrations: phone numbers

> Upload spam reports in CallerAPI. Connect CallerAPI to the rest of your security and compliance stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/callerapi-integrations/
**Categories:** Security and compliance
**Connects through:** HTTP Connector

## Overview

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.

## Use cases

### Phone numbers

Read phone numbers in CallerAPI from any Tray.ai workflow. The CallerAPI API covers calls such as get a spam score and get a ported date.

- Get a spam score
- Get a ported date
- Get porting history

### Spam reports

Read and create spam reports in CallerAPI from any Tray.ai workflow. The CallerAPI API covers calls such as fetch daily spam reports and download a spam CSV snapshot.

- Fetch daily spam reports
- Download a spam CSV snapshot
- Upload spam reports

### Report webhooks

Read and update report webhooks in CallerAPI from any Tray.ai workflow. The CallerAPI API covers calls such as subscribe a webhook and unsubscribe a webhook.

- Subscribe a webhook
- Unsubscribe a webhook
- List webhook subscriptions

### Voice firewall sessions

Read and manage voice firewall sessions in CallerAPI from any Tray.ai workflow. The CallerAPI API covers calls such as list recent sessions and get a session.

- List recent sessions
- Get a session
- Score a call recording

## Challenges Tray.ai solves

### Keeping CallerAPI credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store CallerAPI credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the CallerAPI API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the CallerAPI API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to CallerAPI?

Yes. Tray.ai connects to CallerAPI through the HTTP Connector, which calls the CallerAPI API directly. Any call the CallerAPI API documents can run as a step in a Tray.ai workflow.

### 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.

### Can I get a dedicated CallerAPI connector?

CallerAPI runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated CallerAPI connector from the CallerAPI API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/