Organization::ACCOUNT → Organization::GROUP (required) → Organization::UNIT.Asset::TENANT → Asset::GROUP (optional) → Asset::UNIT.
From SIGN IT 2026-02-03 onwards
By default, your integration needs your Organization::ACCOUNT and an Organization::GROUP (required) — both created via the fiskaly HUB — and Organization::UNITs representing each of your clients, created via the SIGN IT API.
In most cases, a single Group per country is sufficient (e.g. if you intend to support fiscalization in Italy and France, you may create one Organization::GROUP for Italy and one for France).
However, if your internal organization needs a further level of structuring within a country — for example, to separate taxpayers by brand, region, etc. — you can add an additional level by creating a sub-group (a Group nested inside another Group).
Account (main organization)
|
+-- Group ("France")
| |
| +-- Unit ("taxpayer 1")
|
+-- Group ("Italy")
|
+-- Sub-group ("Brand A")
| |
| +-- Unit ("taxpayer 2")
| +-- Unit ("taxpayer 3")
|
+-- Sub-group ("Brand B")
|
+-- Unit ("taxpayer 4")Note: Currently, sub-groups can only be created via API. Support for creating sub-groups directly from the fiskaly HUB may be introduced in future releases. However, once created, sub-groups are already visible in the HUB.
Step-by-step guide
-
Call
createOrganizationwithtype: GROUP, authenticating with the bearer token of the parentGroup(the one created via the fiskaly HUB). TheGroupID is returned incontent.id{ "content": { "type": "GROUP", "name": "name-your-sub-group-here" } } - Call
createOrganizationwithtype: UNIT, making sure to set the sub-group's ID (from step 1) as theX-Scope-Identifierheader. This ensures the Unit is created directly under the Sub-group.
Note: If X-Scope-Identifier is not provided, the Organization::UNIT is created directly under the parent Group (the one created via the fiskaly HUB) by default, via the bearer token used.
Up to SIGN IT 2025-08-12
By default, your integration only needs your main organization (created via the fiskaly dashboard) and Asset::UNITs representing each of your clients (created via the SIGN IT API).
If your structure requires more flexibility, you can introduce an optional intermediate layer, Asset::GROUP, to organize multiple Asset::UNITs into logical groupings.
Tenant (main organization)
|
+-- Group (optional layer)
| |
| +-- Unit ("taxpayer 1")
| +-- Unit ("taxpayer 2")
|
+-- Unit ("taxpayer 3")
|
+-- Unit ("taxpayer 4")
Step-by-step guide
-
Call
createAssetwithtype: GROUP, authenticating with the bearer token of the main organization (the one created via the fiskaly Dashboard). TheGroupID is returned incontent.id{ "content": { "type": "GROUP", "name": "name-your-asset-group-here" } } - Call
createAssetwithtype: UNIT, making sure to set theAsset::GROUPID (from step 1) as theX-Scope-Identifierheader. This ensures the Unit is created directly under the Group.
Note: If X-Scope-Identifier is not provided, the Asset::UNIT is nested directly under the main organization (Asset::TENANT) by default, via the bearer token used.
To learn more about the terminology and structure changes between versions, see: SIGN IT: New Resource Terminology.