Content & Documents · Integration
SignRequest
Add SignRequest to your product for your customers, and give your AI agents governed access to it.
SignRequest handles the point in a workflow where a document has to be signed and the signature has to hold up afterwards. An embedded SignRequest integration creates signature requests from a file your product generated or from one of the customer's own templates, sets the signers and the order they sign in, follows each one through viewed, signed and declined, and downloads the completed document with its signing log. The detail worth building around is duration: somebody may sign in ten minutes or in ten days, so your product should react to the event rather than poll for a change that usually has not happened. Each customer authorises their own team, so requests go out in their name and not yours. fastn holds the credentials per tenant and keeps the connector current.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own SignRequest team so signature requests are sent under their name.
Send a document your product generated for signature without a user downloading and re-uploading it.
Use that customer's own templates so their wording and signer roles are the ones people see.
React to a signed or declined event so the next step of your workflow runs as soon as the outcome lands.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which signature requests are outstanding and who has not signed yet.
An agent sends a reminder on a pending request within governed permissions, with the action logged.
An agent reads a completed document and its signing log to confirm what was agreed.
Example prompt
Which documents are still waiting on a signature, and who is holding each one up?
Set up SignRequest in 4 steps
- 01Enable the SignRequest connector in your fastn dashboard.
- 02Have each customer authorise their own SignRequest team so requests originate with them.
- 03Map the document, signer and template fields your product uses, then enable the signing events you react to.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the SignRequest integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a SignRequest integration without building it. Your customers connect their own SignRequest account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a SignRequest update is not your on-call problem.
- One integration serves your product and your agents. The same governed SignRequest connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Docusign
HelloSign
Adobe Acrobat SignOften used alongside
Tools the same teams tend to run next to SignRequest, across other categories.
Shopify
Stripe
Jira
AsanaSignRequest integration FAQ
How do I add a SignRequest integration to my product?
Enable the SignRequest connector in your fastn dashboard, then let each customer authenticate their own SignRequest account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no SignRequest client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own SignRequest account?
Yes. Every connection is scoped to the individual customer, so each authorises their own SignRequest account and only ever sees their own files, documents and versions. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this SignRequest integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports which signature requests are outstanding and who has not signed yet.
Who maintains the SignRequest integration?
fastn does. When SignRequest changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose permissions does the SignRequest integration run under?
Each customer's own SignRequest grant. Where SignRequest holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in SignRequest automatically?
Where SignRequest supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the SignRequest integration?
A common starting point: let each customer connect their own SignRequest team so signature requests are sent under their name. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the SignRequest integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding SignRequest does not change your per-connector cost. You can start free with 3 connected accounts.
Add SignRequest to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.