Files and e-signing
Connect Scrive to Hypamoon
Yes. Scrive has a public, versioned API and you create the key yourself, so your chat can write the adapter.
OpenThe check
Three questions about the API of Scrive, answered from its own docs.
- Public API docs
- Yes. Read the docs
- A key you create yourself
- Yes. Create personal access credentials yourself in the Scrive account section, or OAuth client credentials under Integration settings. apidocs.scrive.com
- Versions or a changelog
- Yes. Versioned in the URL (version 2); breaking changes get a new version number. apidocs.scrive.com
- How it signs in
- Personal access credentials (one per user) or OAuth with client credentials from your account settings.
- Webhooks
- Yes. It can tell your app when something changes. apidocs.scrive.com
- Hosting
- Cloud
Your own contract flow on Scrive, from intake to a signed file in the right place.
- Documents, templates, signers and their status, straight from Scrive.
- AI that fills the document from the intake and checks who still has to sign.
- An intake page on your own site, and a short email when everything is signed.
Ask your chat
Answers straight from your Scrive data, in Claude or another chat with the full Hypamoon connection.
Which documents sent last week are still waiting for a signature?
Who signed the rental agreement, and when?
When something happens
Scrive sends a webhook to your app, and the app asks AI what happens next.
-
When
A document is fully signed.
AI decidesAI reads the document and picks the customer and the folder it belongs to.
ThenThe signed file is stored with the customer in your app, and the account manager gets an email.
A screen for your team or customers
An app on your own address, with sign-in, on top of the same Scrive data.
- For your customers
Customers sign in and find all their signed documents in one place.
Scrive stays the core: your chat builds the rest on its API, as an adapter plus an app and agents in your Hypamoon project. Reading starts after you click Allow in the portal. Every change an agent or a chat makes in Scrive waits for your approval, one call at a time. How adapters work
Good to know
- Your adapter uses a fixed key: you paste it once in the Hypamoon portal, never in the chat, and it only goes to the API host you allow.
- Callbacks go to the api_callback_url of each document and are retried up to 10 times.
Try it in your chat
Fill in what to read and write, and send it.
Build the Hypamoon recipe build-an-adapter for Scrive. API docs: https://apidocs.scrive.com/. Read: [what]. Write: [what, or nothing].
In Claude, or another chat with the full Hypamoon connection; adapters are not in ChatGPT yet. You paste the key in the portal, never in the chat. The full recipe
Sources
Checked on 7 November 2026.
Scrive is a name of its owner, used here only to describe the software. This page is not an official integration and Hypamoon has no partnership with Scrive. Found something that changed? Tell us at support.
More in files and e-signing
- Adobe Acrobat SignOpen
- BoxOpen
- DocuSignPossible
- DropboxOpen
- PandaDocPossible
- SharePoint and OneDriveOpen
- Yousign (Youtrust)Possible
- DocuWareOpen
- Google DriveOpen
- Dropbox SignOpen
- BoldSignOpen
- SignWellOpen
- OneflowOpen
- DocumensoOpen
- signNowOpen
- Zoho SignOpen
- NextcloudOpen
- pCloudPossible
- SignhostOpen
- PenneoOpen
- SkribbleOpen
- M-FilesOpen
- Autodesk Platform ServicesOpen
Tool not listed? Ask the chat to check its API.
The same three checks work for any software. Your chat reads the vendor's own docs and tells you what it found.
Check if [software] has an open API that a Hypamoon adapter can use: public API docs, a key or token I can create myself without asking the vendor, and versions or a changelog. Link the pages you used.
Fill in the name of your software. Checking needs no connection to Hypamoon.
Ready to connect Scrive?
Connect your chat once, then ask it to build the adapter.
Works in Claude, ChatGPT and Copilot. Add to Claude Add to ChatGPT
Add to Copilot