# SignRequest integrations: documents

> Create a document and create a signature request in SignRequest, and start a workflow when SignRequest sends “Document sent”.

**Canonical page:** https://tray.ai/connectors/signrequest-integrations/
**Categories:** Documents and e-signature
**Connects through:** HTTP Connector

## Overview

SignRequest is an electronic signature service for sending documents out for signing, tracking who has signed, and storing the signed copies. Tray.ai connects to SignRequest through the HTTP Connector, so your workflows can call the SignRequest API alongside the rest of your stack.

## Use cases

### Documents

Read, create, and delete documents in SignRequest from any Tray.ai workflow. The SignRequest API covers calls such as list documents and create a document.

- List documents
- Create a document
- Get a document

### Signature requests

Read, create, and delete signature requests in SignRequest from any Tray.ai workflow. The SignRequest API covers calls such as list signature requests and create a signature request.

- List signature requests
- Create a signature request
- Cancel a signature request

### Templates

Read templates in SignRequest from any Tray.ai workflow. The SignRequest API covers calls such as list templates and get a template.

- List templates
- Get a template

### Teams

Read, create, and update teams in SignRequest from any Tray.ai workflow. The SignRequest API covers calls such as list teams and create a team.

- List teams
- Create a team
- Update a team

### Webhooks

Read, create, update, and delete webhooks in SignRequest from any Tray.ai workflow. The SignRequest API covers calls such as list webhooks and create a webhook.

- List webhooks
- Create a webhook
- Update a webhook

### SignRequest events

Start a Tray.ai workflow the moment something happens in SignRequest. SignRequest sends events such as document sent and document signed to a Tray.ai webhook trigger.

- Document sent
- Document signed
- Document declined

## Challenges Tray.ai solves

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

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

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

The SignRequest 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 SignRequest connector?

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