BayWise Developer API

The BayWise Public API lets you integrate your workshop directly with your own tools — Dealer Management Systems (DMS), ERP platforms, dashboards, automation, or AI assistants.

There are two products, each with its own API under the same base URL and the same kind of key:

Not sure which? Scheduler is about the work; Payments is about the money. Many integrations use both.

How the API works (both products)

• Base URL: https://api.baywise.ai/v1
• Auth: send your key as a bearer token — Authorization: Bearer bw_live_…. Create keys in Settings → Developer; a key can only do what your role allows, and can be scoped to one location.
• Reads: list endpoints return { "data": [...], "next_cursor": … } — pass next_cursor back as ?cursor for the next page.
• Writes: send an Idempotency-Key header on creates so retries never double-record.
• Errors: standard RFC 7807  application/problem+json, each with a request_id you can quote to support.
• Sensitive actions (e.g. voiding a payment) use confirm-then-commit — a prepare step returns a one-time grant, then the real call carries it.

Interactive reference

Every endpoint, field, and schema — with a “try it” console — is in the interactive reference. Pick your product from the dropdown:

• Scheduler API reference 
• Payments API reference 

Guides

• Getting Started — create your first key and make a request in minutes
• Scheduler API / Payments API — concepts, when to use, and a typical flow for each
• Webhooks — subscribe to job, step, and payment events instead of polling
• Reference — the interactive endpoint reference

AI assistants (MCP)

Both products are available to AI assistants (Claude, Cursor, …) via the BayWise MCP server at https://mcp.baywise.ai. Generate a token in Settings → Developer → Connect via MCP; the assistant acts as you and, in this version, has read-only access.