Event listing¶
Read reporting events as individual rows (or as a catalog of types). Use this when you need the underlying events — not aggregated pipeline counts.
Base URL: https://api.giosg.com/api/objectives/v1/orgs/<organization_id>
Authentication
For server-to-server calls, authenticate with a user API token: Authorization: Token <api token>. OAuth2 access tokens use Authorization: Bearer <access token> instead. How to obtain and use each: Get API token. The URL organization_id must match the authenticated organization.
How-to guides: Retrieving events.
Endpoints¶
| Page | Endpoint | Purpose |
|---|---|---|
| Event types | POST /event-types |
Explore which generic-event type masks (vendor / category / action) have been emitted |
| Generic events | POST /events |
Individual generic-event rows (widgets, goals, case management, custom events, …) |
| Message events | POST /message-events |
Individual chat message rows, almost always filtered to msg |
Generic events can reuse pipeline value sets ($name) in filters, next to at least one concrete field.
Message events also have an optional case management integration: flags to attach a case to each message, or to keep only messages that belong to a case. Those flags are off by default and are not required for ordinary chat listing.