Sanity logosanity.ioAll Systems Operational© Sanity 2026
Change Site Theme
Sanity logo

Documentation

    • Overview
    • Platform introduction
    • Next.js quickstart
    • Nuxt.js quickstart
    • Astro quickstart
    • React Router quickstart
    • Studio quickstart
    • Build with AI
    • Content Lake
    • Functions
    • APIs and SDKs
    • Visual Editing
    • Blueprints
    • Platform management
    • Dashboard
    • Studio
    • Canvas
    • Media Library
    • App SDK
    • Content Agent
    • HTTP API
    • CLI
    • Libraries
    • Specifications
    • Changelog
    • User guides
    • Developer guides
    • Courses and certifications
    • Join the community
    • Templates
HTTP API Reference
Overview

  • Content Lake API

    Actions
    Assets
    Copy
    Backups
    Doc
    Export
    History
    Jobs
    Listen
    Live
    Mutation
    Query
    Scheduling
    Webhooks

  • Compute and AI

    Agent Actions
    Embeddings Index

  • Apps

    Media Library

  • Management API

    Access
    Projects
    Roles

HTTP API ReferenceLast updated September 8, 2025

HTTP API Reference

The HTTP API endpoints offer direct access to the same APIs used by the Sanity Client, Studio, and other apps to interact with Content Lake and the greater Sanity ecosystem.

Get started

Authentication

How to submit authenticated requests.

URL Format

tl;dr: <projectId>.api.sanity.io/<version>/<path>

Patches

The valid patch types when using the direct HTTP mutations api.

Popular endpoints

Query API reference

Reference documentation for the Query HTTP endpoint.

Mutation API reference

Reference documentation for the Mutatation HTTP reference.

Actions API reference

Reference documentation for the Actions HTTP endpoint.

New endpoints

Access API reference

A centralized API to manage resource access control through roles and permissions.

Media Library API reference

HTTP endpoints reference for the Media Library API

Agent Actions

Reference documentation for the Agent Actions HTTP API.

Live Content API reference

Reference documentation for the Live HTTP endpoint.