Sequence diagram
2 min
Overview
The following diagram illustrates the complete end-to-end provisioning flow. It visually demonstrates how a partner system must interact sequentially with both platforms: first with the Legacy API for tenant creation and license assignment (Phase 1), and subsequently with the Cloud API for configuring filtering policies and activating networks (Phase 2).
Sequence Diagram
sequenceDiagram
autonumber
participant P as Partner system
participant L as Legacy API<br/>api.fsflt.net
participant N as Cloud API<br/>core.fsflt.net
Note over P,L: Phase 1 — tenant and licensing (X-API-KEY)
P->>L: POST /customerarea/customers/new
L-->>P: customer_code
P->>L: GET /customerarea/licenses/available
L-->>P: license catalogue
P->>L: POST /customerarea/licenses/assign
L-->>P: license_id, expiry_date
P->>L: GET /customerarea/customers/list
L-->>P: organization_id + migration_status
Note over P,N: Phase 2 — filtering configuration (x-api-key)
P->>N: POST /authentication/v1/login
N-->>P: accessToken, user.apiKey.value, organizationId
P->>N: POST /protection/v1/policies {organizationId}
N-->>P: policyId
P->>N: POST /protection/v1/policies/{policyId}/categories/blocked
N-->>P: 207 successes[]
P->>N: PATCH /protection/v1/policies/{policyId}/settings
P->>N: POST /network/v1/static/single {organizationId}
N-->>P: networkId
P->>N: GET /network/v1/{networkId}/dns/available
N-->>P: dnsId
P->>N: POST /network/v1/{networkId}/policies {policyId, dnsId}
N-->>P: binding + DNS addresses
P->>N: GET /network/v1?organizationId=...&includePolicies=true
N-->>P: verified configuration