Admin Panel API — 2.4.2 → 2.5.0 (Integrator Migration Guide)
Previous Release: 2.4.2 · New Release: 2.5.0
Audience: external integrators and service-to-service consumers of the Admin Panel API — service accounts, provisioning automation, and integration tooling.
Please review each section before upgrading.
1. Summary — What Actually Affects You
In plain terms: neither item here is urgent. The pagination change only bites integrations that were already sending malformed parameters and quietly getting away with it — a well-formed request sees no difference. The deprecation is on a brand-new endpoint introduced this same cycle, so no existing integrator is using the old form yet; it's a heads-up for anyone about to integrate, not a migration.
Change | Who is affected | Action | Practical impact | Why this was changed |
|---|---|---|---|---|
Malformed pagination/filter params now return | Anyone sending malformed | Fix the request; well-formed requests are unaffected | 🟢 Low. Only breaks requests that were already malformed. A well-formed request behaves exactly as before. | The old behaviour silently treated a malformed value as "not provided" and returned the entire unfiltered list instead of erroring — a client with a params bug got an oversized, unexpected response instead of a clear failure. Returning |
| New Token Factory integrations only | Use the query-param form | ⚪ None yet. The endpoint launched this same cycle, so no existing integrator is using the old form. Just don't build against it. | The path-parameter form can't represent a HuggingFace model id containing a |
There are no removed endpoints and no breaking schema changes this release. 93 new endpoints were added (Token Factory, Advanced Networking, node logs, GPU visibility) — purely additive, no action needed to keep existing integrations working.
2. Breaking Change: List endpoints now reject malformed pagination/filter params
Before: an unparseable page, per_page, from_time, to_time, or log_id was silently treated as absent, and the endpoint returned the entire unfiltered list.
After:
GET /api/gpuaas?page=abc → 400 Bad Request
Migration: ensure these parameters are well-formed integers/timestamps before sending. If your integration never sends malformed values, there is nothing to change.
3. Deprecation: hardware-options path form
GET /gpuaas/tf/catalog/models/{model_id}/hardware-options is deprecated in favor of:
GET /gpuaas/tf/catalog/models/hardware-options?model_id=...
The path form can't represent a HuggingFace model id containing a /. If you are integrating with Token Factory for the first time, start with the query form.
4. New Capabilities (informational, no migration required)
Token Factory — a new GPU inference/fine-tuning/RAG platform surface (catalog, deploy, chat, fine-tunes, RAG, fleet management).
Advanced Networking — VPCs, subnets, VLANs, and Elastic IPs as first-class API resources.
Both are purely additive; nothing about your existing integration changes because they exist.