# Duo Security integrations: integrations

> Create an integration and create bypass codes in Duo Security. Connect Duo Security to the rest of your IT stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/duo-security-integrations/
**Categories:** IT
**Connects through:** HTTP Connector

## Overview

Duo Security, part of Cisco, adds multi-factor authentication and device checks to logins, with an admin console for managing users, phones and protected applications. Tray.ai connects to Duo Security through the HTTP Connector, so your workflows can call the Duo Security API alongside the rest of your stack.

## Use cases

### Users

Read, create, and delete users in Duo Security from any Tray.ai workflow. The Duo Security API covers calls such as list users and create a user.

- List users
- Create a user
- Retrieve a user

### Integrations

Read, create, and delete integrations in Duo Security from any Tray.ai workflow. The Duo Security API covers calls such as list integrations and create an integration.

- List integrations
- Create an integration
- Modify an integration

### User phones

Read user phones in Duo Security from any Tray.ai workflow. The Duo Security API covers calls such as list a user's phones and associate a phone.

- List a user's phones
- Associate a phone
- Disassociate a phone

### User groups

Read user groups in Duo Security from any Tray.ai workflow. The Duo Security API covers calls such as list a user's groups and associate a group.

- List a user's groups
- Associate a group
- Disassociate a group

### Bypass codes

Read and create bypass codes in Duo Security from any Tray.ai workflow. The Duo Security API covers calls such as create bypass codes and retrieve bypass codes.

- Create bypass codes
- Retrieve bypass codes

## Challenges Tray.ai solves

### Keeping Duo Security 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 Duo Security 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 Duo Security 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 Duo Security 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 Duo Security?

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

### How does Tray.ai authenticate with Duo Security?

The Duo Security API uses basic authentication. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Duo Security connector?

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