Description
According to the OpenPanel documentation, event properties should be part of the payload returned by the /export/events endpoint.
However, when calling the endpoint, event properties are missing entirely, even though they are clearly present for the same event in the OpenPanel UI.
This makes it impossible to reconstruct or analyze event-specific context (e.g. form metadata) via the export API.
Documentation reference:
https://openpanel.dev/docs/api/export#get-events
Expected behavior
The /export/events endpoint should include the event’s custom properties (as shown in the UI) in the response payload, e.g. under a properties field (or equivalent), as implied by the documentation.
Actual behavior
The response only contains top-level event metadata. Event properties are missing.
Questions / Clarification requested
- Is the omission of event properties in /export/events intentional?
- If so, is there another endpoint intended for exporting full event payloads including properties?
- If not, this appears to be a bug or a documentation mismatch.
Description
According to the OpenPanel documentation, event properties should be part of the payload returned by the /export/events endpoint.
However, when calling the endpoint, event properties are missing entirely, even though they are clearly present for the same event in the OpenPanel UI.
This makes it impossible to reconstruct or analyze event-specific context (e.g. form metadata) via the export API.
Documentation reference:
https://openpanel.dev/docs/api/export#get-events
Expected behavior
The
/export/eventsendpoint should include the event’s custom properties (as shown in the UI) in the response payload, e.g. under a properties field (or equivalent), as implied by the documentation.Actual behavior
The response only contains top-level event metadata. Event properties are missing.
Questions / Clarification requested