Productivity
Superhuman Docs in your product and your AI agents, through one API
The toolkit covers docs, pages, tables, columns and rows: list and create docs, read and write page content, and read, insert, update and delete table rows. Your product or AI agent calls them through Connect, which stores the API key and logs every execution.
15 days to try it. No credit card.
POST https://connect.reportei.com/api/tools/coda_create_doc/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"title": "<title>"
}
}How it works
From a connected customer to the first Superhuman Docs call.
- 1
Your customer connects the account
Your system opens a Connect session for the toolkit and your customer connects their Superhuman Docs account. You get the connection id.
- 2
Your product calls the tool
A POST to /api/tools/{tool}/execute with the connection id and arguments. On success, Connect preserves the app's response status and body.
- 3
Connect handles the rest
It stores the credential encrypted, renews tokens for OAuth connections that support renewal and records executions in an audit trail available through the API.
Use cases
What your product does with Superhuman Docs.
Use a doc as a database
A SaaS writes rows into a table of the customer's doc with Create rows and updates them later, matching on key columns.
Generate pages from your data
An agency tool creates a page with Markdown content in a doc, then edits or appends to it as the data changes.
Agent that reads team docs
An AI agent lists docs and pages, reads a page's content as text and queries table rows to answer questions.
Tools
12 Superhuman Docs tools
- List docsGETLists the docs the user can access and has opened at least once, latest activity first, with id, name, owner, workspace and browserLink. Send nextPageToken as pageToken for the next page.
- Create docPOSTCreates a doc, empty or as a copy of another doc, in the My docs folder of the oldest workspace the user joined. Needs the Doc Maker role in the workspace.
- List pagesGETLists the pages of a doc with id, name, subtitle, parent and children. Send nextPageToken as pageToken for the next page.
- List page contentGETReturns the content of a page as plain text, element by element. Send nextPageToken as pageToken for the next part.
- Create pagePOSTCreates a page in a doc, or a subpage, with content in Markdown or HTML. The change is queued and shows up in a few seconds; the response has the id of the page. Needs the Doc Maker role.
- Update pagePUTRenames a page or adds content to it, at the end, at the start or replacing everything. The change is queued and shows up in a few seconds. Changing the name needs the Doc Maker role.
- List tablesGETLists the tables and views of a doc with id, name, type and parent page. Rows are written only to tables, not to views. Send nextPageToken as pageToken for the next page.
- List columnsGETLists the columns of a table with id, name and format. The column ids go in the cells of Create rows and Update row and in the query of List rows.
- List rowsGETLists the rows of a table or view, oldest first unless sortBy says otherwise, with id, name and the values keyed by column id. The data can lag a few seconds behind the doc; send nextPageToken as pageToken for the next page.
- Create rowsPOSTInserts rows in a table, or updates the rows that match the keyColumns. Every matching row is updated. Only base tables take rows, not views; the change is queued and shows up in a few seconds.
API key
Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.
Questions about the Superhuman Docs toolkit
Do I need to build against the Superhuman Docs API?
No. Connect ships 12 Superhuman Docs tools, described and ready. Your customer connects the account and your system calls every tool through the same endpoint, with the same request format.
How does my customer connect their Superhuman Docs account?
With the mode the toolkit accepts: API key. Connect stores the credential encrypted and never returns it to your system.
Does it work with AI agents?
Yes. Each tool's input is described in JSON Schema, which your agent uses directly as a tool definition. The agent picks the tool and the arguments, and your system makes the call to Connect.
Does my customer need a Reportei account?
No. Your customer connects the account on a Connect screen, or your system sends the credential through the API, and they keep using only your product.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
