Skip to main content
The public API is versioned in its path: every endpoint is under https://api.guild.ai/v1. Code you write against /v1 keeps working as the API grows.

​
Changes that ship without notice

These are additive, so they don’t break existing integrations:
  • New endpoints
  • New optional parameters
  • New fields in responses
  • New values in enums, such as a new event type
Your integration should ignore response fields and enum values it doesn’t recognize.

​
Breaking changes

A breaking change is one that could stop an existing integration from working, such as removing or renaming an endpoint, parameter, or field, or changing a field’s type. Breaking changes ship in a new API version, such as /v2, rather than changing /v1 in place. They are announced in these docs ahead of time, with the replacement available when the change is announced.
Last modified on October 26, 2026