The MyAdmin API provides multiple versions to support new features while maintaining backward compatibility. V3 is the recommended version for all new integrations, as it is designed for scalability and robust, paginated data retrieval.
/v3/MyAdminApi.ashx): The modern, recommended endpoint. It's built for performance and handles large datasets using pagination./v2/MyAdminApi.ashx): A legacy endpoint. It remains available for existing integrations but is not recommended for new development and lacks pagination.The most critical part of working with our API is understanding that not all methods have been migrated to V3.
Before using a method, you must check its specific documentation. On our API Reference page, we indicate the version support for each method using visual tags.
The V3 endpoint is the preferred and most robust version for interacting with the MyAdmin API. It is engineered to handle all data requests, especially large collections, with high performance.
Base URL: /v3/MyAdminApi.ashx
The primary advantage of V3 is its built-in pagination, which is required for retrieving lists of data. This is handled via a pagination object in your JSON request.
For a detailed guide on all pagination features (including keyset vs. offset), see the Pagination section under Concepts.
Default rate limits apply to v3 endpoints; however, this policy is subject to change. For more details, please see the Working with Rate Limits section.
The V2 endpoint is a legacy endpoint and is not recommended for new integrations, especially those retrieving lists of data.
Base URL: /v2/MyAdminApi.ashx
To ensure system stability, the v2 endpoint is subject to combination of request-based and data-based rate limiting. Exceeding these limits will result in an HTTP 429 error. For a detailed explanation of how these limits work, For more information, see the Working with Rate Limits section.
The v2 endpoint does not support built-in pagination. Attempting to retrieve a large dataset in a single v2 call will likely result in a timeout or other processing errors.
| Feature | v2 Endpoint (Legacy) | v3 Endpoint (Recommended) |
|---|---|---|
| Recommendation | Not for new development. | Strongly recommended for all new integrations. |
| Primary Use Case | Legacy support. | All new projects, especially those retrieving lists/collections. |
| Pagination | No | Yes (Built-in, required for lists). |
| Rate Limiting | Yes | Yes (Default rate limits) |