Events API Changelog

Version 1.3

Endpoints Affected by Event Pricing Access Restrictions
- services/events/v1/events/{event_id}/worksheets
- services/events/v1/bids/{bid_id}/bid_line_items
If the user does not have event pricing access, a 403 error response is returned.

Attribute created_at was added to expose the time of creation for the event.
Attribute published_at was added to expose the time of publishing for the event.

Attribute restricted was added to identify events that are invitation only even when posted on the public site.

Attribute is_public was added to identify public events.
Param is_public was added to event creation API to specify event visibility. Param is optional and will use event template value if not provided.
The foreign key field spend_category_id was migrated from the attributes section to the relationships section of the Event resource. This improves consistency with the JSON:API spec.
The scout_field_type attribute in Describe endpoints has been renamed type_description for clarity.
The documentation clarifies that the state attribute of an Event is a read only API field.
The documentation clarifies that custom fields of type File are not accessible via API.
Authorization errors will now return HTTP 403.
Paginated endpoints will no longer wrap around to the start of the collection if you follow the next page links.
All relevant functionality was inherited from the Events, Event Supplier Companies, Event Supplier Contacts, Bids, Bid Line Items, Line Items, and Worksheets resources in our legacy V3 public API.