Content & Documents · Integration
GetAccept
Add GetAccept to your product for your customers, and give your AI agents governed access to it.
Embed a GetAccept integration so your customers can send their own documents for electronic signature from inside your product and see status change without switching tools. Access runs through each customer's own GetAccept account, so their templates and sharing rules apply and your product cannot reach documents the connected account could not reach itself. fastn handles per-customer authorisation and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers send a document for signature from your product, using their own templates and recipients.
Show signing status and recipient activity inside your product so nobody chases by email.
Download the completed document and file it against the record it belongs to.
Trigger your product when a document is viewed, signed, declined, or expires.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent checks which documents are outstanding and who has not signed yet.
An agent sends a document for signature within governed permissions, with the action logged.
An agent reacts to a completed signature and runs the next step of the workflow.
Example prompt
List documents sent in the last two weeks that are still unsigned, with the recipient and last viewed date.
Set up GetAccept in 4 steps
- 01Open the GetAccept connector from your fastn dashboard.
- 02Have each customer authenticate their own GetAccept account.
- 03Map the templates, recipient fields, and document types your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the GetAccept integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a GetAccept integration without building it. Your customers connect their own GetAccept 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 GetAccept update is not your on-call problem.
- One integration serves your product and your agents. The same governed GetAccept 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
Adobe Acrobat SignWorks well with
SalesforceOften used alongside
Tools the same teams tend to run next to GetAccept, across other categories.
Shopify
Stripe
Jira
AsanaGetAccept integration FAQ
How do I add a GetAccept integration to my product?
Enable the GetAccept connector in your fastn dashboard, then let each customer authenticate their own GetAccept account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no GetAccept client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own GetAccept account?
Yes. Every connection is scoped to the individual customer, so each authorises their own GetAccept 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 GetAccept 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 checks which documents are outstanding and who has not signed yet.
Who maintains the GetAccept integration?
fastn does. When GetAccept 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 GetAccept integration run under?
Each customer's own GetAccept grant. Where GetAccept 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 GetAccept automatically?
Where GetAccept 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 GetAccept integration?
A common starting point: send a document for signature from your product, using their own templates and recipients. 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 GetAccept integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding GetAccept does not change your per-connector cost. You can start free with 3 connected accounts.
Add GetAccept to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.