Changes
Read change history
Events describe what changed on one opportunity. Use updated_since to discover which records changed, then read events for the ones you already store.
Request
GET https://eoqbgibebefvxxzadphf.supabase.co/functions/v1/external-api/v1/opportunities/{id}/events?since=2026-10-01T00:00:00Z&type=status_changed,date_changed&limit=25| Parameter | Format | Default |
|---|---|---|
| type | Comma-separated or repeated | All types |
| since | RFC 3339 timestamp | None |
| include_insignificant | true or false | false |
| limit | Integer from 1 to 100 | 25 |
| cursor | Opaque string | None |
Results are ordered by detected_at descending, then id descending. Noise and cosmetic events are omitted unless include_insignificant=true. Pagination uses the same cursor rules as the opportunity list.
Event types
opportunity_added
opportunity_removed
status_changed
date_changed
funding_changed
description_changed
qanda_updated
attachments_changed
field_updatedAn unrecognized stored type is returned as unknown. Render it. Do not reject the response because a type or status is new.
changes.previous and changes.current are not stable scalars. They can be text, numbers, or objects. Display them as data, and do not assume a field always changes the same way.