Submit the activation request form required for provider activation.
Submits the activation request form for a specific provider. TheDocumentation Index
Fetch the complete documentation index at: https://docs.hopae.com/llms.txt
Use this file to discover all available pages before exploring further.
data object must contain all fields listed in the provider’s requiredFields (from Get Activation Steps).
A form can only be submitted once per provider. If the form was previously rejected, it can be resubmitted.
Bearer <API_KEY> from Console > Developers > Workspace API Keys.application/jsonsmartid, spid-ig, no-bankid).steps[].requiredFields on the activation-form step — that is the authoritative list. Submitting without the expected fields returns 400 VALIDATION_MISSING_PARAMETER. Empty strings, whitespace-only values, and null are also treated as missing — the server trims and rejects them, not just absent keys.requiredFields from Get Activation Steps to determine which fields to submit.| Field | Type | Description |
|---|---|---|
legalCompanyName | string | Full legal name of the company as shown on official incorporation documents. |
displayName | string | Short brand name shown to end users during verification (e.g., on consent screens). |
logo | base64 | Base64-encoded PNG or SVG logo (max 256KB). |
registrationNumber | string | Company registration number from your country’s business registry (e.g., RCS, HRB, CVR). |
registeredAddress | string | Full registered business address including street, city, postal code, and country. |
vatNumber | string | EU VAT identification number including the country prefix (e.g., DE123456789). |
serviceDescription | string | One-sentence description of your service, shown during provider activation review. |
websiteUrl | url | Public website URL. |
contactEmail | Operations contact email. Required for all providers — used for activation status notifications. | |
contactPhone | string | Operations contact phone in international format. |
SPID provider-specific fields
| Field | Type | Description |
|---|---|---|
userDataLevel | string | SPID data retrieval scope. Allowed values: basic (name, surname, fiscal code, date of birth), advanced (adds place of birth, gender, document details, phone, email, registered address). |
iDIN provider-specific fields
| Field | Type | Description |
|---|---|---|
legalRepName | string | Full legal name of the authorized iDIN legal representative. |
legalRepEmail | Email of the authorized iDIN legal representative. | |
legalRepPhone | string | Phone of the authorized iDIN legal representative. |
BankID Norway provider-specific fields
| Field | Type | Description |
|---|---|---|
bankName | string | Name of the primary bank partner for Norwegian BankID integration. |
useSsn | boolean | Whether you need the end-user Norwegian social security number (fødselsnummer). Requires legal basis when true. |
ssnReason | string | Short justification for requesting the SSN. Required when useSsn is true. |
gdprArticle | string | GDPR legal basis for processing the SSN. Allowed values: GDPR Art. 6(1)(a) - Consent, GDPR Art. 6(1)(b) - Contractual Performance, GDPR Art. 6(1)(c) - Legal Compliance, GDPR Art. 6(1)(f) - Legitimate Interest. |
signatoryName | string | Full name of the person signing the BankID NO service agreement on behalf of your company. |
signatoryEmail | Email of the BankID NO signatory — must be reachable for the signing workflow. | |
signatoryPhone | string | Phone of the BankID NO signatory. |
BankID CZ provider-specific fields
| Field | Type | Description |
|---|---|---|
privacyPolicyUrl | url | Link to your privacy policy page — shown to end users before verification. |
termsOfServiceUrl | url | Link to your terms of service page. |
true, matching fields are also persisted to the app’s company information. Defaults to false. Any field saved this way is prefilled into the requiredFields[].value returned by Get Activation Steps for subsequent providers on the same app, so your users don’t have to re-enter shared details (legal company name, address, contact email, etc.) for every provider they activate.submitted on a successful submission. Review outcomes (approval, rejection) are observed via Get Activation Steps, not this endpoint.