Skip to main content

V1 API Overview

The V1 API provides a unified, domain-based interface for all Switchyard operations. It consolidates the previous /admin/* and /scanner/* routes into a single, consistent API structure.

Base URL

Key Features

Dual ID Support

All endpoints accept both UUIDs and 18-digit taxonomy IDs as identifiers.

Domain-Based Structure

Endpoints are organized by business domain (products, orders, sweeps, etc.).

Consistent Authentication

All routes require Bearer token authentication via Supabase Auth.

Zod Validation

Request/response validation using Zod schemas for type safety.

Authentication

All V1 API endpoints require authentication using a Bearer token:
Get your access token by authenticating with Supabase Auth. See the Authentication Guide for details.

API Domains

The V1 API is organized into the following domains. All endpoint documentation is auto-generated from our OpenAPI specification.

Core Operations

Organization

Equipment

Scheduling & Auth

Utilities

ID Resolution

All endpoints that accept an :id parameter support both formats:
The API automatically detects the format:
  • UUID: 36 characters with hyphens (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)
  • Taxonomy ID: Exactly 18 digits (DDDDDDDDDDDDDDDDDD)
See the Taxonomy ID Guide for details on the ID format.

Common Response Formats

Success Response

List Response

Error Response

Pagination

List endpoints support pagination via query parameters:

Filtering

Many list endpoints support filtering:

Rate Limiting

The API implements rate limiting to ensure fair usage: Rate limit headers are included in responses:

Versioning

The V1 API is versioned in the URL path. Future versions (v2, v3, etc.) will be introduced as separate paths while maintaining backward compatibility with existing versions.

SDKs and Tools

TypeScript Types

Auto-generated TypeScript types from the OpenAPI spec.

MCP Server

Connect Claude and other AI assistants to your Switchyard data.

Next Steps