# FileScan.io integrations: scans and reports

> FileScan.io is a malware analysis service that scans files and URLs, produces threat reports, and checks the reputation of hashes, domains and IP…

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

## Overview

FileScan.io is a malware analysis service that scans files and URLs, produces threat reports, and checks the reputation of hashes, domains and IP addresses. Tray.ai connects to FileScan.io through the HTTP Connector, so your workflows can call the FileScan.io API alongside the rest of your stack.

## Use cases

### Scans

Read and manage scans in FileScan.io from any Tray.ai workflow. The FileScan.io API covers calls such as scan a file and scan a URL.

- Scan a file
- Scan a URL
- Get scan reports

### Reports

Read reports in FileScan.io from any Tray.ai workflow. The FileScan.io API covers calls such as get a report and search reports.

- Get a report
- Search reports
- List public reports

### Reputation

Read and manage reputation in FileScan.io from any Tray.ai workflow. The FileScan.io API covers calls such as check a hash reputation and check an IOC reputation.

- Check a hash reputation
- Check an IOC reputation
- Bulk check IOC reputation

### Threat intelligence

Read threat intelligence in FileScan.io from any Tray.ai workflow. The FileScan.io API covers calls such as get IOC prevalence and find similar reports.

- Get IOC prevalence
- Find similar reports

## Challenges Tray.ai solves

### Keeping FileScan.io 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 FileScan.io 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 FileScan.io 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 FileScan.io 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 FileScan.io?

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

### How does Tray.ai authenticate with FileScan.io?

The FileScan.io 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 FileScan.io connector?

FileScan.io runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated FileScan.io connector from the FileScan.io 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/