Affilitizer has updated the default sorting behavior for affiliate program results returned through both the HTTP API and the Model Context Protocol (MCP). Under this revised arrangement, queries across both interfaces automatically present program records with the newest start dates first, changing the default order from the previous implementation.
What changed
- The default sorting behavior for affiliate program results across the HTTP API and the MCP now presents records ordered by the latest start dates first rather than by update history.
- Callers can explicitly supply the parameter
sort=createdAtto filter or order results to locate recently added program listings in the database. - Users can apply the query parameter
sortOrder=ascto invert the output sequence and view the oldest records first. - Existing pipelines and integrations that depend on the previous default behavior can maintain their original sorting structure by supplying both
sort=updatedAtandsortOrder=ascon requests.
Why it matters
This update alters how affiliate program records are organized in programmatic responses across the HTTP API and MCP tools. For publishers, developers, and advertisers monitoring new commercial partnerships, recent program start dates are now delivered first without requiring custom sorting logic. Meanwhile, organizations and automated ingestion services that rely on the prior default ordering can preserve consistency in their tracking systems by incorporating sort=updatedAt and sortOrder=asc into their integration requests.
Announced on the Affilitizer Changelog.
This article was created with AI assistance and editorially reviewed.
