Browsing events within a tenant is exposed through the List Tenant Events API. This guide explains how to use the tenant feed API perform a full export of all results.

​
Paging

The tenant feed endpoint uses parameters that match the Flare standard paging pattern .

​
Fetching new results in future executions

It is possible to save the next in a database and use it to resume fetching new results in the future. However, it is important that future requests use exactly the same parameters for everything else but next.

​
Getting the full data of results

For performance reasons, feed results only contain the bare minimum. To get the full data, an API call must be made per result to the Retrieve Event endpoint.

​
Available Endpoints

​
List events for a tenant

If you’re looking to export the events of a tenant, refer to the List Tenant Events endpoint. 
# (incomplete example)

for resp in api_client.scroll(
    method="POST",
    url="/firework/v4/events/tenant/_search",
    json={
        "from": last_from,
    },
):
    ...

​
List events for a single identifier

If you’re looking to export the events of a single identifier, refer to the List Identifier Events endpoint. 
# (incomplete example)

# ID of the identifier for which we want to list the events.
identifier_id: int = 12345

for resp in api_client.scroll(
    method="POST",
    url=f"/firework/v4/events/identifiers/{identifier_id}/_search",
    json={
        "from": last_from,
    },
):
    ...

​
List events for an identifier group

If you’re looking to export the events of an entire identifier group, refer to the List Identifier Group’s Events endpoint. 
# (incomplete example)

# ID of the identifier group for which we want to list the events.
identifier_group_id: int = 12345

for resp in api_client.scroll(
    method="POST",
    url=f"/firework/v4/events/identifier_groups/{identifier_group_id}/_search",
    json={
        "from": last_from,
    },
):
    ...

​
End-to-End Examples

These are end-to-end examples in various programming languages.