datawebotAllegro product data: marketplace offers, API access and regional prices
Allegro’s product catalog and seller offers are related but different records. For a useful comparison, keep the product identity separate from each offer, then preserve marketplace, delivery country, currency and language. Allegro documents OAuth-protected API routes, while its current terms restrict reuse of site materials and data.
Choose the API route by whose data you need
Marketplace search · seller-owned offers · permissionSearch offers by market
Allegro documents GET /offers/listing for offers visible on a selected marketplace. The API uses OAuth; set the market and query context before comparing results.
Read your own offers
GET /sale/offers returns offers for the logged-in seller who created them. A seller-authorized token is required; this endpoint does not expose another seller’s account. Its isFulfillment field identifies One Fulfillment warehouse handling.
Check rights separately
The English terms require Allegro consent to download or use materials and restrict commercial aggregation, including scraping. OAuth is an access method, not a reuse license.
Start with Allegro’s REST API reference ↗, the OAuth guide ↗ and the current English Terms & Conditions ↗.
Separate the catalog product from each Allegro offer
Allegro connects marketplace offers to catalog products, but the records answer different questions. A product identifier can help align the item; each offer belongs to a seller and carries its own commercial terms. Keep both identifiers and their observed market context.
Scroll to compare →
| Record | Useful fields to retain | Comparison rule |
|---|---|---|
| Catalog product | Product ID or GTIN when returned, category, title and source-provided parameters | Use as a candidate identity match; do not attach one seller’s price or availability to every offer for that product. |
| Marketplace offer | Offer ID, seller reference when available, product link, selling format, displayed price and currency | An offer is the seller’s commercial listing; keep separate offer IDs even when product titles or GTINs match. |
| Fulfillment operator | For seller-owned offers, the `isFulfillment` flag when returned | Allegro documents `true` for an offer handled by its One Fulfillment warehouse and `false` for seller-handled fulfillment. Keep this seller-offer field distinct from delivery-country eligibility. |
| Offer-to-product link | The returned product ID plus the offer ID and selected variation or parameters | Preserve missing or ambiguous links instead of forcing a catalog match. |
| Observation | Marketplace, request filters, source URL and retrieval timestamp | A listing is a time-bound result, not a durable promise of price, delivery eligibility or stock. |
Carry the selected marketplace into every price comparison
Allegro documents offer search across national marketplaces. Its listing API can take a marketplace, delivery-country and currency context; the response language also depends on the requested marketplace and Accept-Language. A price comparison without those inputs can mix unlike observations.
Scroll to compare →
| Context | Record alongside the offer | Why it changes the comparison |
|---|---|---|
| Marketplace | marketplaceId and the corresponding Allegro national domain | The API defaults to allegro-pl when no marketplace is selected; use GET /marketplaces to check supported values. |
| Delivery destination | shipping.country plus the intended buyer market | Allegro says changing the delivery country can affect available offers, services and delivery options. |
| Price denomination | Raw displayed amount, currency and observation time | Currency varies by marketplace. Store the source amount first; add any converted value as a separate calculation with its FX rate and timestamp. |
| Language | Accept-Language sent and language returned | The default response language follows the selected marketplace; unsupported language choices fall back to that market’s default. |
Choose an authorized API route and check reuse terms
Allegro’s REST API is OAuth-protected. The marketplace search resource and seller account resources are not interchangeable: seller offer-management endpoints return the authorized seller’s own records. API authentication also does not by itself grant rights to reuse website materials.
Scroll to compare →
| Question | Documented route or rule | Scope boundary |
|---|---|---|
| Search offers visible on a chosen market | GET /offers/listing with the marketplace and query filters appropriate to the request | Use Allegro’s current API documentation and OAuth flow; do not treat a successful response as permission to republish content. |
| Read a seller’s own offer catalog | GET /sale/offers and offer-detail resources with an authorized seller token | Allegro describes /sale/offers as offers of the logged-in user; it is not an endpoint for another seller’s account. |
| Reuse product-page material in a commercial dataset | The English Terms & Conditions, valid from September 1, 2026, require Allegro consent to download or use materials and prohibit aggregation or processing for business reuse, including scraping | Confirm written permission and the current terms for the intended use. The API’s OAuth requirement is not a blanket content license. |
Content reviewed 2026-10-02.
Allegro product data questions
Does Allegro provide an API for product and offer data?
Allegro documents GET /offers/listing for marketplace offer search and seller resources such as GET /sale/offers. Allegro says REST API requests require an OAuth bearer token. Check the current method documentation for parameters, permissions and response fields.
Can GET /sale/offers return another seller’s catalog?
No. Allegro describes GET /sale/offers as the offer list for the logged-in user and says the caller must be authorized as the seller who created those offers. Marketplace search and a seller’s account records are separate access paths.
How should I compare Allegro prices across markets?
Keep marketplaceId, delivery country, source currency, response language, offer ID and observation time with each price. Allegro documents these market parameters for offer search, and its terms say country, transaction currency or language can affect offers, services and delivery options.
Does a matching Allegro product ID make two offers equivalent?
No. A catalog product helps identify the item, while each offer carries seller-specific terms such as its selling format and displayed price. Compare offer records separately and preserve the product-to-offer relationship instead of merging their commercial fields.
What does Allegro’s isFulfillment field mean?
For seller-owned offers, Allegro uses isFulfillment to distinguish offers handled through One Fulfillment by Allegro from offers handled by the seller: true means the Allegro warehouse, and false means the seller. Keep this handling field with its offer record.
Do Allegro’s terms allow automated scraping for commercial reuse?
The English Allegro Terms & Conditions valid from September 1, 2026 require Allegro’s consent to download or use materials and prohibit aggregating or processing Allegro data for business reuse, including scraping. Review the current terms and obtain the required permission for the intended use; OAuth authentication alone is not a reuse license.