Changelog

The Julius Answer API is version 1 (/api/v1, OpenAPI info.version 1.0.0). New operations, fields and event types can appear at any time; anything that would break existing code gets a new version and notice first.

How versions work

• Added without notice: new operations, new optional inputs, new fields in answers, new event types and new MCP tools or prompts. Ignore fields and event types you don't know.
• Never changed within v1: existing paths, required inputs, field names and meanings, the error shape and the webhook signature.
• Removed or changed: only in a new version, announced here first.

October 20, 2026: version 1

• REST API with 64 operations: calls and transcripts, contacts, bookings, the to-do list, results for the last days, the team, taught answers, the setup, the phone number, connections, follow-ups and messages to callers (with suggested replies to texts), texting status, the CRM assistant and a ZIP export.
• MCP server for Claude, ChatGPT, Cursor and other AI apps, with every operation as a tool (except the export and the CRM approval), five prompts and console approval for outward steps.
• Sign-in: API keys with read, write or admin access and optional expiry; OAuth 2.1 with PKCE, dynamic client registration and client ID metadata documents.
• Events: signed webhooks for ten event types (including text.received), and the events feed (GET /events) for polling.
• Texting and follow-ups: read and change follow-ups, see texting status, list a caller's texts and emails and send one. From AI apps, messages and changes that reach callers wait for the person's Yes. See texting and follow-ups.
• Partner API for agencies: partner keys, creating workspaces for clients, agency access that owners control, and MCP across many businesses.
• Console: Settings, API & AI apps lists keys, connected apps, agencies and every change they made.