The Sanity Jobs API reports on long-running processes inside Sanity's infrastructure, such as dataset copy jobs. A status call returns a job's id, its state (pending, running, completed, failed, terminating, or terminated), the author IDs behind it, and its created and updated timestamps. A listen stream sends a welcome event, then job events carrying the state and a progress value from 0 to 100, and closes with a final event once the job reaches a terminal state. Errors after the stream opens, such as an unknown job ID or a stream open for 12 hours, arrive as channel_error and disconnect events rather than HTTP status codes.
REST API for the Sanity headless CMS platform. Query, mutate, and manage documents and datasets via GROQ queries and mutations. The API exposes 4 endpoints secured with apiKey, bearer authentication.
The Sanity Webhooks API sets up the webhooks that notify your services when content in a Sanity project changes, and shows how each delivery went. Document webhooks fire per document on create, update, or delete, narrowed by a GROQ filter and shaped by a GROQ projection, while transaction webhooks fire once per dataset transaction. Each webhook targets a URL and a dataset, or every dataset with *, and can set the HTTP method, custom headers, a secret, and whether drafts or all versions trigger it. Messages and delivery attempts record status, result codes, durations, and failure reasons for debugging.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsanity.io" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsanity.io" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.