API reference

The production API origin is https://api.wednesdaychat.com. This reference documents only routes and behaviors that are verified in the production service and explicitly approved for public use.

Access boundary: WEDNESDAY currently uses server-authorized account sessions for most product operations. The existence of an HTTP route does not imply an unrestricted third-party API-key contract.
GET/search?q=…

Searches durable account-owned WEDNESDAY state. Query text is required and bounded; result size is bounded by the service.

Projects

Verified project operations include listing, creating, loading, renaming, archiving, restoring, and deleting projects; reading and updating project settings and instructions; project search; project conversations; file membership; connector bindings; and work history.

Conversations

Verified conversation operations include listing and loading conversations, messages, drafts, follow-ups, branches, archive state, pin state, project movement, feedback, sharing, usage recording, and durable deletion.

Chat streaming

POST/chat

Starts a durable streaming chat turn for the authorized account. The stream is explicitly non-cacheable and supports structured runtime events.

POST/chat/{turn_id}/input

Submits mid-turn steering input to an active turn. Durable cancellation is supported when the turn identifier resolves to a durable chat turn.

Files and artifacts

The production service exposes owner-scoped file upload, file inspection, file-library, picker, attachment-state, download, message-attachment, assistant-artifact, location-context, memory-source-consent, and deep-research capability families. Individual contracts are published only after their request/response schemas are stable enough to support externally.

Publication boundary

Operational probes, privileged administration, deployment coordination, implementation-specific service metadata, upstream routing, and private callback surfaces are intentionally omitted from the developer reference.

Public documentation is a compatibility promise. Source-code presence alone is not a public contract.

Ask WEDNESDAY