# OpenCTI integrations: indicators and reports

> Create an indicator, create a report and create an observable in OpenCTI. Connect OpenCTI to the rest of your security and compliance stack with Tray.ai.

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

## Overview

OpenCTI is a threat intelligence platform from Filigran for storing, linking and sharing indicators, malware, reports and incidents in STIX format. Tray.ai connects to OpenCTI through the HTTP Connector, so your workflows can call the OpenCTI API alongside the rest of your stack.

## Use cases

### Indicators

Read, create, and update indicators in OpenCTI from any Tray.ai workflow. The OpenCTI API covers calls such as list indicators and create an indicator.

- List indicators
- Create an indicator
- Update an indicator

### Reports

Read and create reports in OpenCTI from any Tray.ai workflow. The OpenCTI API covers calls such as list reports and create a report.

- List reports
- Create a report
- Add an object to a report

### Observables

Create, delete, and manage observables in OpenCTI from any Tray.ai workflow. The OpenCTI API covers calls such as create an observable and add a label.

- Create an observable
- Add a label
- Promote to an indicator

### Malware

Read and create malware in OpenCTI from any Tray.ai workflow. The OpenCTI API covers calls such as list malware and create a malware entry.

- List malware
- Create a malware entry

### Incidents

Read and create incidents in OpenCTI from any Tray.ai workflow. The OpenCTI API covers calls such as list incidents and create an incident.

- List incidents
- Create an incident

## Challenges Tray.ai solves

### Keeping OpenCTI 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 OpenCTI 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 OpenCTI 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 OpenCTI 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 OpenCTI?

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

### How does Tray.ai authenticate with OpenCTI?

The OpenCTI API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated OpenCTI connector?

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