Allegro: keys, OAuth authorisation and synchronisation

What it is for

The Allegro connector fetches orders from your seller account, sends listing stock levels (and optionally prices) and passes on parcel numbers. It uses the official Allegro REST API and OAuth authorisation, so Zaksio never sees the password to your Allegro account.

Where to find it in the app

Sales and logistics, "Sales channels", "Add sales channel", type "Allegro". Then the "Connection" tab with the fields "Client ID", "Client Secret" and "Environment" (choose "Production (allegro.pl)" or "Sandbox (allegro.pl.allegrosandbox.pl)").

Where to get the Client ID and Client Secret

1. Log in to the seller account and go to apps.developer.allegro.pl (for the sandbox: apps.developer.allegro.pl.allegrosandbox.pl).
2. Add a new app: enter a name and select the type with browser access (authorisation code). The device flow also works if the app has the "Device flow" option enabled. Type names on the Allegro side are sometimes changed.
3. In the Redirect URI field, enter exactly the address that Zaksio shows when connecting the account. Allegro requires a character-for-character match, including the trailing slash.
4. The app needs these scopes: profile read, order read and write, and listing read and write (allegro:api:profile:read, allegro:api:orders:read, allegro:api:orders:write, allegro:api:sale:offers:read, allegro:api:sale:offers:write). Returns use order read access.
5. Copy the Client ID and Client Secret into the form in Zaksio, choose the environment and click "Save credentials".
6. Authorise your Allegro account and approve the access scopes on the Allegro website, then click "Check connection" when you return. You should see "Connected as" with your login.

Official guide: developer.allegro.pl, the "Authentication and authorisation" tutorial. The look of the Allegro panel may have changed since this article was written.

Two ways to authorise

• Authorisation code with PKCE: Zaksio redirects you to Allegro, you approve access and return to the app. Requires a registered redirect URL. The one-time "state" identifier is valid for 10 minutes.
• Device code: Zaksio shows a short code and an address that you enter on the Allegro website. No redirect is needed, and Zaksio checks in the background whether you have approved access.

Tokens are stored encrypted and refreshed automatically. The Allegro refresh token expires after 3 months, and each one is single-use, so after a longer break you need to reconnect the account from scratch.

Sandbox

Sandbox is a separate Allegro test environment. Production accounts do not exist there, so create an account on allegro.pl.allegrosandbox.pl and an application on apps.developer.allegro.pl.allegrosandbox.pl, and in Zaksio choose the "Sandbox" environment. Client ID and Client Secret from production do not work on the sandbox, and vice versa.

What it synchronises

• Orders: from the "ready for fulfilment" event (paid online or cash on delivery). Unpaid ones appear after payment. Allegro makes events available for 60 days. Cancelling before shipment cancels the order in Zaksio.
• Listings: a list to map. The Allegro list usually does not contain EAN, so matching relies on the SKU entered in the listing as the external ID.
• Stock levels: sent with bulk commands, with a result for each listing. A stock level of 0 ends the listing on Allegro.
• Prices: only when you enable the channel setting "syncPrices", for the Allegro.pl marketplace.
• Tracking number: passed to Allegro after shipping in Zaksio.
• Returns: a return reported on Allegro notifies the team.