Pagination and Filtering

In API v2, list methods are designed for simple automation and UI scenarios.

Basic approach

Where supported, use:

• limit
• offset

This is the most convenient model for Console, simple back-office integrations, and administrative scripts.

Useful filters for databases

For the list of tenant databases in the current public scenario, the following are especially useful:

• state
• name_prefix
• limit
• offset

This allows you to:

• filter only ready, stopped, or error databases;
• quickly find databases by technical prefix;
• build paginated lists in UI and internal tools.

Practical advice

• do not use very large limit values unless you actually need them;
• in automation, filter by tenant first, then by state or name;
• treat the list as dynamic: resource state can change between requests because of auto-start / auto-stop or asynchronous deletion.

For most user scenarios, this model is enough: it is simple, predictable, and well suited for resource catalogs.