Documentation Index
Fetch the complete documentation index at: https://docs.steppd.com/llms.txt
Use this file to discover all available pages before exploring further.
Steppd’s REST API lets you pull published document data programmatically, sections, steps, sub-steps, and metadata, using an API key for authentication. API keys are created and managed from your Profile page, under the API Keys tab.
API keys are available on the Scale plan only. See the API reference for available endpoints.
Create an API key
Open Profile → API Keys
Click your avatar or name in the sidebar to go to your Profile, then select the API Keys tab.
Click + New API key
Click + New API key and enter a name that helps you identify what the key is used for, for example, n8n integration or internal dashboard.
Copy the key immediately
The full API key value is displayed once immediately after creation.Copy your API key now. The key value is never shown again after you leave this screen. If you lose it, delete the key and create a new one.
Key is now active
The new key appears in your list showing its name and creation date. The key value itself is not displayed again, only the name is stored for your reference.
Use the API key
Pass your API key as a Bearer token in the Authorization header of every request.
Authorization: Bearer YOUR_API_KEY
For example, to retrieve a document:
GET /api/documents/{document_id}
Authorization: Bearer YOUR_API_KEY
See the API reference for the full list of available endpoints and response schemas.
Delete an API key
Click Delete on the key row to revoke access. Deletion is immediate, any requests using that key will be rejected instantly. This cannot be undone; if you need access again you must create a new key.
Find your document IDs
The API Keys tab also lists your organization’s published documents alongside their IDs. Click Copy next to any document to copy its ID to your clipboard. Use this ID in API requests to retrieve that document’s content.
If you are building an automation that pulls the latest version of a specific SOP, copy the document ID once and store it in your automation platform’s configuration. The ID does not change between revisions.