Extensions
Get Extension Events
Changed onPoll for extension lifecycle events the current user has triggered.
Events are scoped to the authenticated user via a server-derived keyspace (user:{user_id}); there is no client-controllable keyspace, so an authenticated user cannot read another user's flow-migration or bundle-reload events. A client-supplied keyspace query parameter is rejected with 422 so the contract is explicit -- previously the value was silently dropped, which masked client bugs that assumed it had effect.
svc.since() uses blocking sqlite3; run in a thread pool so the asyncio event loop is not held while waiting on disk I/O.
get/api/v1/extensions/events
Request
- The document declares no server URL.
- Auth
- OAuth 2PasswordToken URL: api/v1/login
- or API key in query parameter x-api-key
- or API key in header x-api-key
Query parameters
sincenumber
UTC epoch timestamp; return events after this cursor
Response
Successful Response
Changes
- info
endpoint added
- info
- breaking
api path removed without deprecation
- breaking