Unless stated otherwise, this page refers to Ukrainian companies and individual entrepreneurs and uses identifiers from Ukrainian public registries.
This section describes the request used to work with the enterprise timeline.
The timeline shows events recorded for an enterprise in ESG SaveEcoBot. Each record returns short structured data about the event object itself and links that can be used to navigate to related API data.
GET /api/v1/enterprises/{registry_id}/timeline
This request returns enterprise timeline events in reverse chronological order. The response also includes structured object, parent_object, and links blocks so an external system can navigate to related data without parsing textual descriptions. Full object details are not duplicated in the timeline; use the provided links for that. Available event values can be retrieved from the Timeline events request.
The registry_id parameter in the request path is required. It is the enterprise identifier.
Example request
$ ESG_API_TOKEN="your_api_token"
$ curl "https://esg.saveecobot.com/api/v1/enterprises/00178353/timeline" \
-H "Authorization: Bearer $ESG_API_TOKEN" \
-H 'Accept: application/json'
Example response
{
"results": {
"enterprise": {
"type": "company",
"registry_id": "00178353"
},
"items": [
{
"id": 1207031,
"event": "created_permission_file",
"type_label": "Додано файл дозволу",
"object": {
"resource": "permission_file",
"id": 99881,
"type_id": 5
},
"parent_object": {
"resource": "permission",
"id": 147,
"type_id": 5
},
"links": {
"object": {
"files": "https://esg.saveecobot.com/api/v1/enterprises/00178353/permission-files/147",
"download": "https://esg.saveecobot.com/api/v1/enterprises/00178353/permission-files/147/download/99881"
},
"parent_object": {
"files": "https://esg.saveecobot.com/api/v1/enterprises/00178353/permission-files/147"
}
},
"occurred_at": "2025-01-24T00:00:00+00:00",
"created_at": "2026-04-28T05:24:07+00:00"
}
],
"pagination": {
"current_page": 1,
"per_page": 20,
"total": 34,
"last_page": 2
}
},
"stats": { "..." }
}
Pagination parameters
page: page number.
Filters
after: returns only records added to the timeline after the specified date and time. Format:YYYY-MM-DD HH:MM:SS.event: returns only records of a single event type. Available values can be retrieved from the Timeline events request.
Response fields
results.items[]
id: timeline record identifier.event: technical event code.type_label: short human-readable event type label.object: short structured description of the main event object.parent_object: short structured description of the parent object if the event refers to a nested resource.links: set of links to related API data.occurred_at: date and time of the event itself.created_at: date and time when the timeline record appeared.
results.items[].object
resource: technical resource type code, for examplereport,permission_file,registry, orcourt_case. Available combinations ofevent,resource, andparent_resourcecan be retrieved from the Timeline events request.id: identifier of this resource in the API.type_id: type identifier, if the resource has a separate type classification.
results.items[].parent_object
- returned in the same format as
object; - used for nested resources, for example a permit file, registry file, EIA document, or SEA document.
results.items[].links
object: links to the event object data.parent_object: links to the parent object data, if present.
results.items[].links.object
- the set of links depends on the resource type;
- it may include
details,files,download,documents,hearings,violations,sanctions, orland_plots; - use these links to get full object data or related records.
results.items[].links.parent_object
- the set of links depends on the parent resource type;
- most often this is a link to a general list of related data, such as
filesordocuments.
