Skip to content

Conversation

@nick-roscarel-octo
Copy link

Adds a deprecation notice for the /api/events and /api/{spaceId}/events endpoints.

[sc-104549]

@nick-roscarel-octo nick-roscarel-octo force-pushed the bft/nick/getevents-v1-deprecation branch from f230c66 to dde4c3c Compare March 11, 2025 02:37
@nick-roscarel-octo nick-roscarel-octo changed the title Add deprecation notice for Get Events V1 Add deprecation notice for the Get Events V1 endpoint Mar 11, 2025
### System and Space Level `/events` API Endpoint
The `GET /events` and `GET /{spaceId}/events` API endpoints will be replaced by new versions that don't return pagination properties. Events are created constantly, minimizing the value of providing individual page numbers, and calculating the total number of results can be very expensive on instances with larger data sets.

For similar functionality without pagination, use the `GET /events/v2` and `GET /{spaceId}/events/v2` endpoints. To export events in CSV format, use the `GET /events/export` or `GET /events/{spaceId}/export` endpoints.
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm running off the assumption that this notice should still be written in present imperative tense, even though the requisite PR isn't merged on the Server side.

If we want to use future tense initially, and then switch to present tense once it's released in cloud, I'm more than happy to raise a separate PR for it :)

@nick-roscarel-octo nick-roscarel-octo marked this pull request as draft March 16, 2025 21:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants