Flowwise Sync for Allegro brings a seller's Allegro orders into their own Shopify store and sends the tracking numbers back to Allegro. This page explains how the application uses the public Allegro REST API, how sellers sign in and how it follows the Allegro REST API Terms and Conditions.
| Application | Flowwise Sync for Allegro |
|---|---|
| Operated by | Newcraft, as part of Flowwise (flowwise.dev) |
| Used through | The Shopify app Allegro Sync Pro and the Flowwise web app at app.flowwise.dev |
| User-Agent | Flowwise-Sync-for-Allegro/1.0 (+https://app.flowwise.dev/docs/allegro-api/) |
| API hosts | allegro.pl (sign-in) and api.allegro.pl |
| Contact | Through Flowwise support in the app, or flowwise.dev/contact |
The application serves Allegro sellers who also run a Shopify store. It does three things for the seller who connected their own Allegro account:
Orders fulfilled by Allegro One Fulfillment are not shipped by the seller, so the application never reports a shipment for them. The application only works with the seller's own account. It does not read other sellers' data, does not scrape allegro.pl and does not message buyers.
The application uses Allegro's OAuth 2.0 authorization code flow. The seller's Allegro password never reaches us.
https://allegro.pl/auth/oauth/authorize with
prompt=confirm and a signed, time-limited state that ties the answer to that seller's
shop and user.https://app.flowwise.dev/embedded/allegro/oauth/callback. The application
checks the state, exchanges the code at https://allegro.pl/auth/oauth/token and reads
GET /me to show which Allegro account was approved.| Scope | Why |
|---|---|
allegro:api:profile:read | Identify the connected seller account (GET /me). |
allegro:api:orders:read | Read order events and checkout forms to import orders, and read carriers and existing shipments. |
allegro:api:orders:write | Add shipment tracking and set the fulfillment status to sent. |
allegro:api:sale:offers:read | Read the seller's own offer to find the SKU and EAN of an order line. |
All requests use Accept: application/vnd.allegro.public.v1+json and the User-Agent shown above.
| Request | Used for |
|---|---|
GET /me | Identify the seller after sign-in. |
GET /order/event-stats | Find the latest order event when the import starts. |
GET /order/events | Find orders that changed since the last check (100 per page). |
GET /order/checkout-forms | Find recent orders that are ready for processing (at most the last 7 days) when a seller first connects. |
GET /order/checkout-forms/{id} | Read one order to create it in Shopify, or to check its status before reporting a shipment. |
GET /sale/product-offers/{offerId} | Read the SKU, EAN and title of an ordered offer. Cached per offer during one run. |
GET /order/carriers | Map the Shopify carrier to an Allegro carrier id. |
GET /order/checkout-forms/{id}/shipments | Check which tracking numbers are already on the order, so no shipment is added twice. |
POST /order/checkout-forms/{id}/shipments | Add the carrier, tracking number and shipped line items. |
PUT /order/checkout-forms/{id}/fulfillment | Set the order status to SENT when every line has shipped. |
429 or a server error the request is retried later with an increasing delay. A
401 refreshes the token once; if that fails, the seller is asked to connect again.To create the order in Shopify, the application uses the order number, line items, prices, delivery method, the buyer's name, delivery address, email address and phone number. It stores the imported orders and their status so the seller can see them and so no order is imported twice.
| Requirement | How the application meets it |
|---|---|
| Identify the application (art. 3.4 c and h) | Every request, including token requests, sends User-Agent: Flowwise-Sync-for-Allegro/1.0 (+https://app.flowwise.dev/docs/allegro-api/). Only the version number changes between releases. |
| Keep the API key to ourselves (art. 3.9 and 3.10) | The client id and secret are held only on our servers and are never given to sellers or third parties. |
| Authorize users through Allegro (art. 4.1 d) | Sellers authorize only through Allegro's OAuth sign-in. The application has no sign-in of its own for Allegro accounts. |
| Inform users (art. 4.3) | This page, the terms and the privacy policy explain what the application does with the seller's data. |
| Act within the seller's permission | The application only reads and changes the connected seller's own orders and offers, and only within the approved scopes. |
| Use the API with care | Scheduled checks, paging, retry with backoff and caching keep the number of requests low. |