Courier Messages Endpoint and Pagination Behavior

Ory Kratos removes the X-Total-Count HTTP response header from the /admin/courier/messages endpoint.
This change eliminates an expensive linear database scan previously required to compute message counts, improving request performance and scalability.

Pagination now operates without a total count. Clients should detect the last page when the number of returned items is smaller than the requested page size. Due to the real-time nature of courier messages, repeated queries with identical filters may return varying results as new messages are created or processed.

A new configuration option, secrets.pagination, defines encryption keys used for encoding and decoding pagination tokens.
These keys are not security sensitive and exist to decouple API clients from the internal pagination implementation.
If unset, Kratos transparently uses a fallback key.

See Kratos API Documentation for details on updated pagination behavior.

This update is available now on Ory Network, Ory Kratos Enterprise, and will be included in the next Ory Kratos release.