Version 0.51.1

Improvements

Synced teams show their external ID in the API, and outgoing webhooks are documented

Teams synced from Atlassian, GitHub, GitLab or Microsoft 365 now include their ID in that system when you read them through the REST API or an AI agent. Scripts can use it to find the same team upstream, for example when setting a team on a Jira issue. There is also a new reference page for outgoing webhooks. It covers each event, the payload format, and how to verify the signature on a request.

Webhooks now tell you more about who owns what

Catalog entity webhooks now include the owning team's ID and, for synced teams, its ID in your team directory. You can route work to the right team without an extra lookup. Webhooks also fire when a team is created, renamed, relinked, or removed, so systems that mirror ownership stay in step right away.

Bug fixes

Service accounts can look up their organization over MCP

AI agents connected with a service account can now ask which organization they are working in. Before, that request failed for service accounts even though it worked for people.

Validation errors now report a consistent error code

Validation errors from the GraphQL API and MCP tools now consistently return the VALIDATION_ERROR error code with the invalid field named in the field extension, instead of occasionally reporting the field name as the error code itself. REST responses for these errors now correctly return 422 Unprocessable Entity.