---
title: "REST API and OpenAPI"
description: "Choose direct REST or an official server SDK, find the resource guide for your workflow, and use generated OpenAPI contracts for automation."
---

The Server API is the trusted control plane for inventory provisioning, hold
inspection, booking, operational changes, reports, and webhook configuration.
Call it from a backend or another environment where buyers cannot inspect your
secret key.

If you have not yet separated inventory, audience access, pricing, and SDK
choice, read the [SeatLayer product model](/start/product-model/) first. This
landing page groups the same contracts by backend workflow.

## Choose REST or a server SDK

| Surface | Choose it when | Start here |
|---|---|---|
| Official server SDK | Your backend uses Node.js, Python, PHP, Java, Go, Ruby, or .NET | [Choose a server SDK](/server-sdk/) |
| REST API | You want direct HTTP control or use another language | [Authentication](/start/authentication/) and [OpenAPI 3.1](/openapi.json) |

Both surfaces operate on the same public contracts. The
[operation support matrix](/server-api/operation-support/) records exact REST
and server-SDK coverage without requiring narrative pages to duplicate it.

## Find a workflow

<CardGrid>
  <Card title="Events and inventory" icon="ph:calendar-check">
    Create and update [Events](/server-api/events/), manage
    [inventory rules](/server-api/inventory/), and use
    [blocks](/server-api/blocking/) for operational holds.
  </Card>
  <Card title="Hold and book" icon="ph:ticket">
    Understand [seat holds](/server-api/how-seat-holds-work/), inspect or create
    [holds](/server-api/holds/), then [book inventory](/server-api/booking/).
  </Card>
  <Card title="Sales channels and private access" icon="ph:users-three">
    Allocate one Event with the [Sales Channels API](/server-api/channels/) and
    authorize an eligible browser with a
    [Buyer Access Session](/server-api/buyer-access-sessions/).
  </Card>
  <Card title="Multi-event inventory" icon="ph:calendar-dots">
    Coordinate one atomic run with the
    [Performance Groups API](/server-api/performance-groups/), or publish
    renewable Plans and Seat Rights with the [Seasons API](/server-api/seasons/).
  </Card>
  <Card title="Operations and reconciliation" icon="ph:arrows-clockwise">
    Handle [idempotency and conflicts](/server-api/idempotency-and-conflicts/),
    [cancellations and box office](/server-api/cancellations-and-box-office/),
    and [reports](/server-api/reports/).
  </Card>
</CardGrid>

## Machine-readable contracts

- [OpenAPI 3.1](/openapi.json) describes public HTTP operations and schemas.
- [Operation support JSON](/operation-support-matrix.json) records REST and
  server-SDK implementation and release evidence.
- [SDK catalog](/sdk-catalog.json) records current package, source, registry,
  documentation, and stability information.

Treat generated contracts as exact operation truth and these guides as workflow
explanation. Keep secret keys server-side, use test-mode resources while
integrating, and follow each mutation's documented retry boundary.