Added Control Over Public and Partner API Responses

Integrations have had little say over how much detail the public and partner APIs return, so a feed that only needs a name and an id still arrives carrying full related records. You can now configure how each relationship is populated, returning full records, short summaries, or ids only, so you can trim a live feed down to exactly what it needs without extra round trips. This works across events, event instances, and custom objects, and your existing settings keep returning full records, so there is no migration required.

Decide how much each field returns

For configured fields, you choose the shape that comes back: a full record, a summary, or just an id. A busy public feed can drop to ids or summaries where the full detail is not needed, which keeps payloads small and responses quick, while fields you leave alone continue to return everything as before. The control sits in the admin alongside the field, so the people who shape a feed do not need to touch the integration. Related records joined onto a record, such as the events under a season or the instances under an event, were previously capped at a small default and came back truncated, so joins now return a fuller page and a theme can request a complete list when it needs every related record, which lets event grids and similar layouts render in full rather than stopping short.

Look events up by external id

When your events carry an identifier from another system, you can now fetch one directly with a lookup by that external id, so an integration that already knows a record in its own terms does not have to search for the matching event first. The lookup returns the same event detail and caching behaviour as the standard endpoint, and the external id is now included in public event responses and in the partner API defaults, so the value you key on travels with the record.

Safely manage custom-theme blocks

Partners can now update the content blocks on a page through a dedicated endpoint, working in a draft and confirming the record has not changed since they last read it, so a stale update cannot quietly overwrite newer work and published content is never touched until the change is applied. To remove a sharp edge, the standard partner write endpoints now reject attempts to set block and theme fields directly and return a clear error instead, so a generic write cannot corrupt a page's block structure. Custom attributes nested inside partner record layouts are now described in the partner schemas as well, so the documentation matches what the API actually returns.