Developer quickstart

Start with the production contract that exists today: a public HTTPS origin, narrow unauthenticated operations, and session-protected product APIs.

Production origin

The canonical WEDNESDAY API origin is:

https://api.wednesdaychat.com

The documentation origin is independent:

https://docs.wednesdaychat.com

Verify service health

GET /health is part of the deliberately public service surface.

curl --fail --silent https://api.wednesdaychat.com/health

A healthy API returns:

{"status":"ok"}

GET /ready reports whether required production dependencies are ready. It can return an HTTP 503 with a not_ready state when the service cannot safely accept production work.

Understand authentication before calling product APIs

WEDNESDAY’s current production product APIs use a server-authoritative account session. Browser requests include the session credential automatically, and unsafe mutations require the WEDNESDAY CSRF header.

Do not construct authority by sending owner IDs, roles, plans, or retired client identity headers. The server session is authoritative.

External developer access: this documentation does not claim a generally available API-key authentication scheme. When WEDNESDAY publishes one, the Authentication and API Reference pages will define it as an explicit public contract.

Choose the right guide

Use Conversation state for durable chat state.
Use Streaming for the structured SSE protocol.
Use Projects for scoped context and project-owned resources.
Use Files for the secure upload lifecycle.
Use API reference for verified routes and access classification.

Machine-readable version

The raw Markdown twin for this page is available at /getting-started.md.