Create a POP account and activate SdI/PEPPOL by talking to an AI assistant

Goal

Create a new POP account and activate SdI (Italy/San Marino) or PEPPOL (rest of the EU) entirely in chat with an AI assistant connected to the remote MCP server — without opening popapi.io or filling out any form.

Prerequisites

• An MCP client connected to https://mcp.popapi.io/mcp (see mcp-remote) — for this flow you don’t need a license_key yet, so you can connect even without an account.
• A valid, reachable email address.

The flow (5 steps)

The assistant will use these 5 tools, in order:

1. pop_onboarding_request_otp — ask the assistant to start registration with your email. If the account doesn’t exist, it’s created automatically. The OTP code is also sent by email, but the assistant already receives it in the response.
2. pop_onboarding_verify_otp — give the assistant the OTP code (expires in 10 minutes): in return you get a temporary onboarding_token (valid 30 minutes), which the assistant will use for you in the following steps.
3. pop_onboarding_get_status (optional) — to check where you stand before proceeding.
4. pop_onboarding_get_account_setup — the assistant retrieves the fields still to fill in (country, company name, VAT number, tax regime, etc.) and the allowed values (e.g. the list of tax regimes for your country).
5. pop_onboarding_save_account_setup — provide the missing data (in natural language, the assistant translates it); at this point you can also ask to activate SdI or PEPPOL in the same request.

Activating SdI or PEPPOL in the same flow

• SdI (IT/SM accounts only) — ask to activate it: the assistant sets active_sdipop_integration = 1 and active_peppol_integration = 0.
• PEPPOL (other EU countries) — ask to register the PEPPOL legal entity: you’ll need address, city, zip code, and the PEPPOL scheme/identifier — the assistant retrieves these from the step-4 lookups if you don’t know them off-hand.
• SdI and PEPPOL are mutually exclusive: you can’t activate both on the same account.

After activation

Once the wizard is complete, get your license_key from Account > API on popapi.io (see get-your-license-key) to start generating invoices — that’s the key you’ll use to authenticate “normal” calls (invoice creation), different from the onboarding_token used only during this flow.

Good to know

• None of the 5 onboarding tools require the Authorization: Bearer header — they only use onboarding_token (or nothing, in the first step).
• If you have an administrator account, you won’t receive an OTP: use your admin password as the “OTP” in step 2.
• Once wizard_completed is true, calling save again doesn’t overwrite anything: it just returns the current state.
• PEPPOL fields, once the legal entity is registered, stay permanently locked (not self-editable).

Common errors

• Expired OTP — you waited more than 10 minutes between request and verification: restart from step 1.
• Expired onboarding_token — more than half an hour has passed since step 2: there’s no refresh, you restart from the OTP request.
• VAT number already in use — 422 error during save: that VAT number is already linked to another account on the chosen environment (live/sandbox).
• Locked field can’t be changed — some fields stay fixed after the first save (e.g. country, or all PEPPOL fields after registration): open a support ticket to change them.

Related configuration

For the technical detail of the underlying protocol (same flow, direct REST calls) see api/onboarding. To connect the assistant see mcp-remote.