---
title: Sequence diagram
slug: sequence-diagram
createdAt: 2026-11-02T08:43:01.065Z
---

## 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

:::BlockQuote
sequenceDiagram
    autonumber
    participant P as Partner system
&#x20;   participant L as Legacy API\<br/>api.fsflt.net
&#x20;   participant N as Cloud API\<br/>core.fsflt.net

&#x20;   Note over P,L: Phase 1 — tenant and licensing (X-API-KEY)
&#x20;   P->>L: POST /customerarea/customers/new
&#x20;   L-->>P: customer\_code
&#x20;   P->>L: GET /customerarea/licenses/available
&#x20;   L-->>P: license catalogue
&#x20;   P->>L: POST /customerarea/licenses/assign
&#x20;   L-->>P: license\_id, expiry\_date
&#x20;   P->>L: GET /customerarea/customers/list
&#x20;   L-->>P: organization\_id + migration\_status

&#x20;   Note over P,N: Phase 2 — filtering configuration (x-api-key)
&#x20;   P->>N: POST /authentication/v1/login
&#x20;   N-->>P: accessToken, user.apiKey.value, organizationId
&#x20;   P->>N: POST /protection/v1/policies &#x7B;organizationId}
&#x20;   N-->>P: policyId
&#x20;   P->>N: POST /protection/v1/policies/&#x7B;policyId}/categories/blocked
&#x20;   N-->>P: 207 successes\[]
&#x20;   P->>N: PATCH /protection/v1/policies/&#x7B;policyId}/settings
&#x20;   P->>N: POST /network/v1/static/single &#x7B;organizationId}
&#x20;   N-->>P: networkId
&#x20;   P->>N: GET /network/v1/&#x7B;networkId}/dns/available
&#x20;   N-->>P: dnsId
&#x20;   P->>N: POST /network/v1/&#x7B;networkId}/policies \{policyId, dnsId}
&#x20;   N-->>P: binding + DNS addresses
&#x20;   P->>N: GET /network/v1?organizationId=...\&includePolicies=true
&#x20;   N-->>P: verified configuration
:::