Overview
Overview
FlashStart currently exposes two independent APIs, served by two different platforms:
| Legacy CustomerArea API | Cloud Panel 2026 API |
|---|---|---|
Base URL | https://api.fsflt.net | https://core.fsflt.net |
Purpose | Customer (tenant) lifecycle and licensing | Filtering configuration: policies, networks, reports |
Authentication | X-API-KEY header | x-api-key header or Authorization: Bearer <JWT> |
Where to get the key | Legacy panel → Integrations > API → Request API Key | New panel → Integrations > API (or user.apiKey.valuefrom the login response) |
Tenant identifier | customer_code (integer) | organizationId (UUID v7) |
Filtering object | profile (profile_code, integer) | policy (policyId, UUID) |
Response envelope | {"code": 200, "content": ...} | Plain JSON / standard HTTP status codes |
Two different APIs, not two versions of the same API
The legacy API and the Cloud Panel API are separate products:
- Different hosts —api.fsflt.netvs vs core.fsflt.net.
- Different credentials — the legacy X-API-KEY does not work on the new platform, and vice versa. You need one key per platform.
- Different ID spaces — legacy uses integer customer_code/ profile_code/dns_id; the new platform uses UUIDs.
- Different resource models — legacy profiles are replaced by new policies; legacy networks must be re-created on the new platform.
- Different error conventions — legacy returns non-standard body codes (406, 409, 412, 416, 417…) and frequently HTTP 200 with an error inside content; the new API uses standard HTTP status codes plus 207 Multi-Status for batch operations.
Any integration must therefore handle two clients, two credentials and two identifier types, joined only by the organization_id field described in section 4.