Changelog
Loading changelog...
| Date | Type | Description |
|---|---|---|
| 2026-05-11 | Added | Add Tasmania and Northern Territory coverage in Australia for incident events. |
| 2026-04-17 | Add | Add Afrikaans, Bulgarian, Czech, Greek, Estonian, Persian, Hebrew, Hindi, Croatian, Hungarian, Indonesian, Japanese, Korean, Lithuanian, Latvian, Macedonian, Portuguese (Brazilian), Slovenian, Serbian (Latin), Thai and Urdu languages' coverage for incident translations. |
| 2025-05-16 | Added | Added typeDescription field in incident response to support incident type translations. |
| 2024-01-11 | Added | Added support for using POST method to pass all parameters as JSON data. |
| 2024-01-11 | Added | The new method helps avoid the situation which API request sometimes has a too large value for URI length limit (i.e. 1000 characters). That is likely to be the case for request by topology segment reference. |
| 2022-05-19 | Changed | The /incidents/{originalId} endpoint now accepts a namespace prefix. If a namespace is not specified, here:traffic:incident is assumed by default.Both variants are accepted: - here:traffic:incident:3879526487457467809- 3879526487457467809 |
| 2022-05-19 | Changed | Response JSON will now contain also HRN notation for both id and original_id. |
| 2022-05-19 | Added | Serbia, Montenegro and Bosnia coverage for flow events. |
Updated 25 days ago
Did this page help you?