Search Endpoints

5min

API changes: New ID ordering logic in the API Search response
Impacted endpoints: All API Search endpoints
Impact: Updated Search Filter and ES DSL
Release date: March 19th, 2025
Ordering logic 
Following a release on March 19th, the default ID ordering in Search response body will change:
Before: ascending by ID
After: descending by last_updated
New formats
Based on this change, some alterations will also be present in pagination and 
x-next-page-after request header usage:
Search Filter
Due to a new ordering, sequencing request header x-next-page-after will accept input in an updated format.
﻿
Before
After
Change
Ascending by ID
Descending by last_updatedand ID
Accepted format
123
"2025-01-01",123
ES DSL
Using sorting with the x-next-page-after request header in ES DSL will return an updated format.
﻿
Before
After
Returned format
0.345,123
0.345,"2025-01-01",123
Backwards compatibility
You might prefer to maintain the current ordering logic. This will be possible using the following ways:
Type
Option
Search Filter Endpoints
Use a new query parameter ?sort=id, which will be added to the queried endpoint
ES DSL Endpoints
Pass "sort": ["id"] along with the "query"
﻿

	Before	After
Change	Ascending by ID	Descending by last_updatedand ID
Accepted format	123	"2025-01-01",123

	Before	After
Returned format	0.345,123	0.345,"2025-01-01",123

Type	Option
Search Filter Endpoints	Use a new query parameter ?sort=id, which will be added to the queried endpoint
ES DSL Endpoints	Pass "sort": ["id"] along with the "query"

Clean Company API

Multi-source Company API (cloned)