Upcoming changes:

27SEP
2021

We have increased the limit of images in ads

From today, users with a company account who list their ads in the Automotive and Real Estate categories can add a maximum of 40 images to their offer. For users with a private account, the limit of 16 images remains the same.

22SEP
2021

Sandbox - on October 6th, 2021 we will update the list of categories and parameters and remove all offers

On October 6th, 2021 we will update the list of categories and parameters on Sandbox. This will allow us to ensure consistency between test and production environments.

Note! Due to the update, we will remove all offers from Sandbox.

21SEP
2021

We will change the names of the delivery methods

On October 4th, 2021, we will update the names of the delivery methods listed below, to be consistent with the other methods:

 Name of the method until 3.10.2021  Name of the method after 4.10.2021
 Kurier DTS  Allegro Zadbano (dawniej DTS)
 Allegro UPS Odbiór w Punkcie  Allegro Odbiór w Punkcie UPS
 UPS Odbiór w Punkcie  Odbiór w Punkcie UPS
 X-press Couriers  Allegro X-press Couriers
 X-press Couriers (z odbiorem zużytego  akumulatora)  Allegro X-press Couriers (z odbiorem zużytego  akumulatora)
 Allegro Przesyłka polecona  Allegro Przesyłka Polecona

We will also make the notation of COD delivery methods more consistent: "pobranie" will always be written at the end of the method name, with a lowercase letter.

The identifiers will remain the same.

You will find more information about this change on the seller’s page.

1SEP
2021

Size tables - we change the existing resource and add new resources to handle them

We have provided new resources to handle size tables:

In addition, for the existing size tables resources - GET /sale/size-tables/{tableId} and GET /sale/size-tables:

  • we added a new template.id field,
  • on December 1st, 2021 we will remove the "images" and "orientation" fields.

You will find more information about size tables in our guide.

26AUG
2021

On September 1st, 2021 we will change the names of Paczka w RUCHu delivery methods

On September 1st, 2021 we will adjust the names of delivery options, in regard to the change of the Paczka w RUCHu service into ORLEN Paczka.

Before change:

  • Allegro Paczka w RUCHu,
  • Paczka w RUCHu.

After change:

  • Allegro ORLEN Paczka,
  • ORLEN Paczka.

The identifiers will remain the same.

You will find more information about this change in Allegro Help.

24AUG
2021

We introduced new resources for managing Campaigns

As we announced before, today we have implemented new resources for processing offers submitted to campaigns, special programs and Allegro badges:

Today we also start to migrate all campaigns to the mechanism in which the Allegro Prices program already operates. You can read more about it in our announcement.

You can find more information about new resources in our guide.

18AUG
2021

We have introduced new statuses of most recent messages in the discussions in /sale/disputes resources

In response to your suggestions, we decided to improve the process of reading new messages in discussions. Therefore, starting today, we are returning two new fields:

  • "messagesStatus" - status of most recent message in the discussion,
  • "lastMessageCreationDate" - most recent message creation date.

Which resources are affected by these changes?

In addition, in the "messagesStatus" field we will return the following values:

  • "NEW" - new dispute (in which the seller has not responded yet),
  • "BUYER_REPLIED" - new message from buyer,
  • "SELLER_REPLIED" - new message from seller,
  • "ALLEGRO_ADVISOR_REPLIED" - new message from Allegro.

You will find more information about API discussions in our guide.

18AUG
2021

Similar categories - list your offer easier

When the product fits into a few similar categories, you can list an offer assigned to this product, but in another, similar category defined by us. You can read more about listing products in similar categories in our news.

We have introduced a change that makes it easier to list an offer in a similar category if:

  • you do not indicate a specific product in the request in the productSet[].product.id field,
  • based on the parameters sent in request, we matched a product that exists in our Product Catalog.

How has it worked so far?

To list in a similar category, it was necessary to indicate the category in the offer part of the request structure, in the category.id field.


What change have we made?

Currently, you can also indicate a category from a set of similar categories in the product part of the request, in the productSet[].product.category.id field:

Sample request structure:

{
    “productSet”: [{
        “product”:
            {
            “name”: “Sample product”,
            “category”: 
                {
                “id”: “99499”
                }, 
            ...
            }],
    ...
}
information

Note! If you indicate a specific product in the request in the productSet[].product.id field, then in order to list an offer in one of the similar categories - as before - you must pass this category in the offer part of the request structure, in the category.id field.


Why have we made the change?

We made the change based on observations of resource usage for listing offers related to a product. We want to make it easier to list offers in similar categories.

For more information on how to list an offer assigned to a product in a similar category, check out our guide.

10AUG
2021

Campaigns - we will make changes and add new features

On August 24th, 2021, we will add new resource operations for processing offers submitted to campaigns, special programs and Allegro badges:

  • PATCH /sale/badges/offers/{offerId}/campaigns/{campaignId} - command change of the price or end of the offer designation in the campaign:

    Sample request for price change:
    curl -X PATCH
    ‘https://api.allegro.pl/sale/badges/offers/12345678/campaigns/BARGAIN’ 
    -H ‘Authorization: Bearer {token}’
    -H ‘Content-Type: application/vnd.allegro.beta.v1+json‘
    -d ‘{
      "prices": {
        "bargain": {
          "value": {
            "amount": "9.99",
            "currency": "PLN"
          }
        }
      }
    }’
    
    Sample request for ending of the offer designation in the campaign:
    curl -X PATCH
    ‘https://api.allegro.pl/sale/badges/offers/12345678/campaigns/BARGAIN’ 
    -H ‘Authorization: Bearer {token}’
    -H ‘Content-Type: application/vnd.allegro.beta.v1+json‘
    -d ‘{
      "process": {
        "status": "FINISHED"
      }
    }’
    
    Sample response:
    {
      "id": "154179f0-ed4c-4b84-9260-302d2dec3801"      -- id of the operation
    }
    
  • GET ​/sale​/badge-operations​/{operationId} - check status of the price change or end of the offer designation in the campaign:

    Sample request:
    curl -X GET
    ‘https://api.allegro.pl/sale​/badge-operations​/154179f0-ed4c-4b84-9260-302d2dec3801’ 
    -H ‘Authorization: Bearer {token}’
    -H Accept: application/vnd.allegro.beta.v1+json‘
    
    Sample response:
    {
      "id": "154179f0-ed4c-4b84-9260-302d2dec3801",
      "type": "FINISH",
      "createdAt": "2021-08-09T12:49:17.347Z",
      "updatedAt": "2021-08-09T12:49:17.530Z",
      "campaign": {
        "id": "BARGAIN"
      },
      "offer": {
        "id": "12345678"
      },
      "process": {
        "status": "REQUESTED",
        "rejectionReasons": []
      }
    }
    

On August 24th, we will also start migrating all campaigns to the mechanism in which the Allegro Prices program already operates.


How does it work now?

When an offer is qualified for a campaign (apart from the Allegro Prices program), we also update the price in its structure. This change is visible in the sellingMode.price.amount field on the resource:

  • /sale/offers,
  • /sale/product-offers.

If the base price changes in the structure of an offer that is in a campaign - the badge is removed and the offer is excluded from the campaign.


What changes will we make?

From August 24th, 2021, if the offer is qualified for the campaign:

  • we will not update the price in its structure - the base price which we return in the sellingMode.price.amount field will remain unchanged,
  • if there is a change in the base price in the offer in the sellingMode.price.amount field during the campaign - offer will not be excluded from campaign,
  • GET /sale/offer-events response will also not return an event about a price change in an offer as a result of qualifying it for campaign.

Changing the price of an offer that is in a campaign or removing it from a campaign will be possible via PATCH /sale/badges/offers/{offerId}/campaigns/{campaignId}.


Why do we make the change?

We want to make it easier to manage offers in the campaigns and programs. With the change, sellers will be able to set a new price that will be valid only for the duration of the campaign or program and will be independent from the base offer price.

You can read more about campaigns and badges in the Allegro Help Center.

2AUG
2021

We have introduced resources for customer returns management

Today we have introduced new beta resources to help you handle customer returns via our API:

information

Note! To use the resources, pass the value ‘application/vnd.allegro.beta.v1+json’ in the Accept and Content-Type headers.

You will find more information about customer returns in our guide.

20JUL
2021

We have made changes to the terms of return policy

We have introduced the first stage of changes to the terms of return policy.

Which resources are affected by these changes?

What have we changed?

To the current structure:

  1. We added address validation for "countryCode": "PL".
  2. We added a new "contact" section with contact information - phone number and email address.
  3. We added a new "options" section.
  4. For value "range": "RESTRICTED":
    • in the restrictionCause.name field we added one value "VALUE_DEPENDENT_ON_FINANCIAL_MARKET" - "A service or item whose prices depend on fluctuations in the financial market over which the seller has no control and which may occur before the end of the withdrawal period, e.g., investment products: gold bars, collectible coins, silver, platinum."
    • we changed the descriptions for existing values in the restrictionCause.description field.

What do you need to adapt your returns policy to the changes?

Check the return addresses. When you create or edit a return policy, you will get an error if it does not match our guidelines (for "countryCode": "PL"):

  • city - only Polish letters (without zip code and special characters),
  • zip code - validation according to the pattern (dd [-] ddd),
  • street - without special signs, in accordance with the rules of carrier validation.

We added new fields and values to the existing structure. Please review them and make changes before October 2021 - before they become effective.

What will we change in October 2021?

  1. We will remove the "attachment" field.
  2. We will remove the "description" field and replace it with an optional "contact" object.
  3. Sending the full "options"structure will be obligatory.
  4. We will remove 3 values from restrictionCause.name:
    • "ALCOHOL",
    • "BOOKED_SERVICE",
    • "FULLY_IMPLEMENTED_SERVICE".

More information: documentation, our guide

Previous news:

- Changes to the terms of return policy (July 6th, 2021)

19JUL
2021

On September 30th we will remove POST /pricing/fee-preview

On September 30th, 2021 we will remove POST /pricing/fee-preview. This resource allows you to check fees we charge in a given category based on the specified conditions of the offer.

Use newer POST /pricing/offer-fee-preview, which allows you to see fees we will charge for a specific offer. All you need to do is provide the full body of the offer in the request structure.

Why are we removing a resource?

POST /pricing/fee-preview uses fields that currently do not affect the fees charged. At the same time, /pricing/offer-fee-preview replaces the /pricing/fee-preview resource - based on specific offer data, you will receive precise information about what listing fees we will charge.

For more information about POST /pricing/offer-fee-preview see our guide.

19JUL
2021

We have added resources for Message Center management

The Message Center is the place where the buyers and the sellers communicate each other. It is a combination of chat and e-mail, in which you will find correspondence conducted within Allegro, as well as messages from buyers.

Today, we released new resources to help you operate the Message Center via our API:

You can find more information about the Message Center in our guide.

16JUL
2021

On August 30th, we will increase the percentage of offers related to the Allegro Product Catalog

On August 30th, 2021 we will increase the the percentage of offers related to the Allegro Product Catalog in the following categories:

productization-table

Due to the nature of some subcategories in those categories, we cannot introduce those requirements in entire categories. In the Automotive category we have enabled the 1% requirement in 161 new subcategories. Check out a detailed list of subcategories where the requirement will apply.

information

Note! If a seller will not meet this condition, it will be not available to list new offers in those categories, if current offers are not assigned to a product.

You can find more information about how to assign an offer to a product in our guide. Check also POST /sale/product-offers resource, which allows you to list an offer assigned to a product with one request:

  • if the product already exists in our database, all you need to do is provide EAN code (or product ID), price and quantity,
  • if the product is not in our database, you need to provide product data, price, and quantity.

You can use GET /sale/offers with product.id.empty=true parameter to check which offers are not associated with a product.

15JUL
2021

We have introduced beta.v3 version of the /sale/product-offers resources

Today we have released a beta.v3 version of the /sale/product-offers resources and introduced the following changes:

  • for POST /sale/product-offers and GET /sale/product-offers/{offerId} - “product” field has been replaced with the “productSet” field, which is an array of objects. Currently, you can provide data only for one product in it.

    Sample request structure:
    {
            "productSet": [{
                    "product": 
                        {
                        "id": "bca3791d-a9f8-43e6-885f-c563b7fb30ee"
                        }
            }],
            "sellingMode": {
                "price": {
                    "amount": "220.85",
                    "currency": "PLN"
                }
            },
            "stock": {
                "available": 10
            }
    }
    
  • for PATCH /sale/product-offers/{offerId} - if the offer is ended and you will update the quantity for it to more than 0, we will not activate the offer - in this case, offer will remain in “ENDED” status.

To start using beta.v3, change the data in Content-Type and Accept headers to “application/vnd.allegro.beta.v3+json”.


Why did we release a new version of resources?

In the coming months we plan to introduce the possibility to define product sets, i.e. offers composed of few products. An example of such a set can be an offer that contains two items: a game console and an additional game. In this case, you will be able to define via POST /sale/product-offers two different products within one offer. The change in PATCH /sale/product-offers we introduced in response to your suggestions - to make it easier to manage offers.

information

Note! We plan to introduce the opportunity to define product sets only in /sale/product-offers resources. At the moment of implementing the feature, we will also add in the request structure the possibility of specifying the quantity of each product included in the set.

Owing to /sale/product-offers resources you can easily:

  • list a new offer connected with a product - all you have to do is provide an identifier of the product from our database or its EAN, price and quantity. You can also create your own product. If, based on the data provided, we recognize that the product is in our database, we will take its data and include it in your offer, other fields we will fill with default values,
  • update data in the offer - you do not have to send the whole offer structure, it is enough to provide only the field you want to change.

You can find more information about /sale/product-offers resources in our tutorial.

13JUL
2021

We have introduced scope for Message Center

According to our previous announcement, today we have introduced a new scope allegro:api:messaging, which is responsible for managing the Message Center.

It allows:

  • a view of the list of threads and messages,
  • creating, sending and deleting messages,
  • downloading and adding attachments to messages.

We are planning to implement the Message Center functionality in the coming days.

You will find more information about API Allegro scopes in our guide.

12JUL
2021

GET /payments/payment-operations - new group and types of operations

In August, we will enable sellers to block funds on Allegro Finance for automatic refunds to buyers. Sellers will be able to choose in My Allegro to block funds for returns and automatic refunds when returning goods.

What will we change?

On July 26th, in GET /payments/payment-operations we will expand:

  • paymentOperations[].group field with a new value: BLOCKADES,
  • paymentOperations[].type field by two new values:
    • BLOCKADE - the funds have been blocked for return,
    • BLOCKADE_RELEASE - the blockade has been released.

Sample response:

{
    "paymentOperations": [
        {
            "type": "BLOCKADE",                             
            "group": "BLOCKADES",                                  
            "wallet": {
                "paymentOperator": "PAYU",                      
                "type": "AVAILABLE",                                            
            "balance": {
                "amount": "3297.81",                       
                "currency": "PLN"
                }
            },
    ...                                         
} 

At the same time, we will add the ability to filter the results by a new group of operations:

GET /payments/payment-operations?group=BLOCKADES

Why will we make the change?

With the new group and operation types, the users will be able to see when and what funds have been blocked for automatic return. Sellers will also be able to recognize operations that have already been unlocked and can be paid out.

8JUL
2021

We have changed the approach in adding photos to offer connected with a product in the /sale/product-offers resources

In response to your suggestions, we decided to change the approach to adding photos to offer connected with a product in the /sale/product-offers resources.

How have we attached the product images so far?

If, based on the data provided, we recognize that the product is in our database, we automatically downloaded images from product data and attached them in the offer.

How do we manage the product images now?

We will not automatically include the recognized product images from our database, if you provide an empty array in the product.images field. In this case, we will only include offer images from the images section.

Sample request:

curl -X POST 
  'https://api.allegro.pl/sale/product-offers' 
  -H ‘Authorization: Bearer {token}’
  -H ‘Accept: application/vnd.allegro.beta.v2+json’ 
  -H ‘Content-Type: application/vnd.allegro.beta.v2+json’ 
  -d ’{
    "product": {
        "id": "990de42f-8a68-4f0c-aedb-060141ffd8e3",
        "images": []
    },
    ...
    "images": [
            "https://...image-address.jpeg",
            "https://...image-address.jpeg"
    ]
    ...
  }’
information

Note! If you will not provide your own offer description and the product:

  • indicated via product.id or
  • recognized based on given data (when you do not provide product.id)

in our database has it and there are images attached to it, we will include them along with the product description - even if you will provide an empty array in the product.images section. So if you want only your photos in offer, add your own description.

You can find more information about this change, along with sample requests, in our tutorial - how to handle images when you:

7JUL
2021

GET /sale/offer-events - new external.id field

Following your suggestions, today we implemented a change to the event log in offers (GET /sale/offer-events). In response, we return a new external.id field. It will indicate what value is set in the external.id field of the offer that the event is related with.

Sample response:

{
  "id": "MTEzMjQzODU3NA",
  "occurredAt": "2021-07-07T15:00:43.891Z",
  "type": "OFFER_ACTIVATED",
  "offer": {
    "id": "2865624934",
    "external": {
      "id": "externalId"
    }
  }
}
6JUL
2021

Changes to the terms of return policy.

In October 2021, we will change the process of returning items on Allegro and the return policy form. Already in July, we will introduce changes to the Allegro API so that everyone has time to adapt their application.

Which resources are affected by these changes?

What will we change from July 20th, 2021?

To the current structure:

  1. We will add address validation. For "countryCode": "PL":
    • city - only Polish letters (without zip code and special characters),
    • zip code - validation according to the pattern (dd [-] ddd),
    • street - without special signs, in accordance with the rules of carrier validation.
      
                   "address": {
                       "name": "Allegro.pl Sp. z o.o.",
                       "street": "Grunwaldzka 182",
                       "postCode": "60-166",
                       "city": "Poznań",
                       "countryCode": "PL"
                    },
                  
  2. We will add a new "contact" section with contact information - phone number and email address.
    
                "contact": {
                    "phoneNumber": "123 123 123",
                    "email": "useridentifier@domain.com"
                  },
                
  3. We will add a new "options" section which will contain the selected options:
    • "cashOnDeliveryNotAllowed" - "Nie przyjmuję zwrotów nadanych za pobraniem",
    • "freeAccessoriesReturnRequired" - "Otrzymałeś gratis? - w przypadku zwrotu towaru odeślij go również do nas",
    • "refundLoweredByReceivedDiscount" - "Otrzymałeś rabat na kolejną sztukę? - w przypadku zwrotu towaru pomniejszymy zwrot wpłaty o wartość udzielonego rabatu",
    • "refundOfCheapestItemInCombinedDiscount" - "Podczas zakupu zestawu otrzymałeś rabat na kolejny produkt? - w przypadku zwrotu jednego produktu z zestawu, otrzymasz zwrot pieniędzy za tańszy produkt",
    • "businessReturnAllowed" - "Przyjmuję zwroty od firm (nie dotyczy jednoosobowych działalności gospodarczych)",
    • "collectBySellerOnly" - "Osobiście odbieram zwrot od kupującego".
    
                "options": {
                    "cashOnDeliveryNotAllowed": true,
                    "freeAccessoriesReturnRequired": true,
                    "refundLoweredByReceivedDiscount": true,
                    "refundOfCheapestItemInCombinedDiscount": false,
                    "businessReturnAllowed": false,
                    "collectBySellerOnly": false
                  }
            
  4. For value "range": "RESTRICTED":
    • in the restrictionCause.name field we will add one value "VALUE_DEPENDENT_ON_FINANCIAL_MARKET" - "Usługę lub przedmiot, których ceny zależą od wahań na rynku finansowym, nad którymi sprzedający nie ma kontroli, a które mogą wystąpić przed upływem terminu na odstąpienie od umowy. Np.: produkty inwestycyjne: sztabki złota, monety kolekcjonerskie, srebro, platyna."
    • we will change the descriptions for existing values in the restrictionCause.description field:
      • "SHORT_SHELF_LIFE" - "Produkt z krótkim terminem przydatności do spożycia lub taki, który szybko się psuje. Np.: twaróg, świeże warzywa, rośliny doniczkowe."
      • "SEALED_MEDIA" - "Nagranie dźwiękowe, wizualne, program komputerowy w zapieczętowanym opakowaniu. Np.: kiedy kupujący zdejmie folię ochronną z fabrycznie nowej gry, lub płyty z muzyką czy filmem."
      • "PRESS" - "Dziennik, periodyk lub czasopismo – z wyjątkiem umów o prenumeratę."
      • "CUSTOM_ITEM" - "Rzecz wyprodukowaną na indywidualne zamówienie kupującego, według jego wytycznych.Np.: koszulka z zaprojektowanym przez kupującego nadrukiem."
      • "SEALED_ITEM_NO_RETURN_DUE_HEALTH_OR_HYGIENE" - "Rzecz, której po otwarciu nie możesz zwrócić ze względu na ochronę zdrowia lub higienę – na przykład: bielizna osobista, test ciążowy, końcówki do szczoteczki elektrycznej, soczewki kontaktowe, maseczki."
      • "NOT_RECORDED_DIGITAL_CONTENT" - "Treść cyfrową, nie zapisaną na nośniku materialnym, z której kupujący zgodził się skorzystać. Np.: pobranie ebooka, kodu do gry."
      • "INSEPARABLY_LINKED" - "Rzecz, którą po dostarczeniu trwale połączysz z innymi rzeczami. Np.: olej samochodowy, który wlejesz do auta."
      • "MEDICINAL_PRODUCT" - "Produkt leczniczy w rozumieniu prawa farmaceutycznego. Np.: leki OTC (bez recepty), leki dla zwierząt."
    
                "availability": {
                    "range": "RESTRICTED",
                    "restrictionCause": {
                        "name": "VALUE_DEPENDENT_ON_FINANCIAL_MARKET",
                        "description": "Usługi lub przedmioty, których cena zależy od wahań na rynku finansowym, nad czym sprzedający nie ma kontroli, a które mogą wystąpić przed upływem terminu na odstąpienie od umowy. Np.: produkty inwestycyjne: sztabki złota, monety kolekcjonerskie, srebro, platyna."
                  },
            

Sample response for GET /after-sales-service-conditions/return-policies/{returnPolicyId}:

{
  "name": "zwrot towaru",
  "availability": {
    "range": "FULL",
    "restrictionCause": null
  },
  "withdrawalPeriod": "P14D",
  "returnCost": {
    "coveredBy": "SELLER"
  },
  "attachment": {
    "id": "54702c96-4ccd-4c0e-b4c7-382a71e810b5",
    "name": "Przykładowy formularz odstąpienia.pdf",
    "url":  "https://after-sales.allegrostatic.com/after-sales-service-d2/d7be84bc-5408-42d2-8d0d-acf3ea02feba"
  },
  "address": {
    "name": "Allegro.pl sp. z o.o.",
    "street": "Grunwaldzka 182",
    "postCode": "60-166",
    "city": "Poznań",
    "countryCode": "PL"
  },
  "description": "Informacje dodatkowe",
  "contact": {
    "phoneNumber": "123 123 123",
    "email": "useridentifier@domain.com"
  },
  "options": {
    "cashOnDeliveryNotAllowed": true,
    "freeAccessoriesReturnRequired": true,
    "refundLoweredByReceivedDiscount": true,
    "refundOfCheapestItemInCombinedDiscount": false,
    "businessReturnAllowed": false,
    "collectBySellerOnly": false
  }
}

What do you need to adapt your returns policy to the changes?

From now on, you can check and adjust the return addresses to the given guidelines. Otherwise, from July 20th, 2021, you will get an error when creating or editing your return policy.

On July 20th, 2021, we will add new fields and values to the existing structure so that they can be adapted to changes. They will not be obligatory at this stage.

What will we change in October 2021?

  1. We will remove the "attachment" field.
  2. We will remove the "description" field and replace it with an optional "contact" object.
  3. Sending the full "options"structure will be obligatory.
  4. We will remove 3 values from restrictionCause.name:
    • "ALCOHOL",
    • "BOOKED_SERVICE",
    • "FULLY_IMPLEMENTED_SERVICE".
30JUN
2021

Sandbox - on July 8th, 2021 we will update the list of categories and parameters and remove all offers

On July 8th, 2021 we will update the list of categories and parameters on Sandbox. This will allow us to ensure consistency between test and production environments.

Note! Due to the update, we will remove all offers from Sandbox.

29JUN
2021

New value in the "endedBy" field

According to our previous announcement, from today we return a new value EMPTY_STOCK in the "endedBy" field, which informs about the end of the offer due to the stock count exhaustion.

What resources are affected by these changes?

For GET /sale/offer-events, we return the "endedBy" field with the new EMPTY_STOCK value. You will see it in the field "offer.publication" for the events where offer was ended - "type": "OFFER_ENDED".

You will find more information about event journal concerning changes in seller’s offers - in our guide.

Previous news:

- New value in the "endedBy" field for /sale/offers/{offerId} resources (June 22nd, 2021)

29JUN
2021

New scope in the Allegro API for Message Center

Scopes define the level of authorization to use the Allegro API. You can apply only for scopes that are actually necessary for the proper functioning of the application. If you do not take any steps, your application will authorize itself with the full scope list every time.

In the first half of July 2021, we will launch a new scope allegro:api:messaging, which will be responsible for managing the Message Center.

It will allow for:

  • a view of the list of threads and messages,
  • creating, sending and deleting messages,
  • downloading and adding attachments to messages.

How will it look after the change?

So far, if you have been requesting access to:

  • a full list of scope, without taking any extra steps - we will display them again to the user on the consent screen with a new scope,
  • a full list of scopes that you provide - we will not display them to the user on the consent screen,
  • only selected scopes - we will not display them again to the user on the consent screen. To use the functionality of the new scope, add its value to the authorizing call, then the user will display a consent screen that already includes the new scope.

What will remain the same?

If you use refresh tokens - only those scopes that were included in the refresh token will be available.

You will find more information about API Allegro scopes in our guide.

25JUN
2021

GET /order/events - a new event type

From July 1st, 2021 for GET /order/events we will add a new event type “AUTO_CANCELLED”. If you see such an entry in the event log, it means that we have automatically cancelled the order. This can happen when the buyer chooses to pay in advance and fails to pay for the order within 7 days.

Note! If the buyer wins the auction and chooses to pay in advance, we will automatically cancel the order if the customer fails to pay within 30 days.

You can find more information about event log in our tutorial.

22JUN
2021

New value in the "endedBy" field for /sale/offers/{offerId} resources

From June 29th, 2021 for:

we will return a new value EMPTY_STOCK in the "endedBy" field, which will inform about the end of the offer due to the stock count exhaustion.

What will change?

  • we will change the reason for the end of the offer which has been sold out - from EXPIRATION to EMPTY_STOCK,
  • we will also return the EMPTY_STOCK value for an auction ended with a Buy Now sale, while for the other auctions we will return the EXPIRATION value,
  • the EXPIRATION value will remain for offers ended after their duration time has expired and will no longer apply to sold-out offers.
information

Note! The change will not affect already ended offers.

21JUN
2021

GET /sale/matching-categories - we are changing the name of the “matching_categories” field

Owing to GET /sale/matching-categories you can retrieve a suggested list of categories in which you can list your item - you just need to provide a particular phrase in the “name” parameter. Thanks to it you can easily and quickly identify the appropriate category.

We want the fields in our API to be named according to certain standards, that is why we decided to rename "matching_categories" to "matchingCategories". Therefore:

  • from today, i.e June 21st, 2021 to July 20th, 2021, we will return both fields in the response - “matching_categories” and “matchingCategories”;
  • on July 21st, 2021 we will remove the "matching_categories" field, so only the "matchingCategories" field will remain.
16JUN
2021

Orders - we have increased the invoice limit

Starting today, you can add up to 5 invoices to each order for the POST /order/checkout-forms/{id}/invoices resource.

Note! The increased limit does not apply to orders with Extended Payment Terms - for them, you can still only add 1 invoice to the order.

You can find more information on how to manage invoices in our guide.

7JUN
2021

Allegro Prices - manage program participation consents

Allegro Prices is a sellers support program that will help them to offer the best prices on the market - at no extra cost. You can find more information about this program on our sellers page.

Today we have introduced news endpoints, owing to which you can manage program participation consents - both for a single offer and the entire account:

You can find more information about new resources in our guide.

1JUN
2021

We have made changes in GET /offers/listing

According to our previous announcement, today we have made changes in GET /offers/listing:

  • access only for verified applications,
  • popularity - instead of the number of items sold, only ranges are available: 0, [1-5], [6-10], [11-20], [21-50], [51-100], [101+];
  • sorting by popularity is not possible,
  • the search is limited to 10 pages (the maximum value of the offset parameter is 600).

You can find more information in our guide.

Previous news:

31MAY
2021

New value in "tax.annotation" field in the billing operations history

Due to the upcoming changes to VAT (VAT e-Commerce Package from July 1st, 2021), today we updated the field: "tax.annotation" in GET /billing/billing-entries. For billing entries that are not subject to VAT - we return the new value "OUT_OF_SCOPE". At the same time, we removed two previous values: "EXEMPT" i "NOT_APPLICABLE".

Sample response:

  ...
{    
    "id": "f2b843f1-8fa3-45a6-98f7-0590cd8d39d2",
    "occurredAt": "2020-09-07T10:47:19.981Z",
    "type": {
        "id": "VEP",
        "name": "VAT e-commerce charge"
    },
    "offer": {
        "id": "9608631867",
        "name": "oferta testowa"
    },
    "value": {
        "amount": "-20.10",
        "currency": "PLN"
    },
    "tax": {
        "annotation": "OUT_OF_SCOPE"
    }
...
 } 

You can find more information about the billing operations history in our guide.

31MAY
2021

New delivery methods

Today we have introduced two new delivery methods of delivering oversized shipments in Poland. You can get identifiers of the new delivery methods using GET /sale/delivery-methods:

  • Allegro SUUS Logistics - id: ae814e65-d1e8-463a-85b2-4dff7e5146a7
  • Allegro SUUS Logistics pobranie - id: b7d7cc1b-04c9-4a47-be31-4dff7e5146a7

You can find more information about this change here.

27MAY
2021

GET /order/checkout-forms/{id}/invoices - new list of invoice rejection reasons

From today, when you use GET /order/checkout-forms/{id}/invoices, in the eptVerification object we will return a new reasons objects array, in which you will find the fields:

  • id - ID of the reason for the invoice rejection,
  • message - rejection reason.

Owing to the reasons array, you will find out for what reasons PragmaGO rejected the invoice file you sent.

Sample response:

  {
   "invoices": [
      {
       ...
       "eptVerification": {                                 
           "status": "REJECTED",                            
           "verifiedAt": "2021-01-07T15:58:00.000Z",
           "reason": "Incorrectly filled invoice",           
           "reasons": [{                                    
                "id": "FIELD_NET_VALUE_NOT_READ_BY_OCR",
                "message": "The net amount is illegible. Make sure the document is legible (a
                            better resolution scan may help)."
            }]
       }
     }
   ]
  } 
information

Note! On August 19th, 2021, we will remove the reason field, so start using the new reasons array.

We only return the eptVerification object for an order with Deferred payment for Businesses. For other payment methods we will return null value.

You can find more information on how to manage invoices in our guide.

25MAY
2021

GET /offers/listing - new field "popularityRange"

According to our previous announcement from June 1st, 2021 we will add a new field "popularityRange" on GET /offers/listing resource.

In this field we will return popularity ranges: 0, [1-5], [6-10], [11-20], [21-50], [51-100], [101+].

In the existing "popularity" field, we will return the lowest value from the range.

Sample response:

{
    ...
    "sellingMode": {
        "format": "BUY_NOW",
        "price": {
            "amount": "265.99",
            "currency": "PLN"
        },
        "popularity": 1,
        "popularityRange": "[1-5]"
    },
    "stock": {
        "unit": "UNIT",
        "available": 3
    },
    ...
 }

Previous news:

24MAY
2021

Order number in the billing operations history

Today in: GET /billing/billing-entries, we have introduced a new object "order", in which we will return the order number in the "order.id" field. Thanks to this change, you will associate fees and commissions with a specific order.

information

Note! We will return the value in the "order.id" field for all billing types in which we show the order number. For the other billing types we will not return the "order" object.

Sample response:

...
{    
    "id": "f2b843f1-8fa3-45a6-98f7-0590cd8d39d2",
    "occurredAt": "2020-09-07T10:47:19.981Z",
    "type": {
        "id": "SUC",
        "name": "Sales commission"
    },
    "offer": {
        "id": "9608631866",
        "name": "oferta testowa"
    },
    "value": {
        "amount": "-10.10",
        "currency": "PLN"
    },
    "tax": {
        "percentage": "23"
    },
    "balance": {
        "amount": "-113.53",
        "currency": "PLN"
    },
    "order" : {
        "id" : "726c25e0-f0f7-11ea-887c-8753d63d8e79"
    }
...
 }

You will find more information about the billing operations history in our guide.

19MAY
2021

We adapted Allegro API to the VAT eCommerce package

As we announced from today we have adapted Allegro API to the European Union VAT eCommerce Package, which will come into force on July 1st, 2021. You can read more about the package on the sellers page.

Therefore, we have introduced a new resource:

information

Note! In each category, the available VAT settings may differ. Therefore, check what VAT rates are available for the given category.

On resources:

  • /sale/offers,
  • /sale/product-offers,

we have extended tax object by new fields:

  • tax.id - the unique identifier of an immutable VAT setting,
  • tax.rate - the tax rate,
  • tax.subject - the subject of taxation,
  • tax.exemption - the exemption of taxation.
information

Note! You can still use the tax.percentage field to enter VAT settings, but in the future we will remove this field entirely. After entering the VAT rate in the tax.percentage field, we will assign to the offer VAT settings appropriate for the category.

In addition, until now, to specify the VAT rate, it was necessary to pass the appropriate value in the payments.invoice field. As of today, we have removed this dependency.

For more information about the change, see our guides:

13MAY
2021

Reminder about changes in GET /offers/listing

We remind you, that on June 1st, 2021 we will introduce changes in GET /offers/listing:

  • only for verified applications,
  • popularity - instead of the number of items sold, only ranges will be available: 0, [1-5], [6-10], [11-20], [21-50], [51-100], [101>]
  • sorting by popularity will not be possible,
  • the search will be limited to 10 pages (the maximum value of the offset parameter is 600).
information

Note! Contact us via the form, or if you are in the Partnership Program for Sellers via your account manager to undergo the verification process.

Previous news:

12MAY
2021

New statuses of order fulfillment

To facilitate the handling of orders with personal pickup of the shipment at the pick-up point, for the resource:

today we have added new values:

  • READY_FOR_PICKUP,
  • PICKED_UP,

which you can provide in the “status” field to update the status of the order.

At the same time for resources:

we will return new values in the fulfillment.status field.

You can find more information on changing the status of an order in our guide and a full list of statuses - in our documentation.

11MAY
2021

What do you think about Allegro devportal?

Complete the survey about our Allegro API website. We want to improve our devportal so that it will truly meet your needs, and your answers will allow us to indicate the direction of further development.

The survey will take you only a few minutes. To complete the survey - click here.

11MAY
2021

Allegro pickup drop off points - we have introduced new endpoints for managing Allegro parcels

Today we have introduced Allegro pickup drop off points. Owing to the new delivery method “Allegro punkty” buyers can now order purchased items to one of our Allegro pickup points. The new delivery method is now enabled only for a selected group of sellers and from May 25th, 2021 it will be available for all merchants. At the beginning we have introduced about 600 points, we plan to add more by the end of 2021, including our parcel machines. You can find more information about Allegro pickup drop off points on our for sellers page.

Sellers will be able to generate parcel labels only via Send with Allegro tool, so today we have introduced new endpoints that will make it easier to handle orders.

You can find more information, how to use those resources in our guide.

Additionally, in response to:

29APR
2021

We will adapt Allegro API to the VAT e-commerce package

On July 1st, 2021 the European Union is introducing the VAT e-commerce package. Therefore, for part of business-to-consumer (B2C) transactions on electronic platforms, sellers from outside the European Union will settle under the new rules. Read more about this in the information for sellers.

Therefore, from May 19th, we will introduce a new resource:

  • GET /sale/tax-settings?category.id={categoryId} - get all VAT settings available in the given category. Based on the list you receive, you can configure the VAT settings for the seller's offers listed in a given category.

    Sample request:

    curl -X GET \
    ‘https://api.allegro.pl/sale/tax-settings?category.id=316194’ \
    -H ‘Authorization: Bearer {token}’ \
    -H ‘accept: application/vnd.allegro.public.v1+json’
    

    Sample response:

    {
      "settings": [                                         -- a list of tax settings in given
                                                            category
        {
          "id": "f40ae51c-70a2-4882-98a7-6272404f0ec5",     -- a unique identifier of an
                                                            immutable VAT setting
          "rate": {                                         -- an object representing VAT tax
                                                            rate assigned to this setting
            "id": "OUT_OF_SCOPE_OF_VAT",                    -- a unique identifier of a rate,
                                                            depending on the category, the
                                                            available values are:
                                                            23.00, 8.00, 5.00, EXEMPT,
                                                            OUT_OF_SCOPE_OF_VAT.
                                                            We can extend the dictionary 
                                                            of available values.
            "name": "Out of scope of VAT"                   -- name for a VAT rate
          },
          "subject": {                                      -- an object representing a
                                                            subject of taxation assigned to
                                                            this setting
            "id": "GOODS",                                  -- a unique identifier of a subject 
            "name": "Goods"                                 -- name for a subject
          },
          "exemption": {                                    -- an object representing a 
                                                            exemption of taxation assigned
                                                            to this setting
            "id": "MPV",                                    -- a unique identifier of an
                                                            exemption
            "name": "MPV (multi-purpose voucher)"           -- name for an exemption
          }
        }
        ...
      ]
    }
    
information

Note! In each category, the available VAT settings may differ. Therefore, check what VAT rates are available for the given category.

At the same time, we will extend the tax object with new fields on resources:

  • /sale/offers,
  • /sale/product-offers.

The new fields are:

  • tax.id - the unique identifier of an immutable VAT setting,
  • tax.rate - the tax rate,
  • tax.subject - the subject of taxation,
  • tax.exemption - the exemption of taxation.
information

Note! You can still use the tax.percentage field to enter VAT settings, but in the future we will remove this field entirely. After entering the VAT rate in the tax.percentage field, we will assign to the offer VAT settings appropriate for the category.

To enter or change the VAT settings in the offer:

  • pass the appropriate combination of values for the tax.rate, tax.subject and tax.exemption fields, based on which we find the identifier of the matching VAT setting. If there is no match, we will return a validation error with information about which fields should be filled or a message that there is no match at all.

    Sample request:

    curl -X PUT
    ‘https://api.allegro.pl/sale/offers/9531382307’ \
    -H 'Authorization: Bearer {token}' \
    -H 'Accept: application/vnd.allegro.public.v1+json' \
    -H 'Content-Type: application/vnd.allegro.public.v1+json' \
    -d ’
    {
        "id": "9531382307",
        "name": "Test offer",
        "category": {
            "id": "257150"
    },
    ...
      "tax": {
        "rate": “23.00”,
        "subject": “GOODS”,
        "exemption": “MONEY_EQUIVALENT”
      }
    …
    }’
    

    Sample response:

    {
        "id": "9531382307",
        "name": "Test offer",
        "category": {
            "id": "257150"
    },
    ...
      "tax": {
        "id": “f40ae51c-70a2-4882-98a7-6272404f0ec5”,
        "rate": “23.00”,
        "subject": “GOODS”,
        "exemption": “MONEY_EQUIVALENT”,
        "percentage": “23.00”
      }
    ...
    }
    
  • in the tax.id field, pass the VAT setting ID obtained by GET /sale/tax-settings?category.id={categoryId}.

    Sample request:

    curl -X PATCH \
    ‘https://api.allegro.pl/sale/product-offers/9531382307’ \
    -H 'Authorization: Bearer {token}' \
    -H 'Accept: application/vnd.allegro.beta.v2+json' \
    -H 'Content-Type: application/vnd.allegro.beta.v2+json' \
    -d ’
    {
      "tax": {
        "id": “f40ae51c-70a2-4882-98a7-6272404f0ec5”
      }
    }’
    

    Sample response:

    {
        "id": "9531382307",
        "name": "Sample product",
        "product": {
            "id": 5902719471797
        },
    …
      "tax": {
        "id": “f40ae51c-70a2-4882-98a7-6272404f0ec5”,
        "rate": “23.00”,
        "subject": “GOODS”,
        "exemption": “MONEY_EQUIVALENT”,
        "percentage": “23.00”
      }
    ...
    }
    

You can read more about the VAT e-commerce package on the for sellers page.

29APR
2021

Repayment date for Extended Payment Terms

In Extended Payment Terms the customer has the option to postpone the payment of the order by 21, 45 or 60 days. In order to receive payment the Seller must provide an invoice that includes the due date of payment (date of purchase + the extended time chosen by the buyer).

To automate this process for resources:

today we released a new field “dueDate” in the object “invoice”. In this field we return the date that defines the date of extended payment.

information

Note! We will return the value of the “dueDate” field only for extended payments for companies. The field will be null for all other payments.

Sample response:

 
...
{
  "invoice": {
    "required": true,
    "address": {
      "street": "Grunwaldzka 182",
      "city": "Poznań",
      "zipCode": "60-166",
      "countryCode": "PL",
      "company": {},
      "naturalPerson": {}
    },
    "dueDate” : “2021-12-01”
  }
...
}

You can find more information about Extended Payment Terms in Allegro Help and our news.

8APR
2021

New delivery methods from Germany and the Czech Republic

Today we have introduced new delivery methods from Germany and the Czech Republic. You can get its identifiers via: GET/sale/delivery-methods:

  • Kurier DPD wysyłka z Niemiec - id: 0c608ab6-4eed-491b-9ec5-8c1458ebe7cc,
  • Kurier DPD wysyłka z Czech - id: 046a3da7-354b-4630-858a-8c1458ebe7cc,
  • Kurier UPS wysyłka z Niemiec - id: 0ed0d545-3e7a-4cd9-b0e8-8c1458ebe7cc,
  • Kurier UPS wysyłka z Czech - id: 041b2a75-face-4827-8dca-8c1458ebe7cc.

You can find more information about delivery methods in our guide.

8APR
2021

From May 7th, 2021 we will require 1% of offers related to the Allegro Product Catalog in the next Automotive categories

In 2019, we have introduced the Allegro Product Catalog in selected categories. Within Allegro Product Catalog we want to gather and describe all of the products that are available in the sellers listed offers. We catalog individual products as a representative, which differs from others with their properties, e.g. model, manufacturer's code, GTIN number, or other basic parameters.

From January 18th, 2021 we require that 1% of offers in selected Automotive categories were related to the Allegro Product Catalog. On May 7th, 2021 we will add new Automotive categories to the list. You can find the full list of categories here.

information

Note! If a seller will not meet this condition, it will be not available to list new offers in those categories, if current offers are not assigned to a product.

You can find more information about how to assign an offer to a product in our guide. Check also POST /sale/product-offers resource, which allows you to list an offer assigned to a product with one request:

  • if the product already exists in our database, all you need to do is provide EAN code (or product ID), price and quantity,
  • if the product is not in our database, you need to provide product data, price, and quantity.

You can use GET /sale/offers with product.id.empty=true parameter to check which offers are not associated with a product.

1APR
2021

Allegro Prices - badge does not change the price in the offer

Allegro Prices is a seller support program that will help them to offer the best prices on the market - at no extra cost.

Currently, with the qualification of an offer to the Allegro Prices program, as with other campaigns, we also update the price in its structure - this change is visible in the sellingMode.price.amount field on the resources:

  • /sale/offers,
  • /sale/product-offers.

From April 14, 2021, we will change the mechanism for campaigns within the Allegro Prices program. If an offer qualifies for this program, we will not change the price in its structure. Therefore, the price we return in the sellingMode.price.amount field will remain unchanged.

Because of this change, the GET /sale/offer-events response will also not return an event about a price change in an offer as a result of qualifying it for this program.

Also, we will no longer return the prices.subsidy.sellerPrice field in the GET /sale/badges and will remove it entirely.

To check which offers have qualified for the Allegro Prices program, use GET /sale/badges.

information

Note! Any change to the price of the goods in the offer will lead to that offer being excluded from the Allegro Prices program. You will not be able to include the offer in the program again until the next qualification round.

The offers that have already qualified for the program will be migrated and will also operate under the new mechanism.

Read more about the Allegro Prices program on the seller’s page. Find out what changes we introduced, to facilitate the handling of orders in which the buyer made a purchase covered by Allegro Prices.

1APR
2021

POST /sale/offer-tags - we reduced the limit of offer tags to 100

Today we reduced the limit of offer tags, which you can add to your account via: POST /sale/offer-tags. The current limit which was: 10000, has been changed to: 100.

information

Note! We will not remove redundant tags for users who have already exceeded the threshold of 100 tags. However, please remember that Buyers will see only the first 100 tags on the website, which are not hidden.

You can find more information, how to add tags to your offers in our guide.

29MAR
2021

We removed the "ean" field and the "eans" object

According to our previous announcement, today we removed:

Use the Global Trade Item Number (GTIN) parameter to add or change EAN, ISBN and ISSN.

17MAR
2021

PATCH /sale/product-offers/{offerId} - we have added support for a “product.id” field

Using resource PATCH /sale/product-offers/{offerId} you will easily edit your offer. All you have to do is provide any field of the offer in the structure. You do not have to pass its entire structure.

Recently we have announced, that on April 1st, 2021 we will increase the percentage of offers related to the Allegro Product Catalog. To facilitate this process, we have added support for a field: product.id, in which you indicate the identifier of a given product or the GTIN parameter (EAN, ISBN, ISSN). In response, we will automatically update the offer with:

  • category and parameters,
  • description,
  • images,
  • compatibilityList section,
  • TecDoc specification

according to the data in the associated product.

In summary, if you provide product.id via PATCH /sale/product-offers/{offerId}, you will agree that the offer will be adapted to the product.

information

Note! If you want to keep the current description, photos and product parameters, in addition to product.id you should deliver them in such fields as : description, images i product.parameters. You can retrieve this data from your offer via GET /sale/offers/{offerId}.

We have provided a detailed instruction in our guide, to illustrate the process of associating the offer with the product using the PATCH method.

Sample request:

curl -X PATCH \
  ‘https://api.allegro.pl/sale/product-offers/7680042192 \
  -H 'Authorization: Bearer {token}'  \
  -H 'Accept: application/vnd.allegro.beta.v2+json'
  -H 'Content-Type: application/vnd.allegro.beta.v2+json' \
  -d ’{
  "product": {
        "id": "0475a562-fbbb-4260-b772-59a82aa96554"
        }
  }'

You cannot remove a product from the offer. If you provide value null in a field product.id - we will return an error 422 status code.

Sample response:

 {
    "id": "7680042192",
    "name": "Żarówka samochodowa LED",
    "product": {
        "id": "0475a562-fbbb-4260-b772-59a82aa96554",
        "publication": {
            "status": "NOT_LISTED"
        }
    },
    "afterSalesServices": {
        "impliedWarranty": {
            "id": "f4f3541e-41c2-481f-938a-2a1b8c0ce65a"
        },
        "returnPolicy": {
            "id": "7068910b-29b9-449b-8ad0-99625a6312db"
        },
        "warranty": null
    },
    "payments": {
        "invoice": "NO_INVOICE"
    },
    "sellingMode": {
        "format": "BUY_NOW",
        "price": {
            "amount": 100,
            "currency": "PLN"
        },
        "startingPrice": null,
        "minimalPrice": null
    },
    "stock": {
        "available": 3,
        "unit": "UNIT"
    },
    "location": {
        "countryCode": "PL",
        "province": "WIELKOPOLSKIE",
        "city": "Poznań",
        "postCode": "60-166"
    },
    "delivery": {
        "shippingRates": {
            "id": "7dd8049c-1753-4842-8870-e29a2efc3d62"
        },
        "handlingTime": "PT48H",
        "additionalInfo": ""
    },
    "publication": {
        "duration": null,
        "status": "ACTIVE",
        "endedBy": null,
        "endingAt": null,
        "startingAt": null,
        "republish": false
    },
    "description": {...}
    "validation": {
        "errors": [],
        "warnings": [],
        "validatedAt": "2021-03-16T14:01:53.434Z"
    },
    "createdAt": "2021-02-24T07:01:55Z",
    "updatedAt": "2021-03-16T14:01:53.793Z",...
    "images": [
        "https://a.allegroimg.com/original/119247/d50959f64c568b3cd1421c70f31e",
        "https://a.allegroimg.com/original/1112b4/d03b421247169a2835880cc39d88"
    ],
    "external": null,
    "category": {
        "id": "257359"
    },
    "tax": {
        "percentage": null
    },
    "sizeTable": null,
    "discounts": {
        "wholesalePriceList": null
    }
}

If you want to check which of your offers are not associated with a product, please use GET /sale/offers?product.id.empty=true.

You can find more information, how to manage your offer using the method PATCH in our guide.

15MAR
2021

Allegro Prices - we will add new objects and field types to handle orders

Allegro Prices is a seller support program that will help you to offer the best prices on the market - at no extra cost.

Because of this program, on March 31th, 2021 we will make changes to:

so you will be able to correctly identify and process orders where the buyer has purchased from the offer that is in the Allegro Prices program.

For GET /order/checkout-forms and GET /order/checkout-forms/{id} we will add objects:

  • payment.reconciliation - payment amount that Allegro covers and will transfer with your payment under the Allegro Prices program,
  • lineItems[].reconciliation - where in the value object, we will return the amount by which the item price was reduced and the costs of which will be compensated by Allegro as part of the buyer's payment or billing entry.

In the lineItems[].reconciliation object, we will also return the type field, in which you will get one of the two possible values:

  • "BILLING" - reconciliation for the price reduction on billing entry,
  • "WALLET" - reconciliation for the price reduction in buyer’s payment.

For such orders, we will also return a new discount type in the discounts field: "ALLEGRO_PRICES".

Sample request:

curl -X GET \
  'https://api.allegro.pl/order/checkout-forms/4fceac60-71c6-11eb-bb0e-5f505b61d1dc’ \
  -H 'Authorization: Bearer {token}'  \
  -H 'Accept: application/vnd.allegro.public.v1+json'

Sample response:

 {
  ...
    "payment": {
        "id": "677d4ba1-71c6-11eb-a259-c766517115fd",
        "type": "ONLINE",
        "provider": "PAYU",
        "finishedAt": "2021-03-15T12:18:33.434Z",
        "paidAmount": { 
            "amount": "80",                 -- customer payment amount
            "currency": "PLN"
        },
        "reconciliation": {
            "amount": "0",                  -- amount of reconciliation for the price
                                            reduction in buyer’s payment.
                                            Will only occur in the case of 
                                            "WALLET" type reconciliation    
            "currency": "PLN"
        }
    },
    "status": "READY_FOR_PROCESSING",                      
    ...
    "lineItems": [
        {
            "id": "ffc36fa0-9584-11e8-8d53-07c966f77738",
            "offer": {
                "id": "6205584023",
                "name": "Lifebelt",
                "external": {
                "id": "ext_2018_08_17" 
              }
            },
            "quantity": 1, 
            "originalPrice": {          
                "amount": "80.00",
                "currency": "PLN"
            },
            "price": {
                "amount": "80.00",      
                "currency": "PLN"
            },
            "reconciliation": {
                "value": {  
                "amount": "20.00",          -- reconciliation amount
                "currency": "PLN"
                },
            "quantity": 1,                  -- amount of reconciled items
            "type": "BILLING"               -- reconciliation type, one of two 
                                            values are possible:
                                            BILLING (reconciliation for the price 
                                            reduction on billing entry);
                                            WALLET (reconciliation for the price reduction 
                                            in buyer’s payment).
            },
            "selectedAdditionalServices": [ ],
            "boughtAt": "2021-03-15T12:18:33.434Z"
        }
    ],
    "surcharges": [],
    "discounts": [ 
                {
                "type": "ALLEGRO_PRICES"    -- ALLEGRO_PRICES discount type means, 
                                            that we reduced price and granted 
                                            compensation
                }             
    ],
    "summary": {
        "totalToPay": {
            "amount": "80.00",           
            "currency": "PLN"
        }
    },
 "updatedAt": "2021-03-15T12:18:33.434Z",
 "revision": "dc0f896f"                                   
}
information

Note! In case of a correct payment (in which there was no overpayment or underpayment), the amount in payment.paidAmount and summary.totalToPay fields should be identical - regardless of whether the order was covered by Allegro Prices.

In GET /billing/billing-entries we will return a new billing operation type: "PS1". You will get it when a buyer makes a purchase that is covered by the Allegro Prices program, and in the order we returned value "BILLING" in the lineItems[].reconciliation.type field.

You can read more about the Allegro Prices program on the Sellers Page. You can find more informations about change in our guide.

15MAR
2021

We have changed the Terms of Conditions of the REST API Service

According to our previous announcement, today we have changed the Terms of Conditions of the REST API Service.

From today GET /offers/listing will not be available for new applications without verification. The remaining applications need to be verified until June 1st, 2021.

information

Note! Contact us via the form, or if you are in the Partnership Program for Sellers via your account manager to undergo the verification process.

From March 15th, 2021 application registration will only be possible for active accounts with enabled two-step login.

We also remind you that from June 1st, 2021 we will introduce changes to the data we return from GET /offers/listing. For this change, we set the ranges that will be available for the popularity.

3MAR
2021

On April 1st, 2021 we will increase the percentage of offers related to the Allegro Product Catalog

In 2019, we have introduced the Allegro Product Catalog in selected categories. Within Allegro Product Catalog we want to gather and describe all of the products that are available in the sellers listed offers. We catalog individual products as a representative, which differs from others with their properties, e.g. model, manufacturer's code, GTIN number, or other basic parameters.

On April 1st, 2021 we will increase the the percentage of offers related to the Allegro Product Catalog in the following categories:

productization-table

* in rest of the categories there is already 10%. Due to the specificity of some categories, we cannot require the percent of offers associated with a product in all of them. Check out the detailed list of categories in which we will introduce requirements.

On June 30th, 2021 we plan to increase the % requirement of offers assigned to a product to 50% in selected categories, while by the end of 2021 we want to catalog all offers in categories where it is possible.

information

Note! If a seller will not meet this condition, it will be not available to list new offers in those categories, if current offers are not assigned to a product.

You can find more information about how to assign an offer to a product in our guide. Check also POST /sale/product-offers resource, which allows you to list an offer assigned to a product with one request:

  • if the product already exists in our database, all you need to do is provide EAN code (or product ID), price and quantity,
  • if the product is not in our database, you need to provide product data, price, and quantity.

You can use GET /sale/offers with product.id.empty=true parameter to check which offers are not associated with a product.

You will find more information about this change on the for sellers page.

2MAR
2021

New types of attachments in the offer

From now on, when you use POST /sale/offer-attachments, you can add two new attachment types:

  • “ENERGY_LABEL” - energy label,
  • “PRODUCT_INFORMATION_SHEET” - product information sheet.

You will find more information about adding attachments to offer in our tutorial.

1MAR
2021

GET /offers/listing - only for verified applications

In accordance with the decision about which you can read more on the Allegro for Sellers website, we are limiting access to public sales data of other users. Therefore, we will only provide GET /offers/listing to verified applications, taking into account the following information:

  • as of today, i.e. on March 1, 2021, we announced changes to the Terms of Conditions of the REST API Service,
  • on March 15th, 2021 the new REST API Terms and Conditions will take affect - GET /offers/listing:
    • will not be available for new applications - contact us via the form, or if you are in the Partnership Program for Sellers via your account manager to undergo the verification process.
    • applications registered by March 15th, 2021 need to be verified until June 1st, 2021 - contact us via the form, or if you are in the Partnership Program for Sellers via your account manager to undergo the verification process.
  • from June 1st, 2021 GET /offers/listing will be available only for verified applications. We will introduce changes to the data we return:
    • popularity - instead of the number of items sold, only ranges will be available - we will provide more information about it in a separate announcement,
    • sorting by popularity will not be possible,
    • the search will be limited to 10 pages (the maximum value of the offset parameter is 600).

From March 15th, 2021 application registration will only be possible for active accounts with enabled two-step login.

To facilitate application testing and registration in the test environment:

  • GET /offers/listing will be available without verification for all applications,
  • two-step login will not be required.
1MAR
2021

Send with Allegro - we have added the “type” field at the level of the "items" section and changed its requirement

As of today when you create parcels via PUT /parcel-management/parcel-create-commands/{commandId} you can also create a so-called multipack, e.g. consisting of an ordinary package and a pallet. Due to this change, we have added the “type” field also at the level of the "items" section, so you can specify the type of parcel for each shipment separately. We also changed the requirement:

  • “type” is required only on one of the levels (main or in “items”),
  • if “type” fields are filled on two levels, we will check if all “type” fields on the “items” level have the same value as “type” as on the main level. If not, we will return an error.

This option is available only for selected carriers. Below you can find the maximum number of parcels for each of them:

  • 10 - DHL (except pallet), DPD (except dox), GLS, INPOST_KURIER, UPS (own contract), FEDEX,
  • 5 - DHL (pallet),
  • 1 - other carriers.

You can find more information in our guide.

1MAR
2021

We permanently set the null value in the "ean" field and the "eans" object

According to our previous announcement, from today we permanently set the null value in:

and you cannot change it.

On March 29th, 2021 we will completely remove the "ean" field from the offer model and the "eans" object from the product model.

Use the Global Trade Item Number (GTIN) parameter to add or change EAN, ISBN and ISSN.

26FEB
2021

What do you think about Allegro API?

Complete the survey about our API and Allegro API website. Your answers will allow us to understand your needs and indicate the direction of further development.

The survey will take you only a few minutes. To complete the survey - click here.

22FEB
2021

GET /parcel-management/delivery-services - a new field “carrierId”

Today in GET /parcel-management/delivery-services we have introduced a new field “carrierId” in which we return information about shipping carrier ID, who provides the given delivery service. The values of the "carrierId" field match the values available for the GET /order/carriers resource.

Sample request:

curl -X GET \
  'https://api.allegro.pl/parcel-management/delivery-services’ \
  -H 'Authorization: Bearer {token}'  \
  -H 'Accept: application/vnd.allegro.public.v1+json'

Sample response:

{
    "deliveryServices": [
         {
           "id": 12345,
           "service": "INPOST_KURIER",
           "name": "InPost",
           “carrierId”: “INPOST”,                - shipping carrier ID
           "additionalServices": {
               "cashOnDelivery": {
                   "available": true,
                   "expressAvailable": true
                },
               "options": [
                   {
                       "name": "guarantee1200",
                       "description": "Delivery up to 12:00."
                   }
               ]
            },
           "owner": "ALLEGRO"
         }
     ]
}

You can find more information on how to manage parcels via Send with Allegro in our tutorial.

18FEB
2021

Sale commission refunds - we have added information about the type of application

As of February 10th, 2021 the seller may in certain situations receive a sale commission refund automatically, without the need to create a refund application. You can find on the for sellers page more information about what conditions must be fulfilled.

Today we have introduced a new field “type” in response to:

in which you will find information about the type of sale commission refunds application:

  • “MANUAL” - the application was created manually by the seller,
  • “AUTOMATIC” - the application was created automatically.

You can find more information about managing sale commission refunds in our tutorial.

15FEB
2021

Productization - we have removed productEANRequired field in resources for retrieving information about categories

According to our previous announcement today we have removed options.productEANRequired field for:

in which we returned information on whether you need to provide a GTIN parameter when you create a new product proposal.

From now on, use the requiredForProduct field for the GTIN parameter that you will get in response to GET /sale/categories/{categoryId}/parameters. Depending on the category, the GTIN parameter is:

  • EAN (ID 225693),
  • ISBN (ID 245669),
  • ISSN (ID 245673).
2FEB
2021

Authorization - we have extended refresh tokens validity to 60 seconds after first use

Refresh tokens have so far been disposable - after generating a new pair (access and refresh token), the previous ones immediately expired. We extended the validity of refresh tokens to 60 seconds after first use. Owing to it we want to solve the problem of lost refresh tokens due to interrupted connection. In such a situation, the only solution was to go through the entire user authorization process again to generate an access token and a refresh token. At present, it is not necessarily - you can retry to refresh the token with the same refresh token.

1FEB
2021

We ignore the value you send in the "ean" field and the "eans" object

According to our previous announcement, from today we ignore and not validate values in:

Also, we remind you that from March 1st, 2021 value in those objects will be set permanently as null - it will not be possible to change it.

On March 29th, 2021 we will completely remove the "ean" field from the offer model and the "eans" object from the product model.

Use the Global Trade Item Number (GTIN) parameter to add or change EAN, ISBN and ISSN.

1FEB
2021

Add an invoice to the order

Already in February 2021, with the launch of Allegro Biznes, we will introduce new resources, thanks to which you will add and download an invoice to the order:

  • POST /order/checkout-forms/{id}/invoices - create invoice object.

    Sample request:

    curl -X POST \
    ‘https://api.allegro.pl/order/checkout-forms/a8320af2-5f01-11eb-bbeb-112e13b418c5/invoices' \
    -H ‘Accept: application/vnd.allegro.public.v1+json’ \
    -H ‘Content-Type: application/vnd.allegro.public.v1+json’ \  
    -H ‘Authorization: Bearer {token}’ \
    -d ‘{
      "file": {
         “name”: "example-invoice.pdf"      - required, file name
      },
      "invoiceNumber": "FV 01/2020"         - not required, invoice number
    }’

    Sample response:

    {
      "id": "56ae349d-8045-4bb3-adcc-7cf6fb420f61"     - invoice id
    }
  • PUT /order/checkout-forms/{id}/invoices/{invoiceId}/file - upload a *.pdf file with invoice. As “invoice.id” pass the id value you received in response to POST method. You can add one *.pdf invoice to each order. The file size cannot exceed 2 MB.

    Sample request:

    curl -X PUT \
    ‘https://api.allegro.pl/order/checkout-forms/a8320af2-5f01-11eb-bbeb-112e13b418c5/invoices/56ae349d-8045-4bb3-adcc-7cf6fb420f61/file' \
    -H ‘Accept: application/vnd.allegro.public.v1+json’ \
    -H ‘Content-Type: application/pdf’ \
    -H ‘Authorization: Bearer {token}’ \
    -d 'data=@example0-invoice.pdf’
    
  • GET /order/checkout-forms/{id}/invoices - retrieve invoices assigned to the order.

    Sample request:

    curl -X GET \
    ‘https://api.allegro.pl/order/checkout-forms/a8320af2-5f01-11eb-bbeb-112e13b418c5/invoices' \
    -H ‘Accept: application/vnd.allegro.public.v1+json’ \
    -H ‘Authorization: Bearer {token}’
    

    Sample response:

    {
     “invoices”: [
        {
         "id": "56ae349d-8045-4bb3-adcc-7cf6fb420f61",        - invoice id
         "invoiceNumber": "FV 01/2020",                       - invoice number
         "createdAt": "2021-01-07T15:50:00.000Z",             - invoice creation date
         "file": {
             "name": "example-invoice.pdf",                   - file name
             "uploadedAt": "2021-01-07T15:50:00.000Z",        - upload date
             "securityVerification": {                
                 "status": "ACCEPTED",                        - file antivirus
                                                              verification status,
                                                              available values: WAITING, ACCEPTED, REJECTED.
                 "verifiedAt": "2021-01-07T15:51:00.000Z"     - verification date
             }
         },
         "eptVerification": {                                 - object is null for payment methods
                                                              other Extended Payment Terms
             "status": "ACCEPTED",                            - invoice verification for Extended Payment
                                                              Terms, available values: WAITING, ACCEPTED,
                                                              REJECTED.
             "verifiedAt": "2021-01-07T15:58:00.000Z",        - verification date
             "reason": null                                   - the reason for the rejection of the invoice,
                                                              if verification status is REJECTED.
         }
        }
     ]
    }                            
    
26JAN
2021

Productization - we have added new categories in the product data, in which you can list an offer assigned to a Product Catalog.

From now on, if the product fits into a few similar categories, you can list an offer assigned to this product, but in another, similar category defined by us.

In response to GET ​/sale​/products​/{productId} we will return a new list:

  • category.similar

in which we indicate the ID of similar categories. Use the selected ID to list the product in one of the returned categories.

Sample request:

curl -X GET \
‘https://api.allegro.pl/sale/products/b2b61e23-b580-4471-b653-6ed25fd179f7’ \
-H 'Authorization: Bearer {token}' \
-H 'accept: application/vnd.allegro.public.v1+json'

Sample response:

{
    "id": "b2b61e23-b580-4471-b653-6ed25fd179f7",
    "name": "BIO Torch",
    "category": {
        "id": "261573",
        "similar": [
            {
                "id": "110914"
            },
            {
                "id": "305121"
            }
        ]
    }
…
}
information

Note! Sets of similar categories are defined by us - we return them in response to GET ​/sale​/products​/{productId} and you cannot create them by yourself. The set of similar categories is currently limited, but we will systematically expand it.

The parameters within the categories may differ, therefore some parameters in the product may not be consistent with those that can be used in a similar category.

Use GET ​/sale​/products​/{productId}?category.id={similarCategoryId} and in the category.id parameter put the id from the set of similar categories returned by us to filter the parameters for the selected similar category. In response, you will receive product parameters that you can use when listing an offer in a similar category.

At the same time, we expanded the request structure in the offer part in:

by a new field - category.id. Enter in this field one of the id value that we return in the product data in category.similar list. You will list an offer assigned to the product in a similar category.

If in response you receive information about missing required parameters, provide them in the product object. You can check parameter ID with its value via GET /sale/{categoryId}/parameters.

You can also use similar category IDs when you assign an offer to a product via:

Currently, in the category.id field, instead of the main category ID, you can enter one of the values ​​available in the product in the category.similar.id field.

You can find more information on how to list offer assigned to a product in our guides:

21JAN
2021

Processing of orders with Extended Payment Terms

Already in February 2021, with the launch of Allegro Biznes, we will provide a new payment method for transactions between companies (B2B) - Extended Payment Terms. A seller who wants to provide Extended Payment Terms in their offers must have a business account and meet the conditions described in Allegro Help.

Due to the introduction of Extended Payment Terms for the order in the “READY_FOR_PROCESSING” status in:

  • GET /order/checkout-forms/{id} in the payment object:
    • we will provide a new payment type - “type”: “EXTENDED_TERM”,
    • we will provide a new payment provider - “provider”: “EPT”,
    • fields “finishedAt” and “paidAmount” will take a value null until the funds are actually transferred by the service provider (for the transfer to be processed, the seller must issue a VAT invoice and add a tracking number to the order).

    Sample view of payment object for orders with Extended Payment Terms before receiving the payment:

    "payment": {
        "id": "b83c6ea0-3ed0-11eb-a57e-ebbabb38ee2a",
        "type": "EXTENDED_TERM",
        "provider": "EPT",
        "finishedAt": null,
        "paidAmount": null
    }
    

    Once the payment will be transferred to the seller`s account, fields “finishedAt” and “paidAmount” will be updated with values:

    "payment": {
        "id": "b83c6ea0-3ed0-11eb-a57e-ebbabb38ee2a",
        "type": "EXTENDED_TERM",
        "provider": "EPT",
        "finishedAt": "2021-01-18T13:18:04.546Z",
        "paidAmount": {
            "amount": "1150.00",
            "currency": "PLN"
        }
    }
    

    Note! If the buyer chooses Extended Payment Terms as the payment method, he will no longer be able to cancel it and fill out the shipping form again.

  • GET /order/events we will return for this order second event “READY_FOR_PROCESSING” when the funds are transferred by the provider - field “occurredAt” will get the date of this operation as value (this will allow you to recognize that it is not a duplicate event).

You can find more information about Extended Payment Terms in Allegro Help.

20JAN
2021

GET /sale/badges - a new object “prices.subsidy”

Today in GET /sale/badges we have introduced a new object “prices.subsidy” in which we return information about:

  • sellerPrice - amount that is expected by the partner for the sale of the product,
  • targetPrice - price visible to the customer at the platform.

The difference between the amount paid by the customer (targetPrice) and the amount expected by the partner (sellerPrice) will be funded by Allegro as part of the Allegro Price program, which details you will find on for sellers page.


Sample request:
curl -X GET \
‘https://api.allegro.pl/sale/badges’ \
-H ‘Authorization: Bearer {token}’ \
-H ‘Content-Type: application/vnd.allegro.beta.v1+json’
Sample response:

{
 "badges": [
   {
     "offer": {
       "id": "10026815226"
     },
     "campaign": {
       "id": "SUBSIDY",
       "name": "Allegro Cena"
     },
     "publication": {
       "type": "SINCE",
       "from": "2021-01-19T11:31:56.131Z",
       "to": null
     },
     "prices": {
       "market": null,
       "subsidy": {
         "sellerPrice": {              -- amount that is expected by the partner for the sale of
                                       the product. The difference between the amount paid by the
                                       customer (targetPrice), and the amount expected by the
                                       partner (sellerPrice) will be funded by Allegro as part of
                                       the Allegro Price program.
           "amount": "100.00",
           "currency": "PLN"
         },
         "targetPrice": {              -- price visible to the customer at the platform
           "amount": "90.00",
           "currency": "PLN"
         }
       }
     },
     "process": {
       "status": "ACTIVE",
       "rejectionReasons": []
     }
   }
 ]
}
                      
15JAN
2021

From February 15th, 2021 we will require 10% of offers assigned to a product in the Health, Electronics, Sport and Travel categories

In 2019, we have introduced the Allegro Product Catalog in selected categories. Within Allegro Product Catalog we want to gather and describe all of the products that are available in the sellers listed offers. We catalog individual products as a representative, which differs from others with their properties, e.g. model, manufacturer's code, GTIN number, or other basic parameters.

On February 15th, 2021 we will increase the requirement from 1% to 10% in the following categories:

  • Health,
  • Electronics,
  • Sports and Travel.

We plan to catalog all offers where possible by the end of 2021. For this purpose, from September 1st, 2020 we have introduced a requirement for the % of offers assigned to a product. We already require 1% of offers assigned to a product in the following categories:

We also announced a change for January 18th, 2021 whereby:

  • we will increase the requirement to 10% of cataloged offers in the Culture and Entertainment, Beauty, Home and Garden, Supermarket categories,
  • we will require 1% of offers associated with a product in selected sections in the following categories Kids, Business and Services, Automotive.

We want to enable to associate offers with a product in as many categories as possible, but the specificity of the sold items not always allow it. See this file to check in which sections of the categories Kids, Business and Services, and Automotive we will enable the obligation of 1% of offers assigned to a product.

information

Note! If a seller will not meet this condition, it will be not available to list new offers in those categories, if current offers are not assigned to a product.

You can find more information about how to assign an offer to a product in our guide. Check also POST /sale/product-offers resource, which allows you to list an offer assigned to a product with one request:

  • if the product already exists in our database, all you need to do is provide EAN code (or product ID), price and quantity,
  • if the product is not in our database, you need to provide product data, price, and quantity.

You can use GET /sale/offers with product.id.empty=true parameter to check which offers are not associated with a product.

You will find more information about this change on the for sellers page.

14JAN
2021

/sale/product-offers resources - we support new fields that you can provide in request: “publication.startingAt” and “discounts”

Today we have introduced support for two offer attributes, which you can declare in the request structure of POST /sale/product-offers and PATCH /sale/product-offers/{offerId}:

  • publication.startingAt - offer start date, owing to which you can plan to list an offer in the future;
  • discounts - informacje o zniżkach.

For more information on how to submit these fields in the request, see our guide.

13JAN
2021

New delivery method - Kurier PickPack

Today we have introduced a new delivery method which is now available only in Warsaw. You can get its identifier in the resource GET /sale/delivery-methods:

  • Kurier PickPack - id: 41cc412c-ba9e-422d-9750-7918ea717539

You can find more information about this change here.

13JAN
2021

Categories and parameters - we have introduced an event journal in categories and resource with which you can check future changes in parameters

Today we have introduced two new resources, which allow you to follow changes in categories and parameters on our platform:

  • GET /sale/category-events - check changes in categories that took place in the last 3 months. In response, we will return by default 100 oldest events. Using parameter from and ID of given event you can retrieve another portion of data. At present we support the four types of events:
    • CATEGORY_CREATED - new category was created;
    • CATEGORY_RENAMED - category name has been changed;
    • CATEGORY_MOVED - the category has been moved to a different place in the category tree, category parent.id field is changed;
    • CATEGORY_DELETED - category is no longer available, category from redirectCategory field should be used instead.

    Sample request:
    
        curl -X GET
        ‘https://api.allegro.pl/sale/category-events’/
        -H ‘Authorization: Bearer {token}’ /
        -H ‘Accept: application/vnd.allegro.public.v1+json’
                          
    Sample response:
    
        {
        ...
          {
            "id": "MTEzMjQzODU3NA",                     -- event ID
            "occurredAt": "2021-01-12T15:26:43.891Z",   -- date at which event occurred
            "type": "CATEGORY_CREATED",                 -- event type
            "category": {                               -- category data concerned by the
                                                        event
                "id": "165",                            -- category ID
                "name": "Smartphones and Cell Phones",  -- category name
                "parent": {
                    "id": "4"                           -- ID of a parent category
                    },
                "leaf": false                           -- whether the category is
                                                        of the lowest tier
                    }
              }
        ...
        }
                          
  • GET /sale/category-parameters-scheduled-changes - check planned changes in parameters for the next 3 months. In response, you will receive by default a list of the earliest 100 scheduled changes. At present, we support only one type of change - REQUIREMENT_CHANGE (the given parameter will be marked as required).
    information

    Note! Sometimes, the returned events may finally not happen in the future, e.g. if we resign from marking a given parameter as required. In this case, we will remove the event from the response.

    You can also filter your results by date at which change was scheduled. Use the following filters when you want to check what changes we have planned recently:

    • scheduledAt.gte - the earliest date on which the change was scheduled,
    • scheduledAt.lte - the latest date on which the change was scheduled.

    e.g. to check which changes were scheduled till today, you need to make the following request: GET /sale/category-parameters-scheduled-changes?scheduledAt.lte=2021-01-13T23:59:59


    If you want to check which parameters we will mark as required in the near future, use filters:

    • scheduledFor.gte - the earliest date on which the parameter will be marked as mandatory,
    • scheduledFor.lte - the latest date on which the parameter will be marked as mandatory. Should be less than 3 months from the current date.

    e.g. to check which parameters will become mandatory by the end of February 2021, you need to make the following request: GET /sale/category-parameters-scheduled-changes?scheduledFor.lte=2021-02-28T23:59:59Z.


    Sample request:
    
        curl -X GET
        ‘https://api.allegro.pl/sale/category-parameters-scheduled-changes’/
        -H ‘Authorization: Bearer {token}’ /
        -H ‘Accept: application/vnd.allegro.public.v1+json’
                          
    Sample response:
    
        {
        ...
         {
          "scheduledAt": "2021-01-12T15:26:43.891Z",    -- date in the past when the change
                                                        was scheduled
          "scheduledFor": "2021-02-14T15:26:43.891Z",   -- date from the future when we plan to
                                                        implement the change
          "type": "REQUIREMENT_CHANGE",                 -- type of change
          "category": {
              "id": "165"                               -- category ID in which related
                                                        parameter is located
              },
          "parameter": {
              "id": "11323"                             -- parameter ID affected by the change
              }
          }
        ...
        }
                          

You can find more information about the new resources in our guide.

12JAN
2021

Productization - on February 15th, 2021 we will remove productEANRequired field in resources for retrieving information about categories

On February 15th, 2021 we will remove options.productEANRequired field for:

in which we return information on whether you need to provide a GTIN parameter when you create a new product proposal.

From now on, use the requiredForProduct field for the GTIN parameter that you will get in response to GET /sale/categories/{categoryId}/parameters. Depending on the category, the GTIN parameter is:

  • EAN (ID 225693),
  • ISBN (ID 245669),
  • ISSN (ID 245673).
7JAN
2021

We have increased the limit for price changes in the active offer

Today we have increased the limit for changing the price in the active offer.

If:

  • the offer price is lower than 50 PLN - the seller can increase it by no more than 100 PLN,
  • the offer price is over 50 PLN - the seller can increase it by no more than another 200%.

The restrictions apply to a one-time change of the Buy Now price in active offers.

4JAN
2021

We will remove the "ean" field and the "eans" object

According to our previous announcement, we would like to inform you that on March 29th, 2021, we will remove:

  • "ean" field - in the offer model,
  • "eans" object - in the product model.

We have divided the process of removing these objects into 3 steps.


  1. On February 1st, 2021, we will implement a change that if you provide in your request:

    we will ignore those values and not validate them.

    When you get:

    • offer details using GET /sale/offers/{offerId} - in the "ean" field we will return the GTIN parameter value (EAN/ISBN/ISSN) if one has been provided in the offer,
    • product data using GET /sale/product/{productId} - in the "eans" object we will return the value of the GTIN parameter (EAN/ISBN/ISSN) if one has been defined in the product.

  2. From March 1st, 2021 value in:
  3. will be set permanently as null - it will not be possible to change it.


  4. On March 29th, 2021 we will remove the "ean" field from the offer model and the "eans" object from the product model.
  5. This means that you will not receive and will not send:

    • “ean” field by GET/POST/PUT methods on resource /sale/offers,
    • eans” object on resources:
      • /sale/product-proposals,
      • /sale/product.

We remind you, that on June 29th, 2020 we introduced the Global Trade Item Number (GTIN) parameter. You can change the GTIN value (EAN, ISBN, ISSN) only by using this parameter.

4JAN
2021

GET /sale/offers/unfilled-parameters - we have introduced a new filter

Using GET /sale/offers/unfilled-parameters you can check missing parameters in your offers. According to our previous announcement, today we have added a new filter - parameterType. Owing to it, you can set which parameter type you want to receive in the response:

  • parameterType=REQUIRED - currently required parameters,
  • parameterType=REQUIREMENT_PLANNED - parameters that will be marked as required in the next 3 months.

We have also added information about the new filter in our guide.

23DEC
2020

We are turning off single purchase event mapping

According to our previous announcement we remind you that from January 12th, 2021, you will not be able to use single purchase event mapping via GET /order/line-item-id-mappings.

The resource may generate delays due to increased traffic, so stop using it as soon as possible.

21DEC
2020

Scope in the Allegro API on production environment

According to our previous announcement, we remind you that on January 11th, 2021 we will introduce the functionality of the scopes on the production environment, i.e. scopes specifying the level of application authorization to use the Allegro API.

To limit the application's access to only selected resources, you must provide the appropriate scope when obtaining authorization - separate each subsequent scope with space (“%20”). You can find the list of available scopes here.

From January 11th, 2021 on production environment you will have access only to resources, which scopes you provide in the request. If the required scope is not found on the list of scopes in the token, your request will be rejected with the error code 403. If you do not take any steps, your application will authorize itself with the full scope list every time.

Thanks to the implementation of the scope service, you will ensure an increase in the security of users who use Allegro API and applications that use our API.

You will find more information about scopes in our tutorial.

21DEC
2020

Sandbox - on January 5th, 2021 we will update the list of categories and parameters and remove all offers

On January 5th, 2021 we will update the list of categories and parameters on Sandbox. This will allow us to ensure consistency between test and production environments.

Note! Due to the update, we will remove all offers from Sandbox.

18DEC
2020

From January 18th, 2021 we will introduce new requirements for the % of offers assigned to a product

In 2019, we have introduced the Allegro Product Catalog in selected categories. Within Allegro Product Catalog we want to gather and describe all of the products that are available in the sellers listed offers. We catalog individual products as a representative, which differs from others with their properties, e.g. model, manufacturer's code, GTIN number, or other basic parameters.

We plan to catalog all offers where possible by the end of 2021. For this purpose, from September 1st, 2020 we have introduced a requirement for the % of offers assigned to a product. We already require 1% of offers assigned to a product in the following categories:

  • Electronics,
  • Culture and Entertainment,
  • Beauty,,
  • Sports and Travel,
  • Home and Garden,
  • Health,
  • Supermarket.

In some of the above categories, seller does not have to associate an offer with a product - you can find a list here.

From January 18th, 2021:

  • we will require 1% of offers associated with a product in selected sections in the following categories:
    • Kids,
    • Business and Services,
    • Automotive.
  • we will increase the requirement to 10% of cataloged offers in several categories, where we previously required 1%, i.e.:
    • Culture and Entertainment,
    • Supermarket,
    • Home and Garden,
    • Beauty.

We want to enable to associate offers with a product in as many categories as possible, but the specificity of the sold items not always allow it. See this file to check in which sections of the categories Kids, Business and Services, and Automotive we will enable the obligation of 1% of offers assigned to a product.

information

Note If a seller will not meet this condition, he will be able to list a new, similar or reslist an ended offer if he choose assign a product to an offer or adds a new product based on his offer.

You can find more information about how to assign an offer to a product in our guide. Check also POST /sale/product-offers resource, which allows you to list an offer assigned to a product with one request:

  • if the product already exists in our database, all you need to do is provide EAN code (or product ID), price and quantity,
  • if the product is not in our database, you need to provide product data, price, and quantity.

You can use GET /sale/offers with product.id.empty=true parameter to check which offers are not associated with a product.

You will find more information about this change on the for sellers page.

16DEC
2020

New delivery methods

Today we have introduced two new delivery methods for collecting your used car battery. You can get identifiers in the resource GET /sale/delivery-methods:

  • X-press Couriers (z odbiorem zużytego akumulatora) - id: 2a8cb7bf-a31b-45c3-b45e-7918ea717539
  • X-press Couriers (z odbiorem zużytego akumulatora) pobranie - id: 3d7c74e7-4d1b-4800-95a2-7918ea717539

You can find more information about this change here.

14DEC
2020

We are removing the current resource for checking future parameter requirements and will soon replace it with a new one

Today we removed the resource /sale/categories/parameters/required-change owing to which you could check future parameter requirements. We made this decision because we want the resource to be consistent with the current journals. In the near future, we will release a new resource, which we will inform you about in separate news.

8DEC
2020

Provide Authorization header correctly

From January 12th, 2021, we will introduce additional validation of the Authorization header. If in requests:

  • you do not put a space between "Bearer" and the token, e.g. Authorization: Bearer {token},
  • after 'Authorization' you provide more than one value, e.g. Authorization: Bearer mF_9.B6f-4.1JqM, Basic YXNkZnNhdGZzYWzmOlZLdDVOMVhx,
  • you submit more than one Authorization header,

in the response, we will return the 401 Unauthorized code.

Make sure you are properly providing this header in your application.

8DEC
2020

PATCH /sale/product-offers/{offer-id} - we update tecdocSpecification and compatibilityList

Starting today, when you use PATCH /sale/product-offers/{offer-id}, we will automatically update the tedocSpecification and compatibilityList fields in the offer, according to the assigned product data.

We introduce the change so that the data presented in the offer are up-to-date, and updating the offer is as simple as possible.

It is also the first step to the automatic update of data in the product-related offer that we announced. In the future, when we update the product data in the catalog and If you don’t provide your own values, you won’t need to copy or accept changes in your offers after we update the catalog.

You can read more about PATCH /sale/product-offers/{offer-id} in our guide.

27NOV
2020

We are changing the maximum length of the GTIN parameter

On January 18th, 2021 we will change the maximum length of GTIN parameters from the current 18 to 14 characters.

Depending on the category, the changes will affect the parameters:

  • EAN (parameter id=225693),
  • ISBN (parameter id=245669),
  • ISSN (parameter id=245673).

When you use GET /sale/categories/{categoryId}/parameters and GET /sale/categories/{categoryId}/product-parameters, we will return different information in the restrictions.maxLength field for each of the GTIN parameters:


      {
      ...
                  "restrictions": {
                      "minLength": 8,
                      "maxLength": 14,
      ...
                  }
      …
      }
                      

Thanks to this change, we will coherent the maximum and actually verified length of the GTIN parameter. The acceptable GTIN length is 8, 10, 12, 13, or 14 characters.

26NOV
2020

/sale/product-offers resources - beta.v1 will be disabled on December 12, 2020

According to our previous announcement, we remind you that from December 12th, 2020, we will stop supporting the beta.v1 version of the resources:

From November 12, 2020, you can use beta.v2 version of these resources. To start using it, change the data in Content-Type and Accept headers to “application/vnd.allegro.beta.v2+json”.

In the beta.v2 version, we implemented the asynchronous API pattern - make sure you handle it correctly. You can find more information about the new version of /sale/product-offers resources in our guide:

26NOV
2020

GET /payments/payment-id-mappings - we are turning off single purchase event mapping

From January 12th, 2021, you will not be able to use single purchase event mapping via GET /order/line-item-id-mappings. It allows mapping dealId and lineItemId between WebAPI and REST API Allegro.

We will disable this resource due to the complete shutdown of WebAPI Allegro. On January 13th, 2020, we disabled the last methods that used dealId.

The resource may currently generate delays due to increased traffic, so stop using it as soon as possible.

24NOV
2020

Complete your own brand in the offers or suggest your own parameters

We have introduced a change that allows you to suggest your own (custom) parameters along with values in all categories when you list or edit an offer. Additionally, you can add your own values to selected parameters and we will show them on the offer page. This option is available only for certain parameters which you can find here.

Take care of handling your own parameters and values in your application - this will have a significant impact on the shape of Allegro filters. We will collect suggestions of custom parameters and after the verification, we will add them to the standard list of parameters, which are visible on filters. Sellers often want their brands to be visible in search filters, so we will add the most popular own values to the list of available values in the filter.

Custom parameters

custom_parameters_listing_offer

custom_parameters_offer

You can add your own parameters, along with a specific value when you list or edit an offer. The functionality is available in all categories.


Sample structure, how to add your own parameter:


    {
      ...
      "parameters": [...],
      "customParameters": [
        {
          "name": "Name of your own parameter",
          "values": [
            "Value of your own parameter"
          ]
        }
      ],
      "description": {...},
     ...
   }
                  

Custom values

custom_values_listing_offer

custom_values_offer

You can add your own values for selected parameters with ambiguous values. Ambiguous value can be a value such as ”other”, “different pattern”, etc. You can retrieve its identifier via GET /sale/categories/{categoryId}/parameters in options section - field ambiguousValueId.

For now, you can provide your own value only for selected parameters. Information whether a parameter supports this functionality can be checked via GET /sale/categories/{categoryId}/parameters in the customValuesEnabled field in the options section.

Use this option when you list or edit an offer and choose “Other” as a parameter value. Owing to it, your value will be visible in brackets on the offer page. If it becomes popular, we will move it to the filters.

In the future, it will be necessary to provide your own value, if you choose an ambiguous parameter value. When you create a new product and select an ambiguous value, we always require you to provide your own value.


Sample structure, how to add your own parameter value:


        {
        ...
          {
            "id": "129033",                                  -- parameter ID
            "valuesIds": [
              "129033_13"                                    -- ambiguous value ID
            ],
            "values": [ "Missing brand name" ],              -- value, which you want to provide.
                                                             Complete this field.
            "rangeValue": null
          }
        ...
        }
                  

You can find more information about your own parameters and values in our tutorial:

20NOV
2020

Check offers unfilled parameters and future requirements

In response to your suggestions, today we have introduced two new resources to help manage sellers their offers:

  • GET /sale/offers/unfilled-parameters - check offers unfilled parameters. In response, we will return by default a list of 100 offers with unfilled required parameters and parameters that will be marked as mandatory in the next 3 months. Till the end of December we will introduce a filter, owing to which you will be able to choose which parameters you want to retrieve in response.
    If you want to retrieve data only for specific offers, use offer.id parameter, e.g. GET /sale/offers/unfilled-parameters?offer.id=123456789&offer.id=98765432

    Sample request:
    
        curl -X GET \
        'https://api.allegro.pl/sale/offers/unfilled-parameters?offer.id=123456789 \
        -H 'Authorization: Bearer {token}' \
        -H 'Accept: application/vnd.allegro.public.v1+json'
                          
    Sample response:
    
        {
          "offers": [
                 {
                "id": "123456789",      -- offer ID
                "parameters": [         -- information about unfilled parameters
                      {
                        "id": "14228"   -- parameter ID
                      }
                ],
                "category": {
                      "id": "257931"    -- category ID in which the parameter occurs
                }
                 }
        ],
         "count": 1,                    -- number of returned elements
         "totalCount": 1                -- total number of available elements
        }
                          
  • GET /sale/categories/parameters/required-changes - check which parameters will be marked as required in the next 3 months. To narrow the results to a specific time period, use the parameters:
    • scheduledFor.gte - the earliest date on which the parameter will be marked as mandatory,
    • scheduledFor.lte - the latest date, on which the parameter will be marked as mandatory. Should be less than 3 months from current date,
    • e.g. to check which parameters will become mandatory by the end of December, you need to make a following request GET /sale/categories/parameters/required-changes?scheduledFor.lte=2020-12-31T23:59:59Z

    Sample request:
    
        curl -X GET \
        'https://api.allegro.pl/sale/categories/parameters/required-changes \
        -H 'Authorization: Bearer {token}' \
        -H 'Accept: application/vnd.allegro.public.v1+json'
                          
    Sample response:
    
        {
         "changes": [
            {
                "category": {           
                    "id": "1521"                            -- category ID in which the
                                                            parameter will be mandatory
                      },
                "parameter": {
                    "id": "219809"                          -- parameter ID that will be mandatory
                    },
                "scheduledAt": "2021-02-19T23:00:00Z"       -- date from which parameter will be
                                                            marked as mandatory
                 },
            …
             ]
        "count": 10,                                        -- number of returned elements
        "totalCount": 10                                    -- total number of available elements
        }
                          

Owing to the introduced resources, the seller will be able to react faster to changes on our platform, thanks to which he will avoid problems such as, for example, a stock change in offers in which the required parameters are not provided.

We have added information about new resources in our guide.

17NOV
2020

New resources to promote offers

Today we have introduced changes in the promo options:

  • we have added Flexible Emphasized. Owing to it, the seller is able to promote an offer for as many days as he wants, because we will charge a fee for this promo option every day;
  • Bold and Highlight options are available only in the Promo package. If at the time of implementing this change, a seller will promote his offers via those options, they will remain active and visible for buyers till the end of a cycle and then automatically disabled;
  • a seller is able to decide if he wants to disable the promotion package immediately or after the end of the cycle;
  • a seller can disable promo options also in ended offers.

This will make it easier for the seller to manage the offer promo options - he will react faster to changes in sales and will promote offers only when considers it profitable.

Due to the changes, today we have released new API resources for managing promo options:

Below you will find the names of promo options in API, that we have prepared for the new resources. These are three packages of distinctions and one additional option:

  • Flexible Emphasized - for which we charge a fee every day;
  • Emphasized - for which we charge a fee every ten days;
  • Promo package - (Emphasized + Highlight + Bold), for which we charge a fee every day;
  • Department page promo - additional option, for which we charge a fee every ten days;

The change does not affect the offer model. You will still change the promo option using the current API - as before, we will make the change immediately.

You can find more information about managing promo options in our tutorial.

13NOV
2020

Add a tracking number easier

From today you can add a tracking number more easily. You no longer need to enter the next lineItems.id included in the order. Use POST /order/checkout-forms/{id}/shipments and send in a request only required values (carrierId and waybill) - we will assign a tracking number to each lineItem.id from your order.

Sample request:

curl -X POST \    
https://api.allegro.pl/order/checkout-forms/31896452-2de1-11e9-bced-352ab82ad9cd/shipments \
-H 'Authorization: Bearer {token}' \
-H 'Content-Type: application/vnd.allegro.public.v1+json' \
-H 'Accept: application/vnd.allegro.public.v1+json' \
-d '{
    "waybill": "12345678910PL",
    "carrierId": "DHL"            
}’

Sample response:

{
    "waybill": "12345678910PL",
    "carrierId": "DHL",
    "lineItems": [
            {
                "id": "31896450-2de1-11e9-bced-352ab82ad9cd"
            },
            {
                "id": "5b1f4a62-6969-11e8-b090-8b2d9f391430"
            }
    ],
    "createdAt": "2020-10-27T11:46:48.264Z",
    "id": "REhMOjEyMzQ1Njc4OTEwUEw="           
}
12NOV
2020

A new version of /sale/product-offers resources - asynchronous API

From today you can use beta.v2 version of the following resources:

In the beta.v2 version, we implemented the asynchronous API pattern due to the longer duration of some operations on the Allegro platform, such as e.g. changes in the publication status of the offer.

Note! We will disable the beta.v1 version on December 12th, 2020.

Change the data in Content-Type and Accept headers to “application/vnd.allegro.beta.v2+json” to start using beta.v2 version.

You will receive one of three statuses in beta.v2, in response to a valid request to the sale/product-offers:

  • 200 OK - we will implement the changes immediately. Only occurs with the PATCH method,
  • 201 Created - we will create an offer immediately. Only occurs with the POST method,
  • 202 Accepted - we will perform the task asynchronously due to the longer duration of the operation. Occurs with the POST and PATCH methods.

Along with the 202 Accepted status, we will return the Location header in the response, in which you will find a link to the new resource - /sale/product-offers/{offerId}/operations/{operationId}. Use the GET method on it to check the task status. In response, you will receive one of two statuses:

  • 202 Accepted - the operation has not been completed yet. Repeat the previous request.
  • 303 See Other - the operation is finished. In the Location header, we will return a link to the new resource - /sale/product-offers/{offerId}. Use the GET method on it and in the response you will receive the current offer data.

You can find more information about the new version of /sale/product-offers resources in our guide:

2NOV
2020

Large order discount for B2B transactions

From today you can add a large order discount to your offers. Thanks to it, you will offer a discount for buyers during B2B transactions (company - company). To create a large order discount, please use POST /sale/loyalty/promotions and define the single order value thresholds and percentage discount for them. Large order discount will be applied to all of your offers.

Sample request:

curl -X POST
'https://api.allegro.pl/sale/loyalty/promotions' \
-H 'Accept: application/vnd.allegro.public.v1+json' \
-H 'Content-Type: application/vnd.allegro.public.v1+json'  \
-H 'Authorization: Bearer {token}' \
-d '{
    "benefits": [
      {
        "specification": {
            "type": "LARGE_ORDER_DISCOUNT",    -- promotion type (list of available values
                                               can be be found in resource documentation)
            "thresholds": [                    -- discount thresholds
              {
                "orderValue": {
                    "lowerBound": {
                        "amount": "1000.00",   -- order value
                        "currency": "PLN"
                    }
                },
                "discount": {
                    "percentage": "5"          -- discount percentage (%)
                }
            },
            {
                "orderValue": {
                    "lowerBound": {
                        "amount": "1500.00",
                        "currency": "PLN"
                    }
                },
                "discount": {
                    "percentage": "8"
                }
            }
            ]
        }
    }
    ],
    "offerCriteria": [
      {
        "type": "ALL_OFFERS"                   -- discount will be applied
      }                                        to all of your offers
    ]
}'

In response, you will receive the ID of the created large order discount.

Sample response:

{
    "id": "ba01f101-c9ef-4e5d-a88f-efb721bdbb9a",    -- large order discount ID
    "createdAt": "2020-10-27T06:31:29.36Z",          -- creation date
    "benefits": [
      {
        "specification": {
            "thresholds": [
              {
                "orderValue": {
                    "lowerBound": {
                        "amount": "1000.00",
                        "currency": "PLN"
                    }
                },
                "discount": {
                    "percentage": "5"    
                }
            },
            {
                "orderValue": {
                    "lowerBound": {
                        "amount": "1500.00",
                        "currency": "PLN"
                    }
                },
                "discount": {
                    "percentage": "8"
                }
            }
            ],
            "type": "LARGE_ORDER_DISCOUNT"
        }
    }
    ],
    "offerCriteria": [
      {
        "type": "ALL_OFFERS"
      }    
    ]
    "status": "ACTIVE"
}

You will find more information about large order discount and resources to manage it in our tutorial.

30OCT
2020

Buyer can change shipping data - update

According to our previous announcement, we will allow buyers to change the address in the shipping form data in January 2021. We made the decision to change the implementation date due to the extension of the time needed to implement the solution in integrations.

23OCT
2020

POST /sale/product-offers and PATCH /sale/product-offers{offer-id} - we added support for more fields (VAT rate and offer duration) that you can send in the request

In response to your suggestions, we have added in:

support for two more offer attributes: VAT rate and offer duration. You can set these attributes in the offer if you declare the fields in the request structure:

  • tax.percentage - VAT rate,
  • publication.duration - offer duration.

You can find more information about new fields in our guide.

19OCT
2020

POST /sale/product-offers oraz PATCH /sale/product-offers/{offerId} - we added size table support

Today we have introduced a sizeTable section in the POST /sale/product-offers and PATCH /sale/product-offers/{offerId} structure. Owing to it you can add a defined size table to your offer. As with the other fields in this resource - provide the name or id of the size table.

You can find more information about a new section in our guide.

15OCT
2020

GET /sale/categories/{categoryId}/parameters - we have added new fields for handling dependent parameters

On November 16th, 2020 we plan to introduce the next stage of handling the dependent parameters - a conditional obligatory and display. You can read more information about dependent parameters in our previous news. Owing to the dependent parameters we will simplify navigation and buyers will be able to compare offers that so far are in various categories. In addition, sellers will be able to provide complete and adequate data to their offers, which will correspond to the nature of their product. As a result, buyers will find well-described offers easier.

A conditional obligatory means that the requirement of the parameter depends on the value chosen for the conditioning parameter, e.g. if the seller will choose “State” as “New”, then he should also know what is the “Manufacturer Code” value, so we will mark it as a mandatory. If he will choose “Used”, then the “Manufacturer Code” will be optional, for example, in the case when the product has a frayed label.

A conditional display means that the visibility of the parameter depends on the value chosen for the conditioning parameter, e.g. if in the “Soaps” category (258383) for the “Type” parameter seller will choose “bar”, we will display the “Weight” parameter and hide “Volume”. On the other hand, if the seller will choose the value “liquid” or “paste”, then we will hide the "Weight" parameter and show "Volume".

Therefore, we added new fields to GET /sale/categories/{categoryId}/parameters:

  • options.requiredDependsOnValueIds - in which we will return the value identifiers of the conditioning parameter, which determines whether a parameter will be required, e.g. ID of the value “New” for the “State” parameter,
  • options.displayDependsOnValueIds - in which we will return a set of values identifiers of the conditioning parameter, which determines whether a parameter will be visible, e.g. if this field applies to the “Volume” parameter in the “Soaps” category, we will return identifiers of the “liquid” and “paste” values for the “Type” parameter.

You can find a list of the first categories and parameters for which we will introduce conditional obligatory and display on for sellers page.

Sample response structure:

{
  "parameters": [
    {
      "id": "202877",
      "name": "Liczba rdzeni procesora",
      "type": "integer",
      "required": false,
      "requiredForProduct": false,
      "unit": null,
      "options": {
        "variantsAllowed": true,
        "variantsEqual": false,
        "ambiguousValueId": null,
        "dependsOnParameterId": "202870",
        "requiredDependsOnValueIds": [
          "202870_1"
        ],
        "displayDependsOnValueIds": [
          "202870_1",
          "202870_2"
        ],
        "describesProduct": false
      },
      "restrictions": {s
        "min": 0,
        "max": 1000000,
        "range": false
      }
    }
  ]
}
     
9OCT
2020

PATCH/sales/product-offers/{offer-id} - new resource for offer edition

Today, in addition to the POST /sale/product-offers resource previously provided by us, we have introduced a new resource PATCH /sale/product-offers/{offer-id}. Owing to it, you can easily edit your offer - you can change any field of the offer, and at the same time, you don't have to pass its entire structure.

If you use PATCH /sale/product-offers/{offer-id} and do not provide a field value - we will keep the current value of this field in the offer and change only those in which you provide a value different than before. On the other hand, when you pass a null value - we will remove the current value of the field from the offer, unless the field is required.

Thanks to this approach, you can independently edit any field in the offer, including:

  • photos,
  • parameters,
  • location,
  • price,
  • description of the offer.

We wanted to provide the same facilities as when creating offers by POST /sale/product-offers, resource, therefore PATCH /sale/product-offers/{offer-id} for example, allows you to change the offer status without having to use a separate publication command, or to add images to the offer directly from external server.

You can find more information about PATCH /sale/product-offers/{offer-id} in our guide.

8OCT
2020

New section “discounts” in an offer

Today, in the offer model, we have introduced a new section discounts, in which we return information about the discounts assigned to the offer. Currently, in the section, you will find the id of the wholesale price list added to the offer. If it is missing, we will return null value.

Offer model after change:

...
   "discounts": {
       "wholesalePriceList": {
           "id": "5637592a-0a24-4771-b527-d89b2767d821"
       }
   },
...

Thanks to the change, you can easily add a wholesale price list when listing or editing an offer.

You will find more information about wholesale price lists in our tutorial.

6OCT
2020

Scope in the Allegro API

Today on the test environment (allegro.pl.allegrosandbox.pl) we have introduced the functionality of the scopes, i.e. scopes specifying the level of application authorization to use the Allegro API. Each scope is assigned a set of permissions that define:

  • a set of resources that can be accessed using scope,
  • a set of operations that can be performed in scope.

So far, each of the applications registered on the Allegro Sandbox Application Management website (Zarządzanie aplikacjami Allegro Sandbox) asked for access to all Allegro scopes available in the API. From now on, you can only apply for scopes that are actually necessary for the proper functioning of the application. To limit the application's access to only selected resources, you must provide the appropriate scope when obtaining authorization - separate each subsequent scope with space (“%20”). You can find the list of available scopes here.

Sample request that allows the application to access only resources for managing offers and reading orders:
https://allegro.pl.allegrosandbox.pl/auth/oauth/authorize?response_type=code&redirect_uri=http://www.example.com&client_id=438f71d3a26e4d829783a0a621873465&scope=allegro:api:sale:offers:write%20allegro:api:orders:read

From January 11th, 2021 on production environment you will have access only to resources, which scopes you provide in the request. If the required scope is not found on the list of scopes in the token, your request will be rejected with the error code 403.

Therefore, start work on the correct support of scope by your software today. If you do not take any steps, your application will authorize itself with the full scope list every time. We will display them to the user on the consent screen when confirming the connection of the application with the user's account and in the list of applications in the tab Linked Apps. Make sure you use only the necessary scopes - thanks to this you will limit the number of questions from users and rejected application associations. Thanks to the implementation of the scope service, you will ensure an increase in the security of users who use Allegro API and applications that use our API.

You will find more information about scopes in our tutorial.

2OCT
2020

POST /sale/products-offers - if you provide your own description in the request, we will not combine it with the description from our product database

Up to this date, we combined both the description provided in the request and the product description. In response to your suggestions, from now on, we will present the product description in the offer only if you do not provide your own description in the description section.

You can find more information about POST /sale/product-offers in our guide.

2OCT
2020

Sandbox - technical break

On October 6th, 2020 at 07:00 AM we will start a technical break for the test environment, which will last about 1 hour. We are sorry for the inconvenience.

1OCT
2020

Sandbox - buyer can change shipping data

In the second half of October, we will allow buyers to change the address in the shipping form data. The customer will be able to change the shipping data for the order in the READY FOR PROCESSING status, if, for example, previously provided incorrect information. As in the order cancellation, certain conditions will have to be meet:

  • seller has a company account;
  • order fulfillment status (“fulfillment.status”) is different than: PROCESSING, READY_FOR_SHIPMENT, SENT;
  • seller has not added tracking number to the order.
  • change of address is available within 3 days from the date of purchase.

The feature is now available in our test environment. Therefore, for:

  • GET /order/events - we added a new event type "BUYER_MODIFIED", which you will receive when the buyer changes the address;
  • GET /order/checkout-forms and GET /order/checkout-forms/{id} - in delivery.address section we added a new field - modifiedAt, in which we return:
    • the date when the buyer changed the data in the order;
    • null for orders without buyer modification.
    We also added this field to the production environment, but until the functionality is available to buyers, we will always return null.

To change the shipping data as a buyer, go to purchase details in the Your Purchases tab and choose “Change” below the customer data.

23SEP
2020

Changes to e-mail notifications

Today, Allegro has introduced new consents that you can manage in the tab Consents to Notifications. From now on, you can decide which notifications about your offers you need for your work. New consents:

  • when you list an offer or ad,
  • when your offer or ad is automatically renewed,
  • when your offer or ad is finished,

are disabled by default on a company account. You can change it in the tab Consents to Notifications.

You will find more information about changes on Allegro news page.

22SEP
2020

Sandbox - technical break

On September 24th, 2020 at 07:00 AM we will start a technical break for the test environment, which will last about 1 hour. We are sorry for the inconvenience.

17SEP
2020

From October 14th, 2020 we will require 1% of offers assigned to a product in the next categories

Since the beginning of 2019, we have been creating solutions that help assign items from Allegro’s offers to products from our database. Owing to it, sellers can list their offers faster and it is easier for the customers to find the product that meets their needs. We plan that in 2021 all offers in selected categories will be associated with our database.

We already require 1% of offers to be assigned to products in:

  • Electronics,
  • Culture and Entertainment,
  • Beauty.

From October 14, we will require 1% of offers assigned to products in the following categories:

  • Sports and Travel,
  • Home and Garden,
  • Health,
  • Supermarket.

We will not require it in some categories - you will find a list of them in this file.

information

Note! If a seller won’t meet this condition, it will be not available to list new offers in those categories (excluding the categories from the file), if current offers aren’t assigned to a product.

You can find more information about how to assign an offer to a product in our guide. Recently we have introduced new resource POST /sale/product-offers, which allows you to list an offer assigned to a product with one request:

  • if the product already exists in our database, all you need to do is provide EAN code (or product ID), price and quantity,
  • if the product is not in our database, you need to provide product data, price, and quantity.
16SEP
2020

We have introduced a new resource that allows you to retrieve the suggested categories for the given phrase

Today we have introduced a new resource GET /sale/matching-categories that allows you to retrieve the suggested categories in which you can list your product from the given phrase. Owing to this you can easier and faster identify the appropriate category.

In the request, pass the name parameter in which you will provide the searched phrase, e.g. name = bmw x3. In response, you will receive a list of suggested categories.


Sample request:

curl -X GET \
    'https://api.allegro.pl/sale/matching-categories?name=bmw x3' \
    -H 'Authorization: Bearer {token}' \
    -H 'Accept: application/vnd.allegro.public.v1+json'

Sample response:

{
  "matching_categories": [
    {
      "id": "250885",                   -- id of the suggested category.
      "name": "Wahacze",                -- name of the suggested category.
      "parent": {                       -- parent category in relation to the
                                        suggested category: owing to this
                                        object you will know the exact
                                        suggested category path.
        "id": "250882",                 -- id of the parent category.
        "name": "Wahacze i elementy",   -- name of the parent category.
        "parent": {
          "id": "8683",
          "name": "Układ zawieszenia",
          "parent": {
            "id": "620",
            "name": "Części samochodowe",
            "parent": {
              "id": "3",
              "name": "Motoryzacja",
              "parent": null
            }
          }
        }
      }
    },
    . . .
     {
      "id": "255100",
      "name": "Lampy przeciwmgielne",
      "parent": {
        "id": "255098",
        "name": "Lampy przednie i elementy",
        "parent": {
          "id": "623",
          "name": "Oświetlenie",
          "parent": {
            "id": "620",
            "name": "Części samochodowe",
            "parent": {
              "id": "3",
              "name": "Motoryzacja",
              "parent": null
            }
          }
        }
      }
    }
  ]
}
15SEP
2020

We have introduced a new resource that allows you to retrieve the suggested compatibilityList section

Today we have introduced a new resource GET /sale/compatibility-list-suggestions that allow you to retrieve the suggested compatibilityList section. Use this endpoint when you don’t have a compatibilityList section in your offer. Owing to the completed compatibilityList section, it is easier for the customers to find the product they are interested in. We create suggestions on the basis of compatibility lists from the other sellers offers. You can modify the list according to your needs, e.g. remove or add some of the elements.

Pass in the request one of the parameters on the basis of which we will return the suggested compatibilityList section:


Sample request:

curl -X GET \
    'https://api.allegro.pl/sale/compatibility-list-suggestions?offer.id=6505550901' \
    -H 'Authorization: Bearer {token}' \
    -H 'Accept: application/vnd.allegro.public.v1+json'

Sample response:

{
    "type": "MANUAL",
    "items": [
        {
            "type": "ID",
            "id": "73ff4bae-958d-4b75-a49c-d0c11fdd233c",
            "text": "Toyota AVENSIS (_T22_) 2.0 VVT-i (AZT220_) (1AZ-FSE) 1998ccm 150KM/110kW 2000/10-2003/02",
            "additionalInfo": []
        },
        {
            "type": "ID",
            "id": "de7a2247-78fa-4a12-94f1-f43b5f33ac7e",
            "text": "Toyota AVENSIS (_T22_) 2.0 TD (CT220_) (2C-TE) 1975ccm 90KM/66kW 1997/09-2003/02",
            "additionalInfo": []
        }
    ]
}

The received list can be used when you list or edit an offer.

10SEP
2020

Wholesale price list for B2B transactions

From today you will add wholesale price lists to your offers. Thanks to them, you will offer a discount during B2B transactions (company - company). To create a wholesale price list, please use POST /sale/loyalty/promotions and define the quantitative thresholds and the percentage discount applicable to them.

Sample request:

curl -X POST
'https://api.allegro.pl/sale/loyalty/promotions' \
-H 'Accept: application/vnd.allegro.public.v1+json' \
-H 'Content-Type: application/vnd.allegro.public.v1+json' \
-H 'Authorization: Bearer {token}' \
-d '{
 "benefits": [
    {
      "specification": {
          "type": "WHOLESALE_PRICE_LIST",        -- promotion type (list of available values
                                                 can be found in resource documentation)
          "name": "Price list number 1",         -- wholesale price list name
          "thresholds": [                        -- discount thresholds
              {
                "quantity": {                    -- minimum quantity purchased items
                    "lowerBound": 5
                },
                "discount": {                    -- discount percentage (%)
                    "percentage": "5"
                }
              },
              {
                "quantity": {
                    "lowerBound": 10
                },
                "discount": {
                    "percentage": "8"
                }
              }
            ]
          }
    }
  ],
  "offerCriteria": [
    {
      "type": "OFFERS_ASSIGNED_EXTERNALLY"        -- you will assign offers via
    }                                             PUT /sale/offer-modification-commands/{commandId}
  ]
}'

In response, you will receive the ID of the created wholesale price list.

Sample response:

{
    "id": "9de4be5d-9c60-48aa-8711-363625c9d793",    -- wholesale price list ID
    "createdAt": "2020-08-13T06:08:06.011Z",         -- creation date
    "benefits": [
        {
            "specification": {
                "name": "Price list number 1",
                "thresholds": [
                    {
                        "quantity": {
                            "lowerBound": 5
                        },
                        "discount": {
                            "percentage": "5"
                        }
                    },
                    {
                        "quantity": {
                            "lowerBound": 10
                        },
                        "discount": {
                            "percentage": "8"
                        }
                    }
                ],
                "type": "WHOLESALE_PRICE_LIST"
            }
        }
    ],
    "offerCriteria": [
        {
            "type": "OFFERS_ASSIGNED_EXTERNALLY"
        }
    ],
    "status": "ACTIVE"
}

You will assign the created wholesale price list to selected offers using the resource responsible for group changes in the offers - PUT /sale/offer-modification-commands/{commandId}.

Sample request:

curl -X PUT \
'https://api.allegro.pl/sale/offer-modification-commands/daccd266-fa5e-4a6b-a10b-d24836c411e1' \
  -H 'Authorization: Bearer {token}' \
  -H 'Accept: application/vnd.allegro.public.v1+json' \
  -H 'Content-Type: application/vnd.allegro.public.v1+json' \
  -d '{
 "modification": {
   "discounts": {                                          -- change type
     "wholesalePriceList": {                    
       "id": "9de4be5d-9c60-48aa-8711-363625c9d793"        -- wholesale price list ID
     }
   }
 },
 "offerCriteria": [
   {
     "offers": [
       {
         "id": "9292002929"                                -- offer ID
       },
       {
         "id": "9876543210"
       }
     ],
     "type": "CONTAINS_OFFERS"
   }
 ]
}'
information

Note! Currently, you will not receive information about the wholesale price list assigned to the offer in response to GET /sale/offers/{offerId}.

You will find more information about wholesale price lists and resources to manage them in our tutorial.

10SEP
2020

GET /sale/offers - new filtering options

Today in GET /sale/offers we have introduced new options for filtering offers by:

  • category.id - you can find offers that belong to a given category,
  • product.id.empty - you can search for offers that do not have an assigned product (product.id),
  • productizationRequired - you can filter out offers that belong to the categories where productization is mandatory.

For example, if you would like to search for offers that belong to the 260660 category, do not have a product assigned, and must meet the product binding requirement, you just need to call:

GET /sale/offers?category.id=260660&product.id.empty=true&productizationRequired=true

8SEP
2020

We removed the parameter user.id / seller.id from the calls

According to your suggestions, starting today, you no longer need to pass the parameter when calling the following resources:

If you still pass user.id or seller.id in your call, we will also return the correct response.

1SEP
2020

Wysyłam z Allegro - new tool for managing parcels

Wysyłam z Allegro is a tool that facilitates parcel management on Allegro. Sellers can prepare parcels and print labels there and order a pickup of parcels from the indicated address by carriers. We will automatically add the tracking numbers to the appropriate orders. You can read more about this tool on the Sellers Page.

Learn more about API resources in the new guide.

Before you start using API Wysyłam z Allegro, activate your account via:

28AUG
2020

Check whether you can add your own value for the parameter with an ambiguous value

Today we have introduced a new field customValuesEnabled in options section in the response to GET /sale/categories/{categoryId}/parameters. Owing to it, you can check whether you can add your own value for a parameter with an ambiguous value in a given category.

Ambiguous value is for example “other” in the parameter “Brand”. You can retrieve its identifier via GET /sale/categories/{categoryId}/parameters in options section - field ‘ambiguousValueId’.

You can check how to add your own value for a parameter with an ambiguous value in our guide.

27AUG
2020

GET /offers/listing - search for offers by the seller login

According to your suggestions, we have introduced in GET /offers/listing possibility to search for offers by the seller login. Until now, it was possible to search for offers of a given seller only by ID.

Sample request:

  curl -X GET \
  'https://api.allegro.pl/offers/listing?seller.login=Allegro' \
  -H 'Authorization: Bearer {token}' \
  -H 'Accept: application/vnd.allegro.public.v1+json'
27AUG
2020

Sandbox - technical break

On September 3rd, 2020 at 07:00 PM we will start a technical break for the test environment, which will last about 1 hour. We are sorry for the inconvenience.

18AUG
2020

We removed delivery methods “Kurier wieczór” and “Kurier wieczór pobranie”

According to our previous announcement today we have removed delivery methods:

  • “Kurier wieczór”,
  • “Kurier wieczór pobranie”.
17AUG
2020

Dynamic Client Registration

We have introduced a new type of authorization - Dynamic Client Registration. It is an extension to the OAuth2 standard that allows you to create automatically an instance of your application. If the client installs a copy of your software directly (e.g. an instance of a store platform in their own infrastructure), this type of authorization is just for you. DCR ensures full security of data authorization, and at the same time does not force each client to manually generate separate access data (client ID and client secret).

You can find more information about DCR in our tutorial.

7AUG
2020

POST /sale/offers - we have added a new field “warnings” in response

In response to POST /sale/offers we have added a new field “warnings” in the validation section. We inform in it whether the description of the offer contains any content that may violate the existing rules of Allegro. Phrases that may cause us to display a message include for example:

  • EAN,
  • return policies,
  • link to the website,
  • information about shipping,
  • size-tables.

Note! You will be still able to list the offer for which we return information in the warnings field.

We have introduced this field because we want sellers to be able to pay attention to their offer content at the very first stage - when they create a new offer. The message will allow sellers to avoid further sanctions imposed by Allegro if they list an improper offer.

Sample response structure:

{
   "validation": {
       "errors": [],
       "warnings": [
           {
               "code": "VALIDATION_WARNING",
               "message": "Wystawiany przedmiot znajduje się w wykazie produktów leczniczych, środków spożywczych specjalnego przeznaczenia żywieniowego oraz wyrobów medycznych zagrożonych brakiem dostępności na terytorium Rzeczypospolitej Polskiej. Jeżeli zdecydujesz się wysłać go za granicę masz obowiązek powiadomienia o tym fakcie Główny Inspektorat Farmaceutyczny. Musi to nastąpić przed zamiarem wywozu lub zbycia produktu poza terytorium Rzeczypospolitej Polskiej.",
               "details": "",
               "path": "",
               "userMessage": "Wystawiany przedmiot znajduje się w wykazie produktów leczniczych, środków spożywczych specjalnego przeznaczenia żywieniowego oraz wyrobów medycznych zagrożonych brakiem dostępności na terytorium Rzeczypospolitej Polskiej. Jeżeli zdecydujesz się wysłać go za granicę masz obowiązek powiadomienia o tym fakcie Główny Inspektorat Farmaceutyczny. Musi to nastąpić przed zamiarem wywozu lub zbycia produktu poza terytorium Rzeczypospolitej Polskiej."
           }
       ],
       "validatedAt": "2017-11-08T18:03:39.68Z"
       }
     }
6AUG
2020

Add your own parameter via REST API

Today we have introduced custom parameters - you can add them when you list or edit an offer. Owing to it descriptions of the offers will be more precise and it will make the purchase decision easier for the buyer We will collect suggestions of custom parameters and after the verification, we will add them to the standard list of parameters.


Remember, custom parameters:
  • can be provided only in selected categories. In response to GET /sale/categories and GET /sale categories/{id} we have added new field - customParametersEnabled in which you can check whether we have enabled custom parameters in a given category,
  • you will add in customParameters field in the offer model. The parameter will be visible on the offer page.
  • have the same limit as in the sales form on the website - you can add up to 4 custom parameters for which you can provide one value,
  • can’t be duplicates - if parameters with this name already exist in Allegro, we will return an appropriate error. However, you can add custom parameters with the same name to the different offers.

Sample request structure:
{
...
"parameters": [...],
"customParameters": [
    {
      "name": "Name of your own parameter",
      "values": [
        "Value of your own parameter"
      ]
    }
  ],
"description": {...},
…
}
Sample response structure:

{
...
"parameters": [...],
"customParameters": [
    {
      "name": "Name of your own parameter",
      "values": [
        "Value of your own parameter"
      ]
    }
  ],
"description": {...},
…
}
29JUL
2020

WebAPI phase out

We will disable Allegro WebAPI from:

  • 1.09.2020 on Sandbox.
  • 26.10.2020 on production environment.

We have updated the terms because from October, there will be no methods left in WebAPI that justify longer maintenance.

On October 26th, 2020 we will also disable WebAPI methods for:

Due to low usage, we do not plan to release the equivalent in REST API. You can check the current data settings for withdrawals in My Allegro. If you want to receive daily payouts, all you need to do is select up an automatic payout option.

24JUL
2020

Sandbox - technical break

On July 30th, 2020 at 09:00 AM we will start a technical break for the test environment, which will last about 2 hours. We are sorry for the inconvenience.

23JUL
2020

On August 18th, 2020, we are going to remove delivery methods “Kurier wieczór” and “Kurier wieczór pobranie”

On August 18th, 2020, we are going to remove delivery methods:

  • “Kurier wieczór”,
  • “Kurier wieczór pobranie”.

From August 4th, 2020, when you create or edit shipping price list, which includes one of these methods, we will return status 422 with an appropriate error message:

"errors": [
        {
            "code": "DEPRECATED_DELIVERY_METHOD",
            "message": "Kurier wieczór pobranie is deprecated.",
            "details": null,
            "path": "rates[5].deliveryMethod.id",
            "userMessage": "Metoda dostawy \"Kurier wieczór pobranie\" nie jest już dostępna."
        },
        {
            "code": "DEPRECATED_DELIVERY_METHOD",
            "message": "Kurier wieczór is deprecated.",
            "details": null,
            "path": "rates[10].deliveryMethod.id",
            "userMessage": "Metoda dostawy \"Kurier wieczór\" nie jest już dostępna."
        }
    ]
15JUL
2020

GET /order/checkout-forms - filter orders by multiple values

As of today, you can provide multiple values for filters in GET /order/checkout-forms:

  • status - e.g. GET /order/checkout-forms?status=BOUGHT&status=FILLED_IN - will return all orders in BOUGHT and FILLED_IN status,
  • fulfillment status - e.g. GET /order/checkout-forms?fulfillment.status=NEW&fulfillment.status=PROCESSING - will return all orders for which fulfillment status is NEW or PROCCESSING.

You can find more information about filters for orders in our guide.

14JUL
2020

Batch offer modification - change VAT rate

We have introduced the option of editing the VAT rate in many offers. To make a change use PUT /sale/offer-modification-commands/{commandId} and during a batch offer modification enter in the field:

  • “invoice” - “VAT” as an invoice type,
  • “tax” - value of the VAT rate. You can use only the following VAT rates specified by Polish law (0%, 5%, 8%, 23%).

Sample request:

curl -X PUT \
  ‘https://api.allegro.pl/sale/offer-modification-commands/{commandId}’ \
  -H 'Authorization: Bearer {token}' \
  -H 'Accept: application/vnd.allegro.public.v1+json' \
  -H 'Content-Type: application/vnd.allegro.public.v1+json' \
  -d '{
    "modification": {
        “payments": {
            "invoice": "VAT",
            "tax": {
            "percentage": "23.00"
               }
        },
   },
    "offerCriteria":[
      {
        "type":"CONTAINS_OFFERS",
        "offers":[
        {
        "id":"7531636067"
        },
        {
        "id":"7512439587"
        }
     ]
     }
     ]
  }’

Owing to the change, in the future we will show in the offers the VAT rate and net price of the product.

Note! Remember the transaction with the customer is settled on the gross price basis (including VAT). We provide a net price for informational purposes.

13JUL
2020

From July 20th, 2020, we will validate dependent parameters

Dependent parameters are currently available only in one category - Ear Clips (123428). If you select the value of the main parameter (Material):

  • “Gold”, “Pink Gold” or “White Gold” - you will be able to provide value for “Gold Hallmark” parameter,
  • “Silver”, “Tibetan Silver” or “Silver-gilt” - you will be able to provide value for “Silver Hallmark” parameter,

From July 20th, 2020, we will validate dependent parameters. It means that you will be able to choose:

  • “Gold Hallmark” parameter, only if you select the value associated with gold for the "Material" parameter,
  • “Silver Hallmark” parameter, only if you select the value associated with silver for the "Material" parameter,
  • both parameters, if you choose values associated with gold and silver,
  • none of these parameters if "Material" is not associated with either gold or silver.

If you choose an invalid dependent parameter, we will return an appropriate error, for example:

 “Dependent parameter 206646 cannot take values [999] when parameter 15835 has values [Glass, Steel].”

You can find more information about dependent parameters in our news.

6JUL
2020

Sandbox - technical break

On July 10th, 2020 at 09:00 AM we will start a technical break for the test environment, which will last about 2 hours. We are sorry for the inconvenience.

29JUN
2020

On September 30th, 2020 we are going to remove WebAPI methods for retrieving Public sales data

On September 30th, 2020 we are going to remove the following WebAPI methods:

  • doGetSiteJournal,
  • doGetSiteJournalInfo,
  • doShowItemInfoExt,
  • doGetItemsInfo,
  • doGetBidItem2.

We will not provide equivalents for these methods in the REST API. At present, any user, e.g. any seller, is able to retrieve and analyze data on any transactions concluded on the website by any other seller. In particular, due to the sensitivity of this information, we have decided to change our approach - from October 1st, 2020, transaction data will not be publicly available.

Note! Every seller on Allegro will still have access to data on their sales - both in the tools provided by Allegro and in Allegro API resources.

You can find more information about limiting access to sensitive transaction data on the for sellers page.

29JUN
2020

GTIN parameter in offers and products

According to our previous announcement today we have introduced the Global Trade Item Number (GTIN) parameter. In most categories, we marked it as a basic parameter, which identifies the product in an offer. If you want to add or change GTIN parameter use the available parameters (depending on category):

  • EAN (parameter id=225693),
  • ISBN (parameter id=245669),
  • ISSN (parameter id=245673).

You can check parameters available in a given category by GET /sale/categories/{categoryId}/parameters.


GTIN in offers

In offers, GTIN parameter overrode “ean” field, whose values were transferred to the new parameter. You can only fill in the EAN, ISBN, ISSN value in the GTIN parameter. To do so retrieve an offer via GET /sale/offers/{offerId} and then edit it by PUT /sale/offers/{offerId}. If you try to change the value of the "ean" field in the offer, you will receive an error message: "Ean field is read-only. Set this value in parameter with id: {id}."

If you use in your integration the "ean" to recognize your offers (as so-called signature), switch to the "external.id" field, which is dedicated to the signature.

GTIN in products

The GTIN parameter for products functions in parallel with the existing "eans" array. We transferred the current values of "eans" to the new parameter. If you propose a product via POST /sale/product-proposals you can submit EAN, ISBN or ISSN value only in the GTIN parameter.

The GTIN parameter received the "isGTIN" flag in the "options" structure of the product parameters. Owing to it, when you will add an offer based on a product, you will recognize if a parameter has many values, you can only use one of them.

Sample request:

curl -X GET \
        ‘https://api.allegro.pl/sale/products/0ca14fc3-7084-4fa2-83da-d04104e8b162’ \
        -H 'Accept: application/vnd.allegro.public.v1+json'

Sample response:

...
"parameters": [
{
    "id": "225693",
    "name": "EAN",
    "valuesLabels": [
        "0901362561720"
    ],
    "values": [
        "0901362561720"
    ],
    "unit": null,
    "options": {
        "identifiesProduct": true,
        "isGTIN": true
    }
}
],
...
information

Note! In the future, we will remove the "ean" field in the offer and the "eans" array in the product. You will change the GTIN value (i.e. EAN, ISBN, ISSN) only using the parameter, so start working on their correct implementation in your application today.

26JUN
2020

POST /sale/product-offers - we have introduced new fields that you can add to your request

In response to your suggestions, we have introduced three new fields that you can provide in the POST /sale/product-offers structure:

  • name - offer title,
  • external.id - signature,
  • delivery.additionalInfo - additional delivery information.

You can find more information about this resource in our guide - how to list an offer assigned to a product with one request.

16JUN
2020

From August 1st, 2020 we will require 1% of offers assigned to a product in the categories Electronics, Beauty, Culture and Entertainment

Since 2019, we introduce elements of productization on the platform. We are grouping offers presenting the same products. As a result, it is easier for the customers to find the product that meets their needs. Offer assigned to a product will be displayed in new places, e.g. - on product pages.

We plan to productize the Allegro platform by mid-2021, therefore from August 1st, 2020 we will require 1% of offers assigned to a product in the following categories:

  • Electronics,
  • Beauty,
  • Culture and Entertainment.
information If a seller won’t meet this condition, it will be not available to list new offers in those categories, if current offers aren’t assigned to a product.

You can find more information about how to assign an offer to a product in our guide. Recently we have introduced new resource POST /sale/product-offers, which allows you to list an offer assigned to a product with one request:

  • if the product already exists in our database, all you need to do is provide EAN code (or product ID), price and quantity,
  • if the product is not in our database, you need to provide product data, price and quantity.
15JUN
2020

Sandbox - technical break

On June 17th, 2020 at 07:00 AM we will start a technical break for the test environment, which will last about 2 hours. We are sorry for the inconvenience.

10JUN
2020

We have introduced dependent parameters in the first category - Ear Clips

Dependent parameters are parameters:

  • for which a set of available values depends on the value of another parameter. A dependent parameter can be Model because available values will depend on value provided in Brand parameter, e.g. if you select Nokia as Brand, Model parameter values will be limited to Nokia models only,
  • which will be available depending on the choice of another parameter value, e.g. (theoretical example) if you want to list a bracelet and as a value for Material parameter you will select gold, there will be another parameter - Gold Hallmark.

According to our previous announcement, we have introduced dependent parameters in the category Ear Clips (123428). If you select the value of the main parameter (Material):

  • “Gold”, “Pink Gold” or “White Gold” - dependent parameter will be “Gold Hallmark”,
  • “Silver”, “Tibetan Silver” or “Silver-gilt” - dependent parameter will be “Silver Hallmark”,

You can find more information about dependent parameters in our news. We will no longer inform you about the next available dependent parameters on the Allegro API website.

10JUN
2020

List a charity offer on Allegro

On June 15th, 2020 you will be able to list charity offers on Allegro. Today we have introduced a new resource GET /charity/fundraising-campaigns which allows you to browse charity organizations.

Additionally, we have added a field “fundraisingCampaign” in offer model. If you want to list a charity offer, use POST /sale/offers and in the field “fundraisingCampaign” provide an ID of a chosen charity organization.

Sample request:

curl -X GET \
‘https://api.allegro.pl/charity/fundraising-campaigns?limit=10&phrase=Zbieramy’ \
-H 'Accept: application/vnd.allegro.public.v1+json' 

Sample response:

{
    "campaigns": [
        {
            "id": "4ed5aebc-a916-4144-b9e9-45f9408a9fe7",
            "name": "Zbieramy na karmę dla zwierząt ze schroniska",
            "organization": {
                "name": "Platforma Charytatywna"
            }
        }
    ]
} 
9JUN
2020

List of billing types

Today we have introduced a new resource GET /billing/billing-types, which allows you to retrieve a list of billing entries types. You can use it to identify the values in the "type.id" field, which are returned in a response to the resource GET /billing/billing-entries.

4JUN
2020

Net price and VAT rate in an offer

Today in the offer model we have introduced two new fields:

  • “netPrice” - net price, which we calculate automatically based on the VAT rate. You cannot define it yourself.
  • “tax” - VAT rate, which you can define, if the "VAT invoice" option is selected in the offer. At present you can use only the following VAT rates specified by Polish law (0%, 5%, 8%, 23%).

Offer model after change:

...
"sellingMode": {
    "format": "BUY_NOW",
    "price": {
      "amount": "2460",
      "currency": "PLN"
    },
    "netPrice": {
        "amount": "2000",
        "currency": "PLN"
      },
    "startingPrice": null,
    "minimalPrice": null
  },
 "tax": {
    "percentage": "23.00"
  },
...

Owing to the change, in the future we will show in the offers the VAT rate and net price of the product.

Note! Remember the transaction with the customer is settled on the gross price basis (including VAT). We provide a net price for informational purposes.

3JUN
2020

GET /sale/categories/{categoryId}/parameters - we add new fields and simplify listing an offer assigned to a product

Up to this date, when you listed an offer assigned to a product via POST /sale/product-offers and wanted to receive two different sets of offer and product parameters, you needed to use two separate resources. To simplify this process - in the response for GET /sale/categories/{categoryId}/parameters we have added new fields:

  • options.describesProduct - value:
    • true - this is a product parameter,
    • false - this is an offer parameter.
    Note! Offer parameters are related to individual offer, e.g. condition, expiration date, but not with a specific product feature.
  • requiredForProduct - true means you need to provide a value for this parameter when adding a new product proposal.

You can find more information on how to list an offer assigned to a product in a simple way in our guide.

Sample response:
{
     “id”: “10563”,
     “name”: “Brand”,
     “type”: “dictionary”,
     “required”: true,
     “requiredForProduct”: true
     “unit”: null,
     “options”: {
          “variantsAllowed”: false,
          “variantsEqual”: true,
          “ambiguousValueId”: “10563_40”,
          “dependsOnParameterId”: null
          “describesProduct”: true
     },
…
}
1JUN
2020

Sandbox - on June 8th, 2020 we will update the list of categories and parameters and remove all offers

On June 8th, 2020 we will update the list of categories and parameters on Sandbox. This will allows us to ensure consistency between test and production environments.

Note! Due to the update, we will remove all offers from Sandbox.

We plan to conduct similar updates once a quarter. We will inform you about them in advance.

29MAY
2020

GTIN parameter in offers and products

On June 29th, 2020 we will introduce the Global Trade Item Number (GTIN) parameter. In most categories, we will mark it as a basic parameter, which identifies the product in an offer. If you want to add or change GTIN parameter use the available parameters (depending on category):

  • EAN (parameter id=225693),
  • ISBN (parameter id=245669),
  • ISSN (parameter id=245673).

You can check parameters available in a given category by GET /sale/categories/{categoryId}/parameters.


GTIN in offers

In offers, GTIN parameter will override “ean” field, whose values will be automatically transferred to the new parameter. You can only fill in the EAN, ISBN, ISSN value in the GTIN parameter. To do so retrieve an offer via GET /sale/offers/{offerId} and then edit it by PUT /sale/offers/{offerId}. If you try to change the value of the “ean” field in the offer, you will receive an error message: “Ean field is read-only. Set this value in parameter with id: {id}.”

If you use in your integration the “ean” to recognize your offers (as so-called signature), switch to the “external.id” field, which is dedicated to the signature.

GTIN in products

The new GTIN parameter for products will function in parallel with the existing “eans” array. We will transfer the current values of “eans” to the new parameter. If you propose a product via POST /sale/product-proposals you can submit EAN, ISBN or ISSN value only in the GTIN parameter.

The GTIN parameter will receive the “isGTIN” flag in the “options” structure of the product parameters. Owing to it, when you will add an offer based on a product, you will recognize if a parameter has many values, you can only use one of them.

information Note! In the future, we will remove the “ean” field in the offer and the “eans” array in the product. You will change the GTIN value (i.e. EAN, ISBN, ISSN) only using the parameter, so start working on their correct implementation in your application today.

A week before the introduction we will make the category and product available on Sandbox with the new GTIN parameter. It will allow you to test the new feature. We will inform you about the details on our forum.

28MAY
2020

Order management resources available only in public version

On June 10th, 2020 resources responsible for order management:

will be available only in public version. We announced change previously on GitHub post #2220.

Please, make the necessary change to your software. To switch to the public version, you should change the headers value ‘accept’ and ‘content-type’ from:

‘application/vnd.allegro.beta.v1+json’ to ‘application/vnd.allegro.public.v1+json’.

27MAY
2020

POST /sale/product-offers - we added new field ‘status’

POST /sale/product-offers is a new resource, which allows you to list an offer assigned to a product with one request:

  • if the product already exists in our database, all you need to do is provide EAN code (or product ID), price and quantity,
  • if the product is not in our database, you need to provide product data, price and quantity.

You can find more information about this resource in our guide.


In the response structure, as part of product data, we added new field status in publication section, in which we inform based on data from the request:

  • we created new product proposal and assigned it to an offer (PROPOSED),
    {
        “product”:{
            “id”: “0cb89863-9bd0-4f92-x364-16ec3908201x”,  – submitted product ID
            “publication”: {
                “status”: “PROPOSED”
                },
              }
      …
    }
  • we identified the product in our database and assigned it to an offer (LISTED),
    {
        “product”:{
            “id”: “0cb89863-9xd0-4f92-x364-16ec3908201x”,  – product ID from our database
                “publication”: {
                    “status”: “LISTED”
          },
        }
      …
    }
  • we didn’t create a new product proposal and didn’t assign any product from our database to an offer (NOT_LISTED), but we listed an offer itself. This can happen e.g. when you try to create an offer and product in category, in which you can’t add new product proposal.
    {
        “product”:{
            “id”: null
            “publication”: {
                “status”: “NOT_LISTED”
          },
          },
        }
      …
    }
18MAY
2020

GET /me - we added email and tax ID in response

In response to your suggestions, we have introduced two new fields for GET /me:

  • email,
  • company.taxId.

Via GET /me you can retrieve user data, whose token is sent in the request.

Sample request:
curl -X GET
‘https://api.allegro.pl/me’
-H ‘Accept: application/vnd.allegro.public.v1+json’
Sample response:
{
    “id”: “12345678”,
    “login”: “example_login”,
    “firstName”: “Jan”,
    “lastName”: “Nowak”,
    “email”: “example_login@allegro.pl”,
    “company”: {
        “name”: “Allegro.pl”,
        “taxId”: “525-267-47-98”
    }
}
15MAY
2020

Productization - add your own value for parameter with ambiguous value, when you create a product

You can find information about ambiguous values and how to add your own value in selected categories in our previous announcement. For now, you can define your own value when you create a product via POST /sale/product-proposals.

You can retrieve ambiguous value identifier via GET /sale/categories/{categoryId}/parameters in the field ambiguousValueId. We wrote more info about this field in our news. You can find a current list of parameters, to which you can add your own value, on our sellers page.

When you create a product, provide the following structure in the parameters section to add your own value. If you provide an ambiguous value identifier in the valuesIds field, it is mandatory to fill in your own value in the values field.

 {
        “id”: “129033”,                               – parameter id
        “valuesIds”: [
         “129033_13”                                  – ambiguous value id
        ],
        “values”: [ “Missing brand name” ],           – value, which you want to provide.
                                                      Complete this field.
        “rangeValue”: null
  }
14MAY
2020

POST /sale/product-offers - simple way to list an offer assigned to a product

Process of listing an offer assigned to a product is a complex operation - you need to send multiple requests to different resources. We aim to make this process easier, we want to limit the number of operations required to list an offer assigned to a product.

Therefore, we have introduced a new, additional resource POST /sale/product-offers in beta version, which allows you to list an offer assigned to a product with one request:

  • if the product already exists in our database, all you need to do is provide EAN code (or product ID), price and quantity,
  • if the product is not in our database. you need to provide product data, price and quantity.

We will complete the rest of the data needed to list an offer with default values.

You can find more information about new resource in our guide.

In the future, when you use this resource, we will fill out your offers with the most recent data from our product catalog. If you don’t provide your own values, different from those in the product, you won’t need to copy or accept changes in your offers after we update the catalog. It will also allow us to automatically complete the parameters that we currently require when editing the offer.

7MAY
2020

Orders - a new field “revision”

Today we have introduced a new field “revision” for resources:

In this field we inform about order revision. Owing to it, you will be sure that you change the order fulfillment status (“fulfillment.status”) in the order, which exactly the same copy is in Allegro. The value of the “revision” field will change when the buyer makes a change that affects the order data (e.g. change of order status, payment, address, invoice, etc.).

28APR
2020

Authorization - we have increased tokens length

Tokens can now contain up to 2048 bytes. If you set a lower limit in your software, increase it then operations via API can be performed correctly. We apologize for the technical issues caused by this unannounced change.

27APR
2020

GET /payments/payment-id-mappings - we are turning off payments mapping

From May 8th, 2020, you won’t be able to use payments mapping via GET payments/payment-id-mappings. This resource allows you to retrieve payment.id by providing transactionId or vice versa. On January 13th, 2020, we disabled last WebAPI methods that used transactionId.

24APR
2020

Categories and parameters - add your own value for dictionary parameter with ambiguous value

Ambiguous value is for example “other” in the parameter “Brand”. You can retrieve its identifier via GET /sale/categories/{categoryId}/parameters in options section - field ‘ambiguousValueId’. We informed about this in an earlier announcement.

As of today, you can define custom value for parameters with ambiguous value by API in selected categories. Use this option when you listing or editing an offers and you can’t find an appropriate value. Thanks to this, we will collect suggestions of missing values and after verification we will add them to the list of values. In the future it will be necessary to provide custom value, if you choose an ambiguous parameter value.

You can find a current list of parameters, to which you can add your own value, on our sellers page. For now, custom parameter values can be added only by API.

To add a custom value, check the ambiguousValueId field in selected category via GET /sale/categories/{categoryId}/parameters:

{
    “parameters”: [
    {
        “id”: “129033”,
        “name”: “Brand”,
        “type”: “dictionary”,
        “required”:true,
        “unit”: null,
        “options”: {
            “variantsAllowed”: false,
            “variantsEqual”: false,
            “ambiguousValueId”: “129033_13”         – identifier for ambiguous value,
                                                    in this case it is “other”
        },
        …
    }

After that, when you creating draft or editing offer, provide following structure in the parameters section:


  {
        “id”: “129033”,                         – parameter id
        “valuesIds”: [
         “129033_13”                            – ambiguous value id
        ],
        “values”: [ “Missing brand name” ],     – value, which you want to provide.
                                                Complete this field.
        “rangeValue”: null
  }
    

In the future you will be able to define custom values for product proposals - we will inform you about the implementation in a separate news.

23APR
2020

GET /offers/listing - we will change maximum number of offers in a response

On May 6th, 2020 you will receive maximum 60 offers in response to GET /offers/listing. Please, make the necessary changes to your software now - in other case you will receive 60 offers by default.

16APR
2020

Orders cancellation by the buyer

On May 5, 2020 we will introduce to buyers option to cancel an order within 3 days after purchase. Buyer will be able to cancel an order if:

  • seller has a company account;
  • order fulfillment status (“fulfillment.status”) is different than PROCESSING, READY_FOR_SHIPMENT, SENT;
  • seller has not added tracking number to the order.

Therefore, to the following resources:

If the buyer cancelled an order, which is already paid, you can refund the payment via POST /payments/refunds. For cancelled orders you can create a sale commission refund application via POST /order/refund-claims.

You can find more information about orders cancellation on the for sellers page.

14APR
2020

Multi-variants - end of supporting beta version

According to our previous announcement we remind you that from April 27, 2020 we will stop supporting beta version of resources that allows you to combine offers into multi-variant offer.

In the public version we have introduced changes that will simplify working with multi-variant offers.

  • You can edit automatically combined offers. Up to this date, when you tried to create a new multi-variant offer in category where we automatically link offers, we returned an error.
  • Creating new and editing existing multi-variant offers is handled by two separated resources:
    • POST /sale/offer-variants - you can create a multi-variant offer. Previously you had to generate a UUID and provide it in the URL via the PUT method, now it will not be necessary - you will receive the ID in response;
    • PUT /sale/offer-variants/{setId} - you can edit multi-variant offer.

You will find more information about the new model of multi-variants resources in our guide.

The list of resources that we have released in public version:

7APR
2020

New resources for managing offer terms

We have introduced new resources, which allows you to manage:

You can find more information in our guide.

6APR
2020

New universal required parameters - update

According to the announcement on April 6, 2020 in most categories Allegro we planned to introduce required parameters for the Manufacturer’s code, Brand and Model parameters. However, due to the current situation, which affects both consumers and entrepreneurs, we decided that for most categories we will move the deadline for marking parameters as required from April 6 to May 6.

More information you can find on the for sellers page.

6APR
2020

Category and parameters in English

As of today, you can specify the language in the header to get a response in English for the following resources:

To retrieve English version just add header:

-H ‘Accept-Language: en-US’

You will find more information in our guide - Listing offers.

2APR
2020

New fields for dependent parameters

Dependent parameters are parameters:

  • for which a set of available values depends on the value of the another parameter. Dependent parameter can be Model, because available values will depend on value provided in Brand parameter, e.g. if you select Nokia as Brand, Model parameter values will be limited to Nokia models only,
  • which will be available depending on the choice of another parameter value, e.g. (theoretical example) if you want to list a bracelet and as a value for Material parameter you will select gold, there will be another parameter - Millesimal fineness.

Currently, we focus on dependency between selected parameter and set of available values for dependent parameter.

We plan to introduce dependent parameters gradually in selected categories, the first will appear in Clips category (123428). We will inform you about next categories and parameters on the sellers page. The parameters may be required, you can check it in the ‘required’ field in the response for GET /sale/categories/{categoryId}/parameters.
Owing to this solution we will limit the number of available categories in the future, which will simplify navigation, e.g. seller will list “Nokia 8” already in the parent category “Smartphones and mobilephones” - specifying Brand and Model accordingly.

Therefore, we have introduced new fields in response to GET /sale/categories/{categoryId}/parameters:

  • dependsOnParameterId - in options section. Returned id for “A” parameter, indicates can be provided in “B” parameter, e.g. for the Model parameter (parameter “B”) we will return the id of the parameter Brand (parameter “A”) Parameter id in this field is returned only for dictionary type parameters , in other cases we will return null value,
  • dependsOnValueIds - in dictionary section. We return the identifier of the value of the “A” parameter with which the value of the “B” depends on.

When we introduce first dependent parameters, new fields will help you check whether you are trying to list offer with valid combination of parameter values, e.g. whether Nokia is producing the model provided in the request.

Initially, we won’t return errors, if you don’t bind correctly dependent parameters. If parameter will be required, you will need to provide value, but we will ignore the dependency between the parameters. We will inform you in advance, when more strict validation will be implemented.

Below you can find example of a structure that explains the dependent parameters functionality:


  {
    “id”: “1254”,
    “name”: “Model”,
    “type”: “dictionary”,
    “required”: false,
    “unit”: null,
    “options”: {
      “variantsAllowed”: true,
      “variantsEqual”: false,
      “ambiguousValueId”: “1254_17231”,
      “dependsOnParameterId”: “202689”          – values in the dictionary depend on
                                                the parameter referenced by this field.
                                                In this case it means that values
                                                for Model parameter depends on
                                                Brand parameter value.
      },
    “dictionary”: [
      {
        “id”: “1254_1”,
        “value”: “Galaxy S20”,
        “dependsOnValueIds”: [
          “202689_213101”                       – the ID of the dictionary value
                                                from parameter that this parameter
                                                value depends on.
                                                In this case it indicates Samsung brand.
          ]
       },
       {
         “id”: “1254_2”,
         “value”: “Galaxy S20+”,
         “dependsOnValueIds”: [
           “202689_213101”
          ]
       },
       {…},
       {
         “id”: “1254_3”,
         “value”: “520 Lumia”,
         “dependsOnValueIds”: [
           “202689_213102”                      – in this case it indicates Nokia brand.
          ]
       },
       {…},
       {
       “id”: “1254_4”,
       “value”: “Mi Note 10”,
       “dependsOnValueIds”: [
         “202689_213103”                        – in this case it indicates Xiaomi brand.
         ]
       },
      {
        “id”: “1254_5”,
        “value”: “Mi Note 10 Pro”,
        “dependsOnValueIds”: [
          “202689_213103”
          ]
      }
     ]
   }
                
24MAR
2020

Sale commission refunds in REST API

We have introduced new resources, which allows you to manage commision refunds:

As a seller you can apply for a sale commission refund, when you sold an item, but the transaction did not take place. You can find more information about sale commission refunds in our article.

information Via REST API you can create a sale commission refund application for commissions collected in the last 45 days.

You will find more information in our guide..

20MAR
2020

New delivery methods - UPS Odbiór w Punkcie and UPS Odbiór w Punkcie pobranie

On April 2, 2020 we will introduce new delivery methods. You can get identifiers in the resource GET/sale/delivery-methods:

  • UPS Odbiór w Punkcie - id c576dc1d-4046-4b53-94de-47fc5b6913d4.
  • UPS Odbiór w Punkcie pobranie - id e6d9d675-c8cb-4c0f-bcd2-febebfbac3d5.

You can find more information about this change here.

19MAR
2020

Multi-variants resources released in public version

We have completed the test period for resources, which allows you to combine offers into multi-variant offer. We will support the beta version until 27.04.2020. During this period, you can gradually switch to the public version.

In the public version we have introduced changes that will simplify working with multi-variant offers.

  • You can edit automatically combined offers. Up to this date, when you tried to create a new multi-variant offer in category where we automatically link offers, we returned an error.
  • Creating new and editing existing multi-variant offers is handled by two separated resources::
    • POST /sale/offer-variants - you can create a multi-variant offer. Previously you had to generate a UUID and provide it in the URL via the PUT method, now it will not be necessary - you will receive the ID in response;
    • PUT /sale/offer-variants/{setId} - you can edit multi-variant offer.

You will find more information about the new model of multi-variants resources in our guide.

The list of resources that we have released in public version:

19MAR
2020

New universal required parameters

According to the announcement on April 6, 2020, in most Allegro categories we will introduce required parameters for the Manufacturer’s code, Brand and Model parameters. We are now publishing the file - it contains a list of all parameters (indicating the categories in which they occur), which we will mark as required on April 6. By using this data, sellers will be able to complete their values before implementing the obligation in the service.

18MAR
2020

Changes in shipping method id of Kurier DPD and Kurier DPD pobranie.

On March 19, 2020 we will change the shipping method id for:

  • Kurier DPD - new shipping method id will be c3066682-97a3-42fe-9eb5-9bb2978cf293.
  • Kurier DPD pobranie - new shipping method id will be 259b5c7a-9056-4c74-80ec-9bb2978cf293.

Under the previous shipping method ids of Kurier DPD and Kurier DPD pobranie we will introduce new shipping methods:

  • Allegro Kurier DPD - shipping method id c3066682-97a3-42fe-9eb5-3beeccab840c.
  • Allegro Kurier DPD pobranie - shipping method id 259b5c7a-9056-4c74-80ec-8bdc50cb0413.

Note! If in your shipping price list you are using:

  • Kurier DPD - we will change this method to Allegro Kurier DPD.
  • Kurier DPD pobranie - we will change this method to Allegro Kurier DPD pobranie.

You can find more information about this change here.

18MAR
2020

Prohibition of selling and shipping abroad certain hygiene products and medical components

As of today during activation of an offer with the words (COVID-19, SARS-CoV-2, coronavirus, etc.) in the field “name” we will return an error message:

{
  “userMessage”: “Zabronione jest odwoływanie się w tytule oferty do koronawirusa (COVID-19,
  SARS-CoV-2, koronawirus, itp). W obecnej sytuacji zagrożenia epidemiologicznego i powszechnego lęku
  przed zarażeniem wirusem, może to w istotny sposób zaburzać percepcję konsumentów w trakcie
  dokonywania wyboru oferty oraz prowadzić do dezinformacji.”
}

More information about prohibition you will find on for sellers page.

18MAR
2020

Categories and parameters - new field ‘ambiguousValueId’ for parameters with ambiguous value

We have introduced a new field ‘ambiguousValueId’ in options section in response to GET /sale/categories/{categoryId}/parameters. In this field we inform about identifier for ambiguous value for parameter. Ambiguous value can be value such as ”other”, “different pattern”, etc. e.g. “other” in the parameter “Brand”. In this case the response will look like below:

{
  “parameters”: [
    {
        “id”: “2929”,
        “name”: “Marka”,
        “type”: “dictionary”,
        “required”:true,
        “unit”: null,
        “options”: {
            “variantsAllowed”: false,
            “variantsEqual”: false,
            “ambiguousValueId”: “25929_41”          – identifier for ambiguous value,
                                                    in this case it is “inna” (other)
        },
        “dictionary”: [
          {“id”: “25929_416381”,  “value”: “2skin”},
          {“id”: “25929_31”, “value”: “4F”},
          …
          {“id”: “25929_41”, “value”: “inna”}
        ],
        “restrictions”: {“multipleChoices”: false}
    }
  ]
}

We return value in the new field only for dictionary parameters, for which you can choose an ambiguous value. In other cases you will receive null.

Note! In the future you will be able to define new values for ambiguous values. We will inform you about the details in a separate news.

17MAR
2020

New resource to retrieve available delivery company ID

We have introduced a new resource GET /order/carriers, which allows you to retrieve available delivery company IDs - which are necessary to add a tracking number to an item in order.

You will find more details in our tutorial.

Sample request:
curl -X GET
https://api.allegro.pl/order/carriers
-H ‘Authorization: Bearer {token}’ /
-H ‘Accept: application/vnd.allegro.public.v1+json’
Sample response:
{
    “carriers”: [
        {
            “id”: “UPS”,            – delivery company ID
            “name”: “UPS”           – delivery company name
        },
        {
            “id”: “INPOST”,
            “name”: “InPost”
        },
…
        {
            “id”: “OTHER”
        }
    ]
}
13MAR
2020

Sandbox - technical break

On March 18, 2020 at 7:00 PM we will start a technical break for the Sandbox environment. It will take about 5 hours. Sandbox will be available again from midnight March 19, 2020.

We are sorry for the inconvenience.

9MAR
2020

New resource to retrieve product rating

We have introduced a new resource GET /sale/offers/{offerId}/rating, which allows you to retrieve product ratings assigned to your offers.

Sample request:
curl -X GET
            https://api.allegro.pl/sale/offers/{offerId}/rating
            -H ‘Authorization: Bearer {token}’ /
            -H ‘Accept: application/vnd.allegro.public.v1+json’
Sample response:
{
            “averageScore”: “3.00”,         – average product rating
            “scoreDistribution”: [          – list score distribution with count
            {
              “name”: “5”,                  – widentifier of score
              “count”: 1                    – count of score
            },
            {
              “name”: “4”,
              “count”: 0
            },
            {
              “name”: “3”,
              “count”: 1
            },
            {
              “name”: “2”,
              “count”: 0
            },
            {
              “name”: “1”,
              “count”: 1
            }
            ],
            “totalResponses”: 3,            – number of total responses
            “sizeFeedback”: [               – list of size feedback
            {
              “name”: “BIGGER”,             – identifier of size feedback
              “count”: 0                    – count of sizeFeedback responses
            },
            {
              “name”: “FIT”,
              “count”: 1
            },
            {
              “name”: “SMALLER”,
              “count”: 2
            }
            ]
            }
4MAR
2020

Event journal concerning changes in seller offers in public version

We have concluded the test period for resource, which returns an event journal concerning changes in offers listed by authorized seller that occurred within the last 24 hours. We will support the beta version until 30.03.2020. To switch to the public version, you should change the header value ‘accept’ from:

‘application/vnd.allegro.beta.v1+json’ to ‘application/vnd.allegro.public.v1+json’.

3MAR
2020

What do you think about Allegro API?

Complete the survey about our API and Allegro REST API website. Your answers will allow us to understand your needs and indicate the direction of further development.

The survey will take you only a few minutes. Please find the link to the survey - click here.

2MAR
2020

Co-financed courier delivery in Allegro Smart!

On March 1, 2020 for orders in which the delivery is carried out as part of Allegro Smart! with the courier in the field “cost.amount” we will return the cost of delivery co-financed by Allegro.

More information about co-financed delivery you will find on for sellers page.

6FEB
2020

Orders - new field shipmentSummary.lineItemsSent

We have introduced new field shipmentSummary.lineItemsSent in:

In the fulfillment section, in addition to the order fulfillment status, you will find information whether ordered items have a tracking number. Available values specify assigned tracking numbers to:

information Note! We return the value in the field shipmentSummary.lineItemsSent for orders created after 15.01.2020.

To filter orders by assigned tracking numbers - provide the fulfillment.shipmentSummary.lineItemsSent parameter in your request with the chosen value, e.g.

GET /order/checkout-forms?fulfillment.shipmentSummary.lineItemsSent=NONE
You can provide more than one value, e.g.
GET /order/checkout-forms?fulfillment.shipmentSummary.lineItemsSent=ALL&fulfillment.shipmentSummary.lineItemsSent=SOME
We recognize multiple filters as connected with OR operator - in response you will receive orders, which have at least one status given in the query.

4FEB
2020

Update to March 31 software on servers and connect to Allegro with TLS 1.2 or newer

If you use on the server and connect to Allegro only with TLS 1.1.

TLS (ang. Transport Layer Security) ensures confidentiality and integrity of data transmission. Version 1.1 was created in 2006 and does not meet today’s security standards.

Update software on servers and connect to Allegro with TLS 1.2 or newer. Instructions how to do this you can find here.

Important! If you don’t update software on servers after March 31 you will not be able to connect to the Allegro API.

31JAN
2020

WebAPI available by the end of the year

We are extending the availability of WebAPI to the end of the year. For this reason, we have updated our timetable.

In our timetable we have updated information about the doGetSiteJournal method - in April we will disable the value 0 for input parameter infoType.

  • Via this method you will be able only to retrieve events concerning all offers. The value infoType=1 will be available until this method is no longer available.
  • If you want to get events, which concern logged user - use offer journal - GET /sale/offer-events.
27JAN
2020

Order fulfillment status change available via REST API

According to the previous announcement, we have introduced resource for changing order fulfillment status, visible in the fulfillment.status field:

Sample request:
curl -X PUT
‘https://api.allegro.pl/order/checkout-forms/{checkoutFormId}/fulfillment'
-H ‘Authorization: Bearer {token}’
-H ‘Accept: application/vnd.allegro.public.v1+json’
-H ‘Content-Type: application/vnd.allegro.public.v1+json’
-d ‘{
            “status”: “SENT”                – sample values: NEW,
                                            PROCESSING, etc.
                                            Full list can be found in
                                            our documentation
}’

You will find more details in our guide - how to process orders.

If the seller has enabled subscription, in the Orders tab he can set automatic:
  • change the status to “SENT”, when a tracking number(waybill) is added,
  • sending a message to the buyer after the status is changed.
16JAN
2020

Restrictions in return address (redirect_uri)

We will introduce the following changes to the return addresses:

  • you can only use domain addresses, public IP-addresses and localhost,
  • you cannot use private IP-addresses:
    • 10.0.0.0 - 10.255.255.255
    • 172.16.0.0 - 172.31.255.255
    • 192.168.0.0 - 192.168.255.255
  • as of 31.03.2020 you will not be able to:
    • use addresses 127.x.x.x. (“loopback” address - 127.0.0.0/8).

To prepare for change, go to “Manage Applications” (“Zarządzanie aplikacjami Allegro”) and change Return address (“Adres przekierowań”), that are no longer supported. Correct return address:

  • must be the URI address,
  • must contain a HTTP(S) protocol,
  • cannot contain URI fragments,
  • cannot contain relative paths,
  • cannot use IP address.

You can use multiple redirect_uri addresses (add them in the new lines).

If you do not make the changes, your users will not be able to login to the application.

16JAN
2020

New statuses of order fulfillment

We have introduced new field fulfillment.status in: in which you will find information about current fulfillment status, according to the information set by the seller in the Orders.

The currently available values for the fulfillment.status are:
  • NEW - new order,
  • PROCESSING - order in progress,
  • READY_FOR_SHIPMENT - order to sent,
  • SENT - order sent,
  • CANCELLED - order cancelled.
List of statuses can be found in our documentation.
information Note! We return the value in the field fulfillment.status for orders created after 15.01.2020 or in a situation where the seller has changed status after this date.
You can filter your orders by fulfillment status - provide the fulfillment.status field with value as a parameter in your request, e.g.

GET /order/checkout-forms?fulfillment.status=SENT - will return shipped orders.

Order fulfillment status seller can change in Orders tab. In the near future we will provide this functionality via REST API.

Due to this change, we have introduced a new event type in GET /order/events - FULFILLMENT_STATUS_CHANGED. Event will occurs, if the status of the order fulfillment has been changed. You can pass it in your request as a value of type parameter, which will limit the results in the response.

You will find more information about order management in our guide.
13JAN
2020

Orders management only by REST API resources

According to the previous announcement we removed WebAPI methods responsible for orders management. Thus, order management in WebAPI is no longer possible.

Switch to REST API resources and use it to process orders. Detailed information you can find in our tutorial. In REST API we have provided mapping for selected WebAPI values, which allows you to maintain continuity in order processing, more information you will find here.

13JAN
2020

New resources for management of user rating

We have introduced new resources for answering and requesting removal of user rating:

You can find more information about user rating in Allegro Help.

07JAN
2020

User authorization - PKCE-enhanced Authorization Code Flow

We have introduced PKCE (Proof Key for Code Exchange) mechanism, which you can use in the user authorization process. Owing to the PKCE, you can protect your application against the use of authorization_code by malicious software.

To use it, generate code_verifier by yourself - it should be a random string containing between 43 and 128 characters, which you will use in access token request. Then in the authorization process, add two parameters:

  • code_challenge - code for the PKCE mechanism, its value depends on the encryption method, which you specify in the code_challenge_method,
  • code_challenge_method - code_challenge encryption method. It can take one of two values:
    • S256 - means that the code_challenge is encrypted (with SHA-256 algorithm) code_verifier. Use this value - it provides better safety due to the encryption used,
    • plain - means that the code_challenge value will be equal to the code_verifier value.

Below you can find examples of HTTP requests for code_verifier = KnAijeNvdSeloYlVcOh3HRmgZX57wDeVHiwRFQKO2F9DdBI.

For code_challenge_method=S256:

https://allegro.pl/auth/oauth/authorize?response_type=code&client_id=a21...6be&redirect_uri=http://exemplary.redirect.uri&code_challenge_method=S256&code_challenge=a69se03ZmsPhTLYQKHpGUH7m5waf-U8D-5pTwFRgLI4
For code_challenge_method=plain:
https://allegro.pl/auth/oauth/authorize?response_type=code&client_id=a21...6be&redirect_uri=http://exemplary.redirect.uri&code_challenge_method=plain&code_challenge=KnAijeNvdSeloYlVcOh3HRmgZX57wDeVHiwRFQKO2F9DdBI
Then, when you’re requesting for access token, as code_verifier provide the same value as you specified earlier:
curl -X POST -H ‘Authorization: Basic YTI…Hg=’ ‘https://allegro.pl/auth/oauth/token?grant_type=authorization_code&code=pOPEy9Tq94aEss540azzC7xL6nCJDWto&redirect_uri=http://exemplary.redirect.uri&code_verifier=KnAijeNvdSeloYlVcOh3HRmgZX57wDeVHiwRFQKO2F9DdBI'
You will find more information in our guide - user authorization.

09DEC
2019

Orders - new carriers

From today with POST/order/checkout-forms/{id}/shipments, you can add new carriers in field carrier.id:

  • YUN_EXPRESS
  • CHINA_POST

You will find more information about orders in our tutorial.

05DEC
2019

New limit for drafts

As of January 13, 2020 we will introduce the limit of drafts (offers with status “INACTIVE”). On one account you will be able to create up to 20,000 drafts.

When you exceed the limit, you will not be able to add new drafts and receive a message - “You cannot create new drafts - your account has exceeded the maximum number {maxInactiveOffers} of drafts.”

To avoid this situation:

You will find more information about creating drafts in our tutorial and documentation.

29NOV
2019

GET /sale/offers - new filtering option

Today in GET /sale/offers we have introduced new option for filtering offers by delivery.shippingRates.id.empty - you can check offers without shipping rates ID.

A sample request of offers without shipping rates ID:

GET sale/offers?delivery.shippingRates.id.empty=true

27NOV
2019

GET /order/checkout-forms - new filtering and sorting options

Today in GET /order/checkout-forms we have introduced new options for filtering orders by:

  • delivery.method.id - delivery method id,
  • buyer.login - buyer login,
  • updatedAt.lte - upper bound of checkout form last modification date,
  • updatedAt.gte - lower bound of checkout form last modification date

and sorting orders by:

  • lineItems.boughtAt - increasing latest line item bought date,
  • -lineItems.boughtAt - descending latest line item bought date,
  • updatedAt - increasing checkout form last modification date,
  • -updatedAt - descending checkout form last modification date.
information Note! New filtering and sorting options are available for orders created after 06.11.2019.

A sample request of orders sorted by descending checkout form last modification date:

GET /order/checkout-forms?sort=-updatedAt

21NOV
2019

GET /sale/offer-events - new types of events

In response to your suggestions, we have introduced two new types of events for GET /sale/offer-events: GET /sale/offer-events:

  • bid was placed on the offer (“type”: “OFFER_BID_PLACED”),
  • bid for offer was canceled (“type”: “OFFER_BID_CANCELED”).

GET /sale/offer-events is an event journal concerning changes in offers listed by authorized seller that occurred within the last 24 hours.

You can find more information about it in our guide.

19NOV
2019

Constraints on purchases for campaigns, special programs and Allegro badges

Today in response to resources:

we have introduced a new, optional object “purchaseConstraints”. With it, you can limit the number of items available to a single buyer in a campaign.

You will find more information about constraints on purchases in our tutorial.

13NOV
2019

Productization - new field unit

We have introduced new field ‘unit’ in the parameters section in response for the following resources:

In this field we inform about unit for given parameter value. If a value is not associated with any unit, we return null.

30OCT
2019

What do you think about Allegro API?

Complete the survey about our API. Your answers will allow us to understand your needs and establish priorities in addressing them.

The survey will take you only a few minutes. Please find the link to the survey - click here.

21OCT
2019

Billing operations and balance

We have introduced new resource GET /billing/billing-entries, which allows you to retrieve list of billing operations and balance for the authorized user.

By default, you will retrieve list of 100 billing operations, where the first result is the newest. You can use sorting and filtering to narrow down your search results and get the data you are interested in. More information you will find in our tutorial.

Sample request, for which you will retrieve information about the operations from 10.10.2019

curl -X GET
https://api.allegro.pl/billing/billing-entries?occurredAt.gte=2019-10-10T00:00:00.000Z&occurredAt.lte=2019-10-10T23:59:59.000Z
-H ‘Authorization: Bearer {token}’ /
-H ‘Accept: application/vnd.allegro.public.v1+json’ /
-H ‘Content-Type: application/vnd.allegro.public.v1+json’

Sample response

{
    “billingEntries”: [
        {
            “id”: “da74ef80-f97a-4b04-a748-4c129cfb94b8”,   – billing entry ID
            “occurredAt”: “2019-10-10T10:27:17.412Z”,       – date of billing entry
            “type”: {
                “id”: “LIS”,                                – three-letter code of the billing type
                “name”: “Wystawienie przedmiotu”            – name of the billing type
            “offer”: {
                “id”: “6206586563”,                         – offer ID
                “name”: “oferta testowa”                    – offer title
            },
            “value”: {
                “amount”: “-1.00”,
            “currency”: “PLN”
            },
            “tax”: {
                “percentage”: “0”                           – tax rate
                 “annotation”: “EXEMPT”                     – additional field - returned if the
                                                            billing entry is exempt from tax
                                                            (“EXEMPT”)  or tax is not applicable
                                                            (“NOT_APPLICABLE”)
            },
            “balance”: {
                “amount”: “-737.57”,                        – balance after the operation
                “currency”: “PLN”
            }
        }
    ]
}

You can find more details about the new resource in the documentation.

18OCT
2019

Split payment - a new type of payment

On November 1, 2019 in response to resources:

we will release a new value in a field “payment.type”: “SPLIT_PAYMENT”.

We are introducing these changes due to release of split payment on November 1, 2019. The payment for the invoice is divided into the net amount and the amount of VAT, transferred to a separate VAT account. Act of August 9, 2019 about change in Act of Value Added Tax and other acts introduces from November 1, 2019 an obligation to use split payment for specific transactions.

You will find more information about split payment introduced on November 1, 2019 on Allegro news page and Allegro Help.

16OCT
2019

List an auction for 24 hours

We have introduced new value for duration of auctions, now you can list it for 24 hours. When publishing the auction, in the publication.duration field, provide “PT24H” or “P1D” value. Before, you could only list an auction for 3, 5, 7 or 10 days.

9OCT
2019

Orders - new field calculatedNumberOfPackages in the delivery section

We have introduced new field ‘calculatedNumberOfPackages’ in the following resources:

In the delivery section, you will receive information about the total number of all packages in the order. Number is calculated based on:

Thanks to this information, you will know how many parcels in this order will be dispatched without any cost, when the Allegro Smart! option is enabled. We return a new field for orders created after 07.10.2019.

8OCT
2019

Productization - resources released in public version

We have concluded the test period for resources, which allows you as a seller to assign offer to a product or create a product. We will support the beta version until 22.10.2019. To switch to the public version, you should change the headers value ‘accept’ from:

‘application/vnd.allegro.beta.v1+json’ to ‘application/vnd.allegro.public.v1+json’

You will find more information about assigning offer to a product or create a product in our tutorial.

8OCT
2019

The end of WebAPI support - for bidding and blacklist management

As was announced earlier, we remind you that on October 14, 2019, we will remove the WebAPI methods responsible for:

Switch to REST API resources, which allow you to make a bid and manage a blacklist.

7OCT
2019

Resources for adding tracking number to order released in public version

We have concluded the test period for resources, which allows you as a seller to add tracking number to given order line item. We will support the beta version until 21.10.2019. To switch to the public version, you should change the headers value ‘accept’ from:

‘application/vnd.allegro.beta.v1+json’ to: ‘application/vnd.allegro.public.v1+json’

information Note! In public version we don’t support automatic carrier change “POCZTEX” to “POCZTA_POLSKA”. Make sure you provide the correct value in carrierId field.

On January 13, 2019 we will remove the WebAPI method doAddPackageInfoToPostBuyForm, which is marked as deprecated.

You will find more information about adding tracking number to given order line item via REST API inhttps://developer.allegro.pl/en/multi_variant_offers/.

3OCT
2019

Offer drafts - limiting storage time

As of today, we storage offer draft for 60 days. After that offer draft will be deleted. If you edit something in offer draft, we will extend its validity by 60 days.

26SEP
2019

New resource for retrieving user data

Today we have released new resource, which allows you to retrieve user data, whose token is sent in the request:

Sample request

curl -X GET
https://api.allegro.pl/me
-H ‘Accept: application/vnd.allegro.public.v1+json’
-H ‘Content-Type: application/vnd.allegro.public.v1+json’ 

Sample response

{
    “id”: “12345678”,
    “login”: “example_login”,
    “firstName”: “Jan”,
    “lastName”: “Nowak”,
    “company”: {
        “name”: “Allegro.pl”
    }
}
19SEP
2019

Productization - Assign product to an offer in categories with vehicle parts

We have released new features, which allow you to assign product to an offer in Braking system category:

  1. In categories with vehicle parts in product details received in response for GET /sale/products/{product.id} you will find:
    • offerRequirements - which provides you with conditions that offers must meet to be assigned with the product, i.e. Condition parameter must be set to New.
    • compatibilityList - Compatibility list id - which you must include in the offer assigned to the product. In addition, we return a text representation of the content of this section.
    • tecdocSpecification - TecDoc specification id - which you must include in the offer assigned to the product. In addition, we return a text representation of the content of this section.
  2. In offer details send with POST /sale/offers and PUT /sale/offers:
    • In compatibilityList provide Compatibility list id received for selected product and “type”: “PRODUCT_BASED”.
    • New object is available - tecdocSpecification - where you should provide TecDoc specification id received for selected product.
  3. In offer details received in response to GET /sale/offers you will receive a text representation of the content of Compatibility list and TecDoc specification. We will not return an error if the text representation is provided in requests for POST /sale/offers and PUT /sale/offers - the text representation is ignored.

You can find more details about assigning products to offers in our tutorial.

18SEP
2019

GET /offers/listing - change in search filters

We have implemented a patch in GET /offers/listing resource, that eliminates previous issues with filtering offers in categories, where parameters values have been merged.

We have changed some identifiers of values for filters, you will find them in “filters” object, that you will retrieve in response for GET /offers/listing.

16SEP
2019

As of October 2nd delivery time will not be included in transaction ratings

According to the announced changes in the Allegro Terms and Conditions, on October 2nd we will remove “delivery time” from areas which customer can rate after transaction. This means that as of October 2nd, sellers will not receive ratings for delivery time.

In effect in ratings created as of October 2nd in responses for the following resources:

in rates.delivery we will return null. For ratings created before October 2nd you will receive ratings for delivery time properly.

Additionally in the GET/sale/user-ratings documentation all fields contained in the rates object are marked as not required.

13SEP
2019

Orders management resources released in public version

We have concluded the test period for resources, which allows you as a seller to manage orders. We will support the beta version until 27.09.2019. To switch to the public version, you should change the headers value ‘accept’ from:

‘application/vnd.allegro.beta.v1+json’ to ‘application/vnd.allegro.public.v1+json’.

On January 13, 2019 we will remove the following methods, which today we have marked as deprecated:

You will find more information about processing orders in our tutorial.

12SEP
2019

Delivery settings available in REST API

Today we have introduced new resources in REST API, which allows you to manage the delivery settings:

Sample request

curl -X GET
https://api.allegro.pl/delivery-settings
-H ‘Authorization: Bearer {token}’
-H ‘Accept: application/vnd.allegro.public.v1+json’
-H ‘Content-Type: application/vnd.allegro.public.v1+json’ 

Sample response

{
    “freeDelivery”: {
        “amount”: 4.04,             – minimum total order amount
        “currency”: “PLN”           required for free delivery
    },
    “joinPolicy”: {
        “strategy”: “MAX”           – policy of calculating delivery costs
    },
    “customCost”: {
        “allowed”: true             – whether the custom delivery cost
                                    should be available
   },
   “updatedAt”: “2019-08-21T10:13:40.036Z”
}

You will find more information about new resources in our documentation.

4SEP
2019

We have updated the Terms and Conditions of Allegro REST API

According to the previous announcement, today we have introduced two changes in the Terms and Conditions of REST API Allegro:

  • in section 4.3. about the obligations of REST API Software Developers, we added specific name of the software - REST API,
  • we added section 7.7. with information about the English version of Terms and Conditions.

We have also published English version of Terms and Conditions.
Introduced changes are minor and do not affect users of Allegro REST API.

3SEP
2019

Productization - we require EAN value when adding a product in selected categories and we add new categories, in which you can assign offer to a product

We have added a new field productEANRequired in resources:

Value true for this field means that in selected category, you must provide at least one EAN value, when creating a new product. For start we have introduced EAN as a required value in one category - SD memory cards.

In addition, as of today you can assign offer to a product in further selected subcategories belonging to the following categories:

  • Child
    • Accessories for mom and baby
    • Toys
    • Health and hygiene
  • Electronics
    • Photography
    • Computers
    • Consoles and automatons
    • Electronics and household appliances
    • Telephones and accessories
  • Culture and entertainment
    • Games
    • Music
  • Motoring
    • Car accessories
    • Workshop tools and equipment
  • Sport and tourism
    • Running
    • Bicycles and accessories
    • Gym and fitness
    • Skating, slackline
    • Team Sports
    • Tourism
    • Fishing
  • Supermarket
    • Article for animals
    • Maintenance of cleanliness
  • Beauty
    • Manicures and pedicures
    • Perfumes and water
    • Care
  • Health
    • Erotica
    • Oral hygiene
    • Natural medicine
    • Specialist medical equipment
    • Rehabilitation and orthopedic equipment
    • Medical equipment
    • Hospital and clinic equipment
    • Intimate health
2SEP
2019

GET sale/offer-events - new event type

Today we have introduced in the response to GET sale/offer-events a new event type - “OFFER_ARCHIVED” for offer which is no longer available on list of the offers and is archived.

You will find more information about event journal in our tutorial.

29AUG
2019

We merge parameters and their values

We have started the process of merging parameters and their values in selected categories:

  • merging parameters - in case, when category contains parameters with different id, but with identical or similar meaning, then we will merge these parameters and combine their values. For example - in Beauty category we will merge Manufacturer parameter with Brand parameter. As a result, we will expand Brand parameter by all values of the Manufacturer parameter, and Manufacturer parameter will be deleted.
  • combining parameter values - e.g. (theoretical example) in color parameter we combine values: black and shades of black. As a result, we have only one value - black.

At present there are many parameters and their values assigned to lower level category, that have similar or identical meaning. By merging parameters, we will be able to move them to higher level category and use these parameters as filters. Owing to this approach buyers will be able to find interesting offer easier.

For example - we unified parameter id for Diameter in all subcategories belonging to the Tires category. Before change, parameter identifiers were different in each of the following subcategories:

  • For passenger cars,
  • For 4x4/SUV cars,
  • For vans,
  • For trucks,
  • For motorcycles and scooters,
  • For agricultural machines,
  • For construction machinery,
  • For quads.

Parameter identifiers were merged and unified with the subcategory For passenger cars. This means for Diameter common parameter identifier is now 127088.

The change does not affect the Tires for passenger cars subcategory (because we merged other parameters to this category). As a result, the parameter have one identifier and contain all values, that were previously available in each of the categories.

information Remember that parameters are updated on regular basis, therefore to retrieve the latest information about them, useGET /sale/categories/{categoryId}/parameters.

How the change will affect offers:

  • We will automatically update parameters in existing offers.
  • When you list a new offer using an old parameter and value - we will automatically update the parameter id and values. We will support automatic update for one year after the parameter was changed.
27AUG
2019

We are going to remove WebAPI methods for relisting offer

On September 30th, 2019 we will remove the following WebAPI methods for listing offer:

If you want to list similar offer via REST API, retrieve it by calling GET /sale/offers/{offerId}, and transfer the whole structure with POST /sale/offers apart from:

  • offer ID (id),
  • last offer validation (validatedAt),
  • offer creation date (createdAt),
  • last offer update (updatedAt).

Remember, you must be authenticated and authorized as a seller who listed the previous offer. Therefore, you will create a new draft offer based on data of the retrieved offer.
Once the offer is complete and properly validated, call PUT on PUT /sale/offer-publication-commands/{commandId} to publish the offer on the site.

You can find more details in our guide.

23AUG
2019

GET sale/offer-events - change in presentation of event time

On August 30, 2019 in response to resource:

we will delete redundant field “publication.endedAt” returned in event “OFFER_ENDED”. At the same time in a field “occuredAt” we will return for every event type its time of occurrence. We already encourage you to read data from this field.

More information about event journal you will find in our tutorial.

21AUG
2019

We are updating the Terms and Conditions of REST API Allegro

On September 4, 2019, we will provide two changes in the Terms and Conditions of REST API Allegro:

  • in section 4.3. about the obligations of REST API Software Developers, we will add specific name of the software - REST API;
  • we will add section 7.7. with information about the English version of Terms and Conditions.

On this day we will also publish English version of Terms and Conditions.
These are minor changes and they do not affect those using the REST API.

19AUG
2019

Blacklist management resources released in public version

We have completed the test period for resources, which allows you as a seller to manage your blacklist of buyers. We will support the beta version until 02.09.2019. To switch to the public version, you should change the headers value ‘accept’ from:

‘application/vnd.allegro.beta.v1+json’ to ‘application/vnd.allegro.public.v1+json’.

On October 14, 2019 we will remove the following methods, which today we have marked as deprecated:

14AUG
2019

Handle email addresses correctly, to ensure proper settlement for the shipping costs

We are going to change the approach to settlement of the shipping cost of Allegro Smart! deliveries. Sellers will not receive the repayment for the Allegro Smart! delivery. They will be provided with payment for a product only.

To dispatch the delivery without any cost, sellers must transfer identical masked email address as in the order details provided by Allegro in the carrier Parcel Manager. The customer’s e-mail address provided on a dispatch label must be complete - it should contain the string visible after “+” - e.g .: 8awgqyk6a5+cub31c122@allegromail.pl.

information

Make sure your sales management system provides the full masked email address for each order

If a seller sends a package but does not provide the customer’s full masked email address in the @allegromail.pl domain, wdelivery cost will be charged. The carrier will display a proper information in the Parcel Manager and at the end of the month he will issue an invoice to the seller for the delivery of these parcels.

When we will introduce these changes
The changes will be introduced gradually for subsequent sellers from the first week of September 2019. We will introduce the new billing model for all sellers on November 1, 2019.

You can find more details in Allegro help.

14AUG
2019

GET /sale/offers - we return information about shipping rates and provide filtering by shippingRates.id

Up to this date, information about shipping rates was returned only when referring to a specific offer with GET sale/offers/{offerId}. From now on, you can retrieve this information by calling GET /sale/offers. Moreover, you can filter GET /sale/offers response by shippingRates.id.

Sample request:

curl -X GET
https://api.allegro.pl/sale/offers?delivery.shippingRates.id={id}
-H ‘Authorization: Bearer {token}’
-H ‘Accept: application/vnd.allegro.public.v1+json’
-H ‘Content-Type: application/vnd.allegro.public.v1+json’ 
13AUG
2019

Orders in Allegro REST API - guaranteed time in the delivery section

We have introduced more details in response, when you call:

You will receive information about guaranteed time of delivery. The Guaranteed time of delivery is ensured by delivery method Kurier X-press and Kurier X-press pobranie. For other delivery methods you will receive null.


This method is gradually rolled out to subsequent sellers - Szybkie dostawy na Allegro - program pilotażowy

You can find sample response with the delivery section below:

“delivery”: {
        “address”: {
            “firstName”: “Jan”,
            “lastName”: “Kowalski”,
            “street”: “Grunwaldzka 182”,
            “city”: “Poznań”,
            “zipCode”: “60-166”,
            “countryCode”: “PL”,
            “companyName”: “Moja firma S.A.”,
            “phoneNumber”: “222333444”
        },
        “method”: {
            “id”: “04b07522-70e5-4dc3-b13b-7918ea717539”,
            “name”: “Kurier X-press”
        },
        “pickupPoint”: null,
        “cost”: {
            “amount”: “20.00”,
            “currency”: “PLN”
        },
        “smart”: false,
        “time”: {
            “guaranteed”: {                            – guaranteed time of delivery
                “from”: “2019-07-31T16:00:00Z”,        – delivery time from
                “to”: “2019-07-31T18:00:00Z”           – delivery time to
            }
        }
    },

You will find more information about orders in our tutorial.

12AUG
2019

Batch offer modification - change duration of offers

As of today, you can change the duration of offers with PUT /sale/offer-modification-commands/{commandId}.

Note!

  • In INACTIVE status you can freely change the duration of Buy Now offers and auctions.
  • In ACTIVE status:
    • You cannot change the duration for an auction;
    • For Buy Now offers you can only set option until all items are sold.
  • in ENDED status:
    • You cannot change the duration for an auction;
    • For Buy Now offers you can only set option until all items are sold. Remember to activate updated offer to be visible on the website.

You can find more details with sample requests in our guide - how to process list of offers.

12AUG
2019

Shipments - changes in delivery company ID

According to the previous announcement for orders with delivery methods:

  • Allegro Pocztex Kurier 48
  • Pocztex Kurier 24
  • Pocztex Kurier 48.

Instead of POCZTEX delivery company ID, provide Poczta Polska in the following processes:

9AUG
2019

Bidding/offers/{offerID}/bid resource released in public version. doBidItem is marked as deprecated.

We have completed the test period for bidding/offers/{offerID}/bid which allows you to place a bid in an auction and receive data about your bid. We will support the beta version until 23.08.2019. During this period, you can gradually switch to the public version. To switch to the public version, you should change the header value ‘accept’ from:

‘application/vnd.allegro.beta.v1+json’ to ‘application/vnd.allegro.public.v1+json’.

We marked doBidItem method as deprecated and:

  • from 2.09.2019 you will not be able to use it to buy in offer with BuyNow format;
  • we will remove this method on 14.10.2019.
2AUG
2019

Orders in Allegro REST API - more information in buyer section

We have introduced more information in response, when you call:

You will receive more details in the buyer section. Details are provided for each status of order: BOUGHT, FILLED_IN i READY_FOR_PROCESSING.

You can find sample response with the new buyer section below:

    “buyer”: {
        “id”: “1424041”,                    – customer id
        “email”: “ymu1woaqq+54111a037@user-dev.allegrogroup.pl”,
                                            – customer’s email address
        “login”: “example_login”,           – customer login
        “firstName”: “Tomasz”,              – customer name
        “lastName”: “Nowak”,                – customer surname
        “companyName”: null,                – customer company name
        “guest”: false,                     – does customer registered the account.
        “personalIdentity”: null,           – PESEL number
        “phoneNumber”: “+381 11 1111111”,   – phone number from customer settings
        “address”: {                        – address data from customer settings
            “street”: “Zielona 90”,         – street
            “city”: “Poznań”,               – city
            “postCode”: “62-111”,               – postal code
            “countryCode”: “PL”,            – country code
        }
information

You will receive more details in the buyer section for orders after 1.08.2019.

You can find more information in our guide - how to process orders.

1AUG
2019

New resource - refund a payment

We have introduced new resources, which allows you to refund a payment to the buyer and retrieve data about payment refunds::

information

Via REST API You can refund payments created after 31 July, 2019.

You can find more information in our guide - how to process orders.

31LIP
2019

Processing offers submitted to campaigns, special programs and Allegro badges

We have introduced resources for processing offers submitted to campaigns, special programs and Allegro badges:

You can find more details about submitting offers to campaigns in our tutorial.

30JUL
2019

Adding a product

We have added a new beta resource for adding new products, i.e. POST /sale/product-proposals. Provided data is verified by our team and accepted details of provided product are available to be assigned to an offer. Some data is accepted automatically, some manually - which may take some time.

When you want to assign the product to an offer, call GET /sale/products/{product.id} to find out which product details has been accepted and are available to be used in an offer.

The process is described in Assigning offers to a product tutorial.

26JUL
2019

Event journal concerning changes in seller’s offers

As of today, a new resource is available in beta version - GET /sale/offer-events. It is an event journal concerning changes in offers listed by authorized seller that occurred within the last 24 hours. You can receive the following types of events in the response:

  • offer was published (“type”: “OFFER_ACTIVATED”);
  • offer was changed (“type”: “OFFER_CHANGED”);
  • stock was changed in an offer - also returned after a purchase (“type”: “OFFER_STOCK_CHANGED”);
  • price was changed in an offer (“type”: “OFFER_PRICE_CHANGED”);
  • offer was ended (“type”: “OFFER_ENDED”).

information

The resource allows you to get events concerning active offers and offers scheduled for activation (status ACTIVE and ACTIVATING). Returned events do not concern offers in INACTIVE and ENDED status.

In request query you may use the following parameter to adjust the response to your needs:

  • from - the id of the last seen event - to receive all events after the given event id (e.g. from=MTEzMjQzODU3NA);
  • limit - the number of events which you want to receive in the response (default - 100, max. 1000);
  • type - the type of events which you want to receive in the response (np. type=OFFER_ENDED).

Sample request - which allows you to get 200 events concerning the stock change, which occurred after the event “id”: “MTU2Mzg2NTM5MTU2Mzg0Ng”

curl -X GET 
https://api.allegro.pl/sale/offer-events?from=MTU2Mzg2NTM5MTU2Mzg0Ng&limit=200&type=OFFER_STOCK_CHANGED'
-H ‘Accept: application/vnd.allegro.beta.v1+json’
-H ‘Authorization: Bearer {token}’

You can find more details about the new resource in the documentation.

25JUL
2019

GET /order/checkout-forms returns payment.finishedAt date for orders with cash on delivery

To this date, the date for payment.finishedAt in GET /order/checkout-forms resource was returned only in orders with payment in advance. As of today, you will receive it for orders with cash on delivery in READY FOR PROCESSING status.

25JUL
2019

On July 30, 2019 we will remove allegroapi.io domain

According to the previous announcement, we remind you that on July 30, 2019 we will remove allegroapi.io domain. If you are still using allegroapi.io to communicate with REST API, you should update the domain address to api.allegro.pl in your system.

To switch to allegro.api.pl domain change call address from https://allegroapi.io/ to https://api.allegro.pl/

You can find more details about available addresses for calling the methods and the authorization process in our guide.

12JUL
2019

New resource which returns list of categories supporting the Compatibility list

At the end of June we published new resources for Compatibility list management. As of today, a new resource is available GET /sale/compatibility-list/supported-categories. The new resource allows you to get the list of categories where Compatibility list is available with additional details.

You can find more details in this tutorial.

11JUL
2019

Shipments - changes in delivery company ID

As of 12 August 2018 for orders with delivery methods:

  • Allegro Pocztex Kurier 48
  • Pocztex Kurier 24
  • Pocztex Kurier 48.

Instead of POCZTEX delivery company ID, provide Poczta Polska in the following processes:

09JUL
2019

New features in resource - GET /sale/loyalty/promotions?user.id={Seller_ID}

We have introduced a new features in GET /sale/loyalty/promotions?user.id={Seller_ID}. You can filter data by offer id and promotion type:

  • BUNDLE - promotional sets of offers,
  • MULTIPACK - quantitative discounts on a single offer,
  • CROSSMULTIPACK - quantitative discounts on many offers.

Sample calls:

Note! Even if you set the limit and offset parameters, the maximum number of promotional features that we will return is 50000. If you have created more promotional features on your account, use the filter: promotion type or offer id to retrieve the complete list.

09JUL
2019

Blacklist management

We have introduced new resources (in beta version), which allows you as a seller to manage your blacklist of buyers.

User, who is added to blacklist, will not be able to buy your items. You can remove him from the blacklist anytime and therefore enable him to buy in your offers.

To add user to blacklist, use resource POST /sale/blacklisted-users.

Note! You need to add buyer’s login or id in structure.

Sample request:

curl -X POST
https://api.allegro.pl/sale/blacklisted-users
-H ‘Authorization: Bearer {token}’
-H ‘Accept: application/vnd.allegro.beta.v1+json’
-H ‘Content-Type: application/vnd.allegro.beta.v1+json’
-d ‘{
    “user”: {
        “id”: 123456,                       - required (if login is not provided), buyer’s id
        “login”: “bad_buyer”                - required (if user.id is not provided, buyer’s login
    },
    “note”: “Rude person”                   - note about reason of blacklisting
}’

Sample response:

{
    “user”: {
        “id”: 123456,
        “login”: “bad_buyer”
    },
    “note”: “Rude person”,
    “createdAt”: “2019-05-08T09:45:818Z”    - date the user was added
                                            to the blacklist
}

You can retrieve the current blacklist using the resource GET /sale/blacklisted-users.

Sample response:

{
    “blacklistedUsers”: [
        {
            “user”: {
                “id”: 123456,
                “login”: “bad_buyer”
            },
            “note”: “Rude person”,
            “createdAt”: “2019-07-04T10:41:31.135Z”
        },
        {
            “user”: {
                “id”: 012345,
                “login”: “bad_buyer1”
            },
            “note”: “Rude person”,
            “createdAt”: “2019-07-04T10:35:10.013Z”
        }
    ],
    “offset”: 0,
    “limit”: 25,                            - limit of displayed results
    “total”: 2                              - number of users assigned to black list
}

In one query you receive up to 25 results. Use parameter “offset” with multiplied “limit” value to browse more users.

To remove user from blacklist use resource DELETE /sale/blacklisted-users/{userId}.

02JUL
2019

New resources - place a bid in an auction

We have introduced new resources (in beta version), which allows you to place a bid in an auction and return data about your bid:

To use these resources, you need to be signed in as user, who wants to place a bid in an auction.

Sample request:

curl -X PUT
‘https://api.allegro.pl/bidding/offers/{offerId}/bid'
-H ‘Authorization: Bearer {token}’
-H ‘Accept: application/vnd.allegro.beta.v1+json’
-H ‘Content-Type: application/vnd.allegro.beta.v1+json’
{
    “maxAmount”:                        - maximum amount that user is willing to
                                        pay for the auction
    {
        “amount”: “60”,
        “currency”: “PLN”
    }
}

Sample response:

{
    “maxAmount”: {
        “amount”: “60.00”,
        “currency”: “PLN”
    },
    “highBidder”: true,
    “minimalPriceMet”: true,
    “auction”: {
        “currentPrice”: {
            “amount”: “50.00”,
            “currency”: “PLN”
        }
    }
}
1JUL
2019

GET /sale/delivery-methods - additional information about delivery methods

From now you can get additional information about rules for delivery methods i.e. price, quantity, shipping time in GET /sale/delivery-methods

You will find more information in our tutorial.

28JUN
2019

PaymentId and transactionId mapping and filtering by payment.id and surcharges.id

From now on, you can call GET /payments/payment-id-mappings, to retrieve transactionId by providing paymentId or vice versa. Just provide values of one of the following parameters:

Sample request:

curl -X GET 
https://api.allegro.pl/payments/payment-id-mappings?paymentId=21f96ba2-714f-11e9-a1f2-5b017850bf22' -H ‘Authorization: Bearer’ -H ‘accept: application/vnd.allegro.public.v1+json’

Sample response:

{
    “paymentId”: “21f96ba2-714f-11e9-a1f2-5b017850bf22”,
    “transactionId”: “1012284437”
}

Identifiers are returned for payments created in last 3 months

Moreover, you can search orders by:

  • payment.id - GET /order/checkout-forms?payment.id=682c64b2-3108-11e9-b62a-6d16ee003b16
  • surcharges.id - GET /order/checkout-forms?surcharges.id=21f96ba2-714f-11e9-a1f2-5b017850bf22

For more details, please refer to documentation.

28CZE
2019

Compatibility section – integrated vehicle database

As of August 2018, in selected categories sellers can add the Compatibility section to provide information on models the product they offer is compatible with. At present, the sellers are asked to provide the said information as text description.

Today, we have published a new version of the Compatibility section that is integrated with the TecDoc vehicle database. We include models the sellers introduced to the new version of the Compatibility section in our search engine. As a result, it will be easier and more convenient for buyers to find an offer and check the compatibility.

The new version of the Compatibility section is supported in selected categories. Depending on the category, you can fill in the section using one method only, i.e. by providing vehicle IDs or by entering a text description.

information

If the section in your offer is filled in as a text description, but the category supports only integrated vehicle database:

  • Transfer the unchanged content of the section using PUT /sale/offers/ and edit other data
  • If you want to edit the content of the Compatibility section, you need to switch to the integrated vehicle database.

You can find more details in this tutorial.

27JUN
2019

Automatically republish offers

As of today you can automatically republish offers or auctions via REST API:

  • offers are republished with initial stock, regardless of how many items you have sold
  • auctions are republished only if they were not concluded with purchase.

If you want to automatically republish your offers or auctions add in offer structure:

“publication”: {
        “republish”: true
        }

You will find more details about listing offers in our tutorial.

26JUN
2019

Changes in GET /sale/offers

On July 10, we will change the default range of data returned for GET /sale/offers. The list of offers, without setting any filters, will include all offers of INACTIVE, ACTIVATING, ACTIVE and ENDED type, not only of ACTIVATING, ACTIVE and ENDED type.

Moreover, you can search the list by:

  • offer.id - GET /sale/offers?offer.id={offer.id}
  • more than one external.id - GET /sale/offers?external.id=1233&external.id=1234

For more details, please refer to documentation.

24JUN
2019

On July 15, 2019 we will remove allegroapi.io domain

According to the previous announcement, we remind you that on July 15, 2019 we will remove allegroapi.io domain. If you are still using allegroapi.io to communicate with REST API, you should update the domain address to api.allegro.pl in your system.

To switch to allegro.api.pl domain change call address from https://allegroapi.io/ to https://api.allegro.pl/

You can find more details about available addresses for calling the methods and the authorization process in our guide.

14JUN
2019

History of payment operations

We have introduced a new resource for retrieving history of seller’s payment operations, i.e.
GET /payments/payment-operations
. Sort and filter the results to get the data you are looking for.

A sample request – displaying payments made June 12, 2019:

GET /payments/payment-operations?occurredAt.gte=2019-06-12T00:00:00.000Z&occurredAt.lte=2019-06-12T23:59:99.999Z&group=INCOME

For more information, please refer to the documentation.

On February 10, 2020, we will remove the following methods, which today we have marked as deprecated:

12JUN
2019

Shipping rates - get delivery methods assigned to your offers

We have implemented a new resource GET /sale/offers/{offerId}/shipping-rates, you can use this resource to get delivery methods assigned to offers without shipping rates. You can use received data to create a new shipping price list. You will find more details about shipping rates in our tutorial.

GET /sale/offers/{offerId}/shipping-rates

Use this resource to get delivery methods assigned in offer without a shipping rate. You must be logged as a seller account.

Sample request:

  curl -X GET 
https://api.allegro.pl/sale/offers/8151913057/shipping-rates' -H ‘Accept: application/vnd.allegro.beta.v1+json’

Sample response:

{
    “rates”: [
        {
            “deliveryMethod”: {
                “id”: “845efe05-0c96-47c3-a8cb-aa4699c158ce”    – shipping method ID
            },
            “maxQuantityPerPackage”: 1,                         – quantity per parcel
            “firstItemRate”: {                                  – shipping cost
                “amount”: “11.00”,
                “currency”: “PLN”
            },
            “nextItemRate”: {                                   – shipping price of
                                                                another item in the parcel
                “amount”: “0.00”,
                “currency”: “PLN”
            },
            “shippingTime”: {                                   – shipping time
                “from”: “PT72H”,
                “to”: “PT120H”
            }
        }
    ]
}
04JUN
2019

Productization - filtering the search results

You can narrow the search results received with GET /sale/products by using the filters returned in the response. We explained the details in this article.

Reminder - since 2019, we have been grouping offers presenting the same product. You can find more details on For sellers page.

17MAY
2019

New filter Shipping from Poland

A new filter – Shipping from Poland (shippingFromPoland) is available for GET /offer/listing in selected categories. Before this change, the filter was based upon data provided by the seller in parameters 128188 and 129626. After the change, the filter is based upon location of the seller saved in the Country field (location.countryCode).

As of May 20, 2019:

  • We will not return results for filters parameter.128188 and parameter.129626; moreover, these filters will not be displayed on the list of filters.
  • You will receive results only for the new filter – shippingFromPoland.

Przykłady użycia:

  • GET /offers/listing?shippingFromPoland=1 (“Shipping from Poland - yes),
  • GET /offers/listing?shippingFromPoland=0 (“Shipping from Poland” - no).

To learn more on searching for offers and filters, read our guide.

13MAY
2019

New process for listing advertisement - implementation

In accordance with earlier announcement,today we have implemented a new process for listing advertisement.

You will find more information in our tutorial.

7MAY
2019

WebAPI methods for processing and managing offers are going to be removed

As announced , we remind you that from June 3, 2019, we will remove the methods for processing and managing offers:

Switch to REST API resources, which allow you to list and manage your offers. You can find more details in this article.

6MAY
2019

GET /sale/offers in public version - UPDATE

Thank you for your comments. We restored publication.startedAt and publication.endedAt fields in the public version of GET /sale/offers.


25APR
2019

Allegro.io is not supported from 30th of July

As of the 30th of July we allegro.io domain no longer will be supported. If you still use allegroapi.io to communicate with REST API, you should update the domain address to api.allegro.pl in your system.

Aby przejść na domenę api.allegro.pl wystarczy w adresie wywołania zmienić wartość: To switch on the address change in the call domain from: https://allegroapi.io/ to https://api.allegro.pl/

You can find more details about available addresses for calling the methods and the authorization process in our guide.

24APR
2019

Manage additional email addresses

As of March 26, the buyer’s email address will be returned as a string in the @allegromail.pl domain, e.g.:

  • 8awgqyk6a5@allegromail.pl - encoded version of the email address
  • 8awgqyk6a5+cub31c122@allegromail.pl - encoded version of the email address with information about the transaction.

We have introduced this change because of security reasons and to protect personal data. All addresses are masked on Allegro. The masked email address consists of an encoded seller-buyer pair and information about the transaction. To read more about email address masking, please visit Allegro Help.



As a result, to contact sellers, buyers must use accounts assigned to their accounts. For this reason, we offer you resources for managing additional email addresses:

More information you will find in our tutorial.

18APR
2019

GET /sale/offers in public version

We have completed the test period for GET /sale/offers, and today we have released it in the public version. The resource allows you to manage your offers. We will support the beta version until 6.05.2019. During this period, you can gradually switch to the public version.
To switch to the public version, you should change the header value ‘accept’ from:

‘application/vnd.allegro.beta.v1+json’ to ‘application/vnd.allegro.public.v1+json’


Note! In the public version, we do not return the startedAt and endedAt fields.


UPDATE:
Thank you for your comments. We restored publication.startedAt and publication.endedAt fields in the public version of GET /sale/offers.


On August 5, 2019, we will remove methods or managing list of seller’s offers from WebAPI. This applies to the following methods, which were marked as deprecated:

We recommend to migrate to REST API counterparts.

16APR
2019

Assign offers to products

As of March 20th, you can assign a product in the offer. As a result, we can group your offer with other offers presenting a given product. This is a new feature we introduced in early 2019 in selected categories. We plan to introduce the feature to other categories as well. Therefore, it will be easier for customers to find offers matching their expectations.

You will find more details in our tutorial.

8APR
2019

New process for listing advertisement postponed to the beginning of May

In accordance with earlier announcement , because migration old adverts takes more time than we originally expected, we decided to postpone new process for listing advertisement.

More information you will find in our tutorial.

4APR
2019

We are going to remove the personal pick-up delivery method - you will not be able to add it to shipping price lists.

In accordance with earlier announcement, are going to remove the personal pick-up delivery method. From Monday, 8.04.2019, you will not be able to add to shipping price lists:

  • Personal pick-up - id a6e4845b-9ace-48ea-b232-918eaf11ba6c
  • Personal pick-up (CASH_ON_DELIVERY) - id 57b987de-ce2d-4e73-9b9f-a7c9ebe9611d

You can use a new method - “Seller pick-up point”.

Owing to the new Seller’s pick-up points:

  • we will display the seller pick-up point on the map that customer sees in the purchase process
  • Information about selected pick-up point:
    • will be sent via e-mail - to customer and merchant
    • will be provided in response of Allegro API in resources for orders management
    • will be shown in Orders and Bought tabs
  • customer cannot select payment method, which is not available in selected pick-up point.

Note! If merchant did not specify pick-up point details, a customer cannot use the new method during the purchase process. In this case the other delivery method option is displayed, where customer can enter any delivery cost. Therefore, we strongly suggest to add pick-up point details to you account:

1APR
2019

doGetItemsList disabled

As announced, we have turned off the doGetItemsList method today.
We recommended to use the REST API method GET /offers/listing , more information here.

29MAR
2019

New process for listing advertisement postponed to the second quarter of 2019

Due to technical problems, we decided to postpone the implementation of new process for listing dvertisement that we announced earlier.
We will inform you in advance about the new implementation deadline.

20MAR
2019

Offer details - new field endedBy

We’ve added today a new field - endedBy in GET /sale/offers/{offerId} resource, in which you receive the reason of offer terminating.

13MAR
2019

As of March 26th we will start masking e-mails in the Allegro API

As of March 26th through the Allegro API we will return the buyer’s email address as a string of characters in the domain @allegromail.pl:

  • 8awgqyk6a5@allegromail.pl - masked version of the email address
  • 8awgqyk6a5+cub31c122@allegromail.pl - masked version of the email address with information about the transaction
We have introduced the change to protect the personal data. E-mail addresses will be masked throughout the whole Allegro.

We will implement the change in both REST API and WebAPI Allegro in resources for handling orders as well as downloading user data.

7MAR
2019

New process for listing dvertisement

As of March 31th before publishing advertisement add by POST /sale/offer-classifieds-packages/{offer-id} selected promotion package and additional options. If you do not add to your advertisement any package, you will not be able to publish it.

More information you will find in our tutorial.

Note! As of March 31th you will no longer be able to post an advertisement by Allegro WebAPI.

5MAR
2019

Multi-variant offers - we automatically combine offers by color/pattern.

Note! We have removed this change.

Note! We have changed the implementation date. We will inform about the new implementation date.

As of March 12th, when you combine offers by color/pattern, you do not need to enter the value for this parameter in the offers array. The value for this field will be determined automatically based on the offer’s main photo.

Note ! Remember that the offers you want to combine by color/pattern must have the identical main photo (thumbnail).

curl -X PUT
  ‘https://api.allegro.pl/sale/offer-variants/{setId}’
  -H ‘Accept: application/vnd.allegro.beta.v1+json’
  -H ‘Content-type: application/vnd.allegro.beta.v1+json’
  -H ‘Accept-Language: pl’
  -H ‘Authorization: Bearer {token}’
  -d  ‘{
  “offers”: [                                           – array with offers you want to
                                                        combine into a multi-variant one
    {
      “id”: “7436547561”,                               – offer ID
    },
    {
      “id”: “7436547336”,
    },
    {
      “id”: “7436547004”,
    }
  ],
  “name”: “Koszulki”,                                   – internal name of the multi-variant
                                                        offer string field; max. 64 characters
  “parameters”: [                                       – array with parameters used to
                                                        combine offers. You can set
                                                        up to 2 parameters
       {
         “id”: “54”                                     – ID of a parameter you want to use
                                                        to combine offers. Call GET on
                                                        /sale/categories/{categoryId}/parameters
                                                        to retrieve a parameter ID for
                                                        a particular category
    },
     {
        “id”: “color/pattern                            – value you use to combine offers,
                                                        color/pattern
    }
   ]
}’

27FEB
2019

We remove the delivery method self-pickup and replace it with a seller pick-up point

In accordance with earlier announcement we remove the delivery method self-pickup. We replace it with a new method “Seller pick-up point”. The migration will take several weeks.
Thanks to the change:

  • we will display the seller pick-up point on the map that customer sees in the purchase process
  • information about the selected by customer pickup point, we will:
    • provide in the mail
    • return through Allegro API in resources to orders management
    • show in my allegro to the customer in the purchased
    • show in my allegro to the seller in the orders
  • the customer will not be able to order with on delivery payment to a point that do not have this form of payment.
Note! If the partner did not specify collection points and the customer decides to choose a new method, we will not display the map and he will not be able to use this delivery method. The customer will see a different delivery method, and a window below in which he will be able to enter any delivery cost. Therefore, add personal collection points to your account:

27FEB
2019

New resource to get a list of tracking numbers

We have introduced a new resource - GET /order/checkout-forms/{checkoutForm.id}/shipments in beta version. It allows you to get a list of tracking numbers assigned to the order.

19FEB
2019

New resource to add a tracking number

We have introduced new resource - POST /order/checkout-forms/{checkoutForm.id}/shipments in beta version. It allows you to add a tracking number to the order. You can assign it to any selected lineItems.id from an order.

We are working on the GET method to retrieve the tracking numbers added to a specific order. It will be available in the coming weeks. More details will be published soon.

14FEB
2019

List of offers - new value and filter - external.id

We have introduced a new signature (external.id) field in GET /sale/offers/ resource. External.id can be also used as a filter for the list of the offers.

Sample request for filter use - GET /sale/offers?external.id={external_id}.

14FEB
2019

Changes in the resource /sale/offer-contacts

As of today, if you want to create a new contact with /sale/offer-contacts resource, you must provide at least one phone number or email address. Otherwise, you will receive a response with 422 status:
“Add at least one phone number or email address to your contact.”

11FEB
2019

Allegro REST API documentation in the new version

We have implemented a new view of Allegro REST API documentation. You will find, among other things, information on whether a given resource is public.

6FEB
2019

Improvements in the resource to search and view offers in the REST API

We have implemented two changes in the resource /offers/listing:

  • the offset value no longer has to be a multiple of the limit,, you can enter any numeric value
  • for numeric values outside the allowable range (for example, -1 lub 3847498327493279847), or those that are not integer, we will return an error with the status HTTP 422 Unprocessable Entity.
30JAN
2019

Changes in the data of delivery methods

  • 4.02.2019 we will change the names of delivery methods in REST API and WebAPI
  • Because of that changes:

    • in Allegro API we will use the same names of delivery methods
    • the names will be better presented in mobile applications, because many of them will be shorter

  • 28.02.2019 we will change the maximum values for shipping methods in REST API and WebAPI.
  • Because of that in Allegro API we will use the same maximum values for shipping methods in the Allegro API.

28JAN
2019

Fee Calculator - Update

We have updated the Fee Calculator in REST API. We have added new field in response “cycleDuration”. In this field you will find information in what cycles we will charge a given fee. More information about fees and commissions you can find in our terms and conditions. The change is backwards compatible and we do not upgrade the resource.

{
    “quotes”: [
        {
            “type”: “listingFee”,                – type of initial payment
            “name”: “Opłata za wystawienie”,     – name of the fee
            “fee”: {                             – amount in PLN
                “amount”: “0.00”,
                “currency”: “PLN”
            },
            “cycleDuration”: “PT240H”            – information in what cycles
                                                 we will charge the fee
        },
…
24JAN
2019

New REST API options for uploading photos

You can upload photos with a link using HTTP and HTTPS protocols (only with a valid certificate) in method POST on https://upload.allegro.pl/sale/images. Rules concerning photos remain unchanged:

  • minimum size – longer side at least 500px,
  • maximum size – 2560x2560px,
  • photos can be of any aspect ratio – of 1:1, 4:3, 16:9 or other
  • supported files: jpg, png and gif.
The other method that requires providing file content in the binary form is also available.
21JAN
2019

February 21, 2019 we will remove the delivery method self-pickup - replace it with a seller pick-up point

February 21, 2019 we will remove the delivery method self-pickup. Until then, replace it with a new method “Seller pick-up point”. Thanks to the change:

  • we will display the seller pick-up point on the map that customer sees in the purchase process
  • information about the selected by customer pickup point, we will:
    • provide in the mail
    • return through Allegro API in resources to orders management
    • show in my allegro to the customer in the purchased
    • show in my allegro to the seller in the orders
  • the customer will not be able to order with on delivery payment to a point that do not have this form of payment.

How to enable seller pick-up point, which customer will be able to choose from the map:

REST API

Add a new delivery method to your shipping price lists using the /sale/shipping-rates/{id}. Remember to not send data for the current delivery method

  • Self-pickup - id a6e4845b-9ace-48ea-b232-918eaf11ba6c
  • Self-pickup (CASH_ON_DELIVERY) - id 57b987de-ce2d-4e73-9b9f-a7c9ebe9611d

WebAPI

Use the DoChangeItemFields method to assign new delivery method to your offers. remember to remove fid 35 - “Free delivery options”.

Note! You can add pick-up points using method /points-of-service. Complete all information about the point at which the customer can pick up the order.

17JAN
2019

New delivery methods - Seller pick-up point

We have introduced new delivery methods. You can get identifiers in the resource GET/sale/delivery-methods:

  • Seller pick-up point - id afa68f62-0154-4556-9ee4-3f97c3c5bdca
  • Seller pick-up point (CASH_ON_DELIVERY) - id b6d6e4cf-67b3-4a4f-a38d-724335e9734f

Note! You can define a list of points by dedicated resource /points-of-service, more information here.

17JAN
2019

Allegro API applications management - you can delete the application key

On Allegro API application management page, you are able to delete the application key which you do not need.

If you want to delete the application key click on the button “DELETE” in a given row.

Note! If you delete the application key, you will not be able to restore it, and all associated Allegro accounts will lose their connection with that application.

9JAN
2019

End of WebAPI support – offer and sales management. Use REST API

As of August 2016, you can connect to Allegro using two API protocols, i.e. REST and SOAP. The one we focus on is REST API that supports all new functionalities we add. Recently, we have introduced a set of REST API resources you can use to::


Plans for Allegro API

We focus on REST API

We would like to remind you that the resources that allows list and edit the offer are public version from September 2018.

REST API schedule - February / March 2019

  • Product-based shopping experience – grouping offers presenting the same product
    • we will introduce resources for assigning new and existing offers to products from our base. The resources will be introduced as beta versions to test them and collect your feedback.
    • At the same time, we are working on resources that will let you add products to our base.
  • resources for managing orders will be available as public. As we are open to your suggestions and comments, we invite you to test the beta resources
  • new resources for adding information about the parcel
  • together with InPost we will work on integration issues related to new order numbers.

Phasing out WebAPI

WebAPI is an old solution we maintain owing to backward compatibility with current applications. However, we are no longer working on it and we will eventually deactivate it.


We will inform you about plans concerning other API methods and resources on a regular basis. Should you have any questions, zachęcamy do kontaktu.

9JAN
2019

Changes in the resource points of service

As announced from today in methods POST and PUT on the resource /points-of-service in structure “address” fields:

  • “Street”
  • “Coordinates”

become mandatory. Detail description of resources for managing points of service you will find here.

08JAN
2019

Show your users account confirmation screen when they are approving access to your application

We’ve added today a screen where user confirms the account on which he wants to approve access for your application:


Because of that user can make sure he links the correct account with the application.

NOTE! If the user is not logged in instead of the account confirmation screen, we will display the login page.

03JAN
2019

Technical break

We would like to inform that on January 9, from 01:00 to 05:00, Allegro are going to do some maintenance works.


REST API and WebAPI Allegro could be unavailable.

24DEC
2018

Client_credentials flow for Allegro OAuth2

We have introduced a path within Allegro OAuth2 that allows you to log on without using the seller’s account. Therefore, you can access resources that do not require user context (such as retrieving a list of categories, browsing through listing, etc.)

12DEC
2018

[Announcement] Changes in the resource points of service

From 09.01.2019 in methods POST and PUT on the resource /points-of-service in structure “address” fields:

  • “Street”
  • “Coordinates”

become mandatory. Detail description of resources for managing points of service you will find here.

10DEC
2018

New delivery methods - Delivery by the seller

We have introduced new delivery methods. You can get identifiers in the resource GET/sale/delivery-methods:

  • Delivery by the seller - id c9091ffb-727e-4a88-bd7c-b17dddbefb4a
  • Delivery by the seller payment on delivery - id d1744bea-fb26-49d4-a2b9-2b59c25132e1
  • 03DEC
    2018

    Technical break

    We would like to inform that on December 4, from 00:00 to 02:00, Allegro are going to do some maintenance works.


    REST API and WebAPI Allegro could be unavailable.

    26NOV
    2018

    New field external.id in events and orders

    We have introduced a new field - external.id in the following resources:

    external.id value will be returned in all orders created after November 22nd, if seller provided such information in the offer.

    22NOV
    2018

    New resources - bulk editing price and quantity

    We have introduced resources for:


    1. Editing price in many offers:


    2. Editing quantity in many offers:

    21NOV
    2018

    New field in string parameters - allowedNumberOfValues

    In resource GET /sale/categories/{categoryId}/parameters we have implemented new field “allowedNumberOfValues” in string parameters (you can add one or more values). In this field you can check how many values you can enter in a given parameter

    Example for parameter “Załączone wyposażenie” (category id: 67480)

    {
        “id”: “216917”,
        “name”: “Załączone wyposażenie”,
        “type”: “string”,
        “required”: false,
        “unit”: null,
        “options”: {
            “variantsAllowed”: false,
            “variantsEqual”: false
        },
        “restrictions”: {
            “minLength”: 1,
            “maxLength”: 40,
            “allowedNumberOfValues”: 10     – information on how many values
                                            you can enter in a given parameter
        }
    }

    20NOV
    2018

    Allegro API applications management - modify the redirect address

    On Allegro API application management page, you are able to change the redirect URI of the already existing applications

    To change the redirect address, click on “EDIT” button below the address, which you want to change. Then you can enter the new address and save it. No limitations were implemented, you can change the address as many times as needed.

    15NOV
    2018

    Linked apps

    From today in a dedicated tab “Linked apps” in “My Allegro” the user can:

    • check what apps are linked to his account
    • unlink the app.

    14NOV
    2018

    Device flow for Allegro OAuth

    While working on new features of Allegro OAuth we have prepared a new path for authorizing users on devices or in apps that do not have:

    • a graphic interface,
    • a browser
    • or other simple mechanism for entering the text.

    04NOV
    2018

    New resources – managing quantitative discount badges displayed on a list of offers

    We have introduced new resources for handling and managing paid new special badges for quantity discounts on one offer.

    30OCT
    2018

    New “smart” field available in order details

    We have introduced a new field - smart. From now on, the following resources return information about a SMART option selected by the buyer:

    30OCT
    2018

    From November 8th EAN value will not be returned in doShowItemInfoExt i doGetItemsInfo responses

    From November 8th EAN value will not be returned in doShowItemInfoExt and doGetItemsInforesponses. The values for EAN field will always be set to empty.

    You are still able to get the EAN value in methods and resources, which allows you to get details about offers listed by authorised seller:

    25OCT
    2018

    New “discounts” field available in order details

    We have introduced a new field - discounts. From now on, the following resources return information about a discount selected by the buyer:

    Values returned:

    • COUPON - a coupon has been used,
    • BUNDLE - some items have been ordered within a set,
    • MULTIPACK - at least one item has been subject to a quantitative discount,
    • CROSSMULTIPACK - some of the items have been subject to quantitative discounts in different offers.
    25OCT
    2018

    Technical break

    We would like to inform that on October 28, between 01:50 summer time and 03:30 winter time, service and REST API Allegro will be unavailable.

    22OCT
    2018

    REST API - Multi-variant offers new field - verification parameter

    We have introduced new field ‘variantsEqual’ (verification parameter). If you want to combine offers in multi-variant offers, all variants of the offer must have the same values in the parameters with the option ‘variantsEqual’.

    18OCT
    2018

    New resource - my offers in beta version

    We have introduced beta version of resource that will allow you, after logging on to a seller account, to get your offers via REST API

    15OCT
    2018

    New field in response - Manage shipping price lists

    We have introduced new field “paymentPolicy” in response:

    12OCT
    2018

    Limiting the number of offers to editing

    As of today, we have introduced a limit of information you can transfer within one query to:

    Therefore, the number of offers you can edit at once has been limited to 1,000. If you transfer more than 1,000 offer IDs an error will be returned.

    {
        “errors”: [{
            “code”: “VALIDATION_ERROR”,
            “message”: “size must be between 0 and 1000”,
            “details”: “Invalid value”,
            “path”: “offerCriteria[0].offers”,
            “userMessage”: “size must be between 0 and 1000”
        }]
    }
    10OCT
    2018

    In April 2019, we will delete the method doGetItemsList

    Today the method doGetItemsList we will mark as deprecated.

    We recommended to use the REST API method GET on /offers/listing, more information here.

    09OCT
    2018

    New resources – dealId and lineItemId mapping

    From now on, you can call GET na zasobie /order/line-item-id-mappings to retrieve dealId by providing lineItemId or vice versa. The new method will allow you to link the new and old event log.

    09OCT
    2018

    New resource - Draft delete

    We have introduced a new resource to remove draft offers DELETE /sale/offers/{offerId}. Only offers with status “INACTIVE” can be deleted.

    08OCT
    2018

    Quantitative discounts for products purchased in several offers

    The promotions resource has been given new features. As of now, you can create a deal for products purchased in several offers. Therefore, the buyer is no longer limited to a single offer. For example, the customer may purchase products in three different offers and the cheapest product will be subject to a discount you set.

    04OCT
    2018

    New features in the resource to search and view offers in the REST API

    We have introduced two changes in the GET method on /offers/listing in REST API:

    • We have implemented new filter, by which you can search offers with free delivery SMART.
    • In response, we added a new field for numeric filters: “unit”.
    03OCT
    2018

    Update - Fee Calculator

    We have introduced changes to a REST API fee calculator. The “offer” field has a new parameter, i.e. “multiVariant” or “multivariate offer”.

    26SEP
    2018

    The resources that allows you list and edit the offer in public version from today

    We have completed the test period for resources that allows you list and edit the offer and today we have released them in the public version. We will support the beta version by 10.10.2018. During this period, you can systematically switch to the public version.


    To switch on the public version change the headers value: ‘accept’ and ‘content-type’ from:


    ‘application/vnd.allegro.beta.v1+json’ to ‘application/vnd.allegro.public.v1+json’


    The list of resources that we have issued in the public version::


    25SEP
    2018

    New resources – Manage tags and attachments in offers

    We have introduced a set of resources for managing tags in offers and uploading attachments. We have also added a section on tags to Listing offers through Allegro REST API.

    Read more to check the details.


    18SEP
    2018

    New resource - Dispute

    We have introduced resources that will allow you, after logging on to a seller account, to use dispute via REST API.

    We have created the following methods:


    11SEP
    2018

    Restrictions for changing the price in the active offer

    On September 24th, we will introduce the following restrictions for changing the price in the active offer:

    • If the offer price is lower than PLN 50 PLN - the seller can increase it by no more than another 50 zł
    • If the offer price is over 50 PLN, the seller can increase it by no more than another 100%.
    The restrictions apply to one-time change of the Buy Now price in active offers.

    If seller tries to change the price above those limits, in following resources:

    we will return the error message:
    • If the offer price is lower than PLN 50 PLN:
      “message”: “You cannot increase the price by more than PLN 50. The maximum price is PLN {Buy Now price + 50 PLN}.”
    • If the offer price is over 50 PLN:
      “message”: “You cannot increase the price by more than 100% The maximum price is PLN {Buy Now price + 100%}”.

    The seller may increase the price above those restrictions, but first the offer must be ended. Then the seller can change the price in the ended offer and then relist it.

    20AUG
    2018

    Technical break

    We would like to inform that on August 21, between 02:00AM and 05:00AM, Allegro are going to do some maintenance works.

    REST API Allegro may be unavailable.

    16AUG
    2018

    A new resource that you will retrieve the id of the last event

    Last week, we published resources, thanks to which you can manage orders in the REST API Allegro. Today we have published the resource order/event-stats. With its help you can download the last event for the authorized seller together with the date of occurrence of this event. With this data, you will be able to read subsequent events starting from the received event identifier within this resource.

    We have also added the field phoneNumber in the buyer section in the response of the GET method for the resource order/checkout-forms for each of the statuses.

    14AUG
    2018

    New resources – Manage shipping price lists

    In addition to already existing resources for managing shipping price lists linked to a seller account and offers:

    We have introduced new resources, which allows you to create and edit shipping price list:

    13AUG
    2018

    The resources that allows you list and edit the offer in public version from September

    The resources that allows you list and edit the offer , will be available in beta version until August 31. We have decided to extend the trial period to adjust those resources according to your comments and requirements.

    Resources will be available in public version from September, when we will implement following features:

    • offer tag administration
    • a shipping price list is not required when you relist or edit an offer via REST API. This is a temporary solution - a shipping price list is going to be required when you relist or edit an offer in first half of 2019
    • new resources for managing shipping price lists.

    13AUG
    2018

    Technical break

    We would like to inform that on August 16, between 02:00AM and 05:00AM, Allegro are going to do some maintenance works.

    REST API Allegro will be unavailable.

    08AUG
    2018

    New structure in the offer model - Compatibility List

    In resources::

    • POST method on /sale/offers
    • PUT method on /sale/offers/{offerId}}
    • GET method on /sale/offers/{offerId}

    we implemented a new section. If you sell in one of the selected sub-categories of automotive parts:

    In this section, you can add a list of cars to which the offered part fits. This section will be displayed under the offer description.

    07AUG
    2018

    New resources for order management

    We have introduced beta version of resources for order management within Allegro REST API. Use them to retrieve a list of events and then – order details. In October, WebAPI methods for order management will be marked as deprecated:

    We have introduced beta version of Allegro REST API resources for orders:

    27JUL
    2018

    As of today, Allegro REST API allows you to retrieve multi-variant offers.

    Therefore, we have a new dedicated resource for Allegro REST API:

    18JUL
    2018

    Update - Resource that will help you check when a fee is charged.

    We have updated the resource GET /pricing/offer-quotes to check fee charging date. We have added a new field in response ILF value - for maintaining offers, which will be counted from July 25.

    09JUL
    2018

    As of today, Allegro REST API allows you to create multi-variant offers.

    We have added new Allegro REST API resources to support multi-variant offers:

    Before you combine offers using the REST API multi-variant feature read this guide to - combining offers as well as best practices.

    03JUL
    2018

    As of today, Allegro REST API allows you to browse and search through offers displayed on listings.

    Therefore, we have a new resource for Allegro REST API:

    GET /offers/listing - I want to retrieve a list of offers according to provided parameters

    As a result, we will deactivate doGetItemsList in the early Q2 2019. We have indicated it as deprecated.

    03JUL
    2018

    You are able to list up to 100,000 offers on a single account

    Seller is able to list up to 100,000 offers on a single account. The limit is applied also to offers which seller listed with a date in the future. If the offer limit is exceeded and seller tries to list a new offer or relist finished offer, we will return the following error message:

    
          {“errors”: [{
                “code”: “PublicationValidationException.MaxActiveOffers”,
                “message”: “Offer cannot be published - your account has exceeded
                the maximum number 100 000 of active offers”,
                “details”: null,
                “path”: null,
                “userMessage”: “Nie można wystawić oferty - Twoje konto przekroczyło
                 maksymalną liczbę 100 000 aktywnych ofert”
            }]}
          
    02JUL
    2018

    Applications name

    You can add name for Your application on developers app page. You can do it in Application name field. We will display it to the customer, when he will try to connect with Allegro by application. After entering the application name, you will not be able to change it.

    How to give the name of an already registered application

    You can also give the name of the application that you have registered in the past. All you need to do is click on the Set Name link in the Application name column.

    28JUN
    2018

    Offer resources in beta until the end of July. We are waiting for your comments and opinions.

    The beta resources that allows you list and edit the offer, will be available until July 31.

    We have decided to extend the trial period because we have not recorded a satisfactory number of calls so far. Therefore, the trial period will last until 31/07/2018.

    We are open to your suggestions and comments, we invite you to test the beta resources After this period, we will mark them as public. Then the introduction of major changes due to backward compatibility will be difficult.

    We are happy to hear your comments, suggestions and comments - we invite you to our forum.

    22JUN
    2018

    We increase the number of contacts in advertisements

    In January, we provided new resources to manage contacts in advertisments. We informed about them in this article. Now we have increased the number of contacts you can add for a single Allegro account from 15 to 50 contacts.

    13JUN
    2018

    Relist finished offer

    A new option is released - sellers are able to relist a finished offer with the same ID. Such offer will be once again available in Allegro.

    You can relist finished offer (status ENDED) with ACTIVATE action in PUT /sale/offer-publication-commands/{commandId}.

    13JUN
    2018

    15th of June - we will finish all offers on our test environment

    On 15th of June around 9:00 AM we will finish all active offers on our test environment.

    We want to prepare for implementation of changes in category tree. We will start introducing the changes with test environment and it needs to be properly adjusted. Additionally we are going to unify the category tree between production and test environment.

    11JUN
    2018

    WebAPI User Agreement update

    We are constantly working on WebAPI and some of the technological changes we introduce require updates to the User Agreement.

    The new version of WebAPI User Agreement (click here to read it) will be effective as of June 18. What’s new?

    • adjusting the WebAPI User Agreement to GDPR requirements
    • introducing new mode to approve changes to WebAPI User Agreement
    • minor editorial changes

    Note that by using WebAPI you agree to comply with and be legally bound by the terms and conditions of WebAPI User Agreement. If you do not approve the changes we will have to lock your access to the service. Therefore, contact us.

    06JUN
    2018

    End of WebAPI support for offer and sales management. Use REST API

    We focus on REST API development

    Until the end of June 2018, you can use beta version of resources that allow you to list and edit offers. As we are open to your suggestions and comments, we invite you to test the beta resources.

    REST API schedule

    • July 2018 – resources that allow users to list and edit offers will be available in a public version.
    • July 2018 – beta version of resources that allow users to retrieve and manage Allegro orders will be available.
    • October 2018 – order related resources will be available in a public version.

    Eventually, Allegro REST API will be the only application programming interface for managing offers and orders.

    Deactivating WebAPI

    • New features will be developed for REST API only.
    • In October 2018, we will mark methods for offer and order management as deprecated. As of that moment, we will encourage you to switch to REST API.
    • In April 2019, we will remove the following methods for offer and order management.
    24MAY
    2018

    API keys – update

    We have introduced several changes concerning WebAPI and REST API keys.

    11MAY
    2018

    Update - Fee Calculator

    We have introduced changes to a REST API fee calculator. The “offer” field has a new parameter, i.e. “condition”.

    10MAY
    2018

    Technical break

    We would like to inform that on May 17, between 01:00 and 03:00, Allegro are going to do some maintenance works.

    REST API Allegro will be unavailable.

    9MAY
    2018

    Introducing a string parameter

    Pursuant to our previous announcement, we have introduced a string parameter.

    You can add it to offers via Listing form, WebAPI and REST API. Please note that the parameter is supported by two categories:

    At first, string parameters will not be required. However, some of them will eventually become obligatory.

    Any changes in this regard will be announced.

    23APR
    2018

    New parameter type – announcement

    In the next few weeks, we will introduce a new parameter type, i.e. string parameter

    that will allow you to define values.

    Two string parameters will be available:

    • with one value
    • with many values

    Sample string parameter:

    Composition:

    Cotton 80%

    Elastin 10%

    Polyester 10%

    19APR
    2018

    Bulk editing of offers – new features

    The option for bulk editing of offers and drafts has new features.

    At present, you can collectively assign:

    • additional services
    • size tables
    • invoicing options
    • shipping price lists
    • promo options
    • bold
    • featuring
    • highlighting
    • option for promoting an offer on a category page
    • promo package: featuring, highlighting and bold

    19KWI
    2018

    Size tables in REST API

    From now on you can retrieve IDs and content of size tables.

    12APR
    2018

    List and manage offers via REST API

    New beta version of Allegro REST API listing and offer management resources are available.

    We are still working on the beta version resources, but even though we encourage you to test them. The changes we want to introduce, e.g. size table will be available only through Allegro REST API.

    From now on, you can use REST API to:

    • list offers
    • end offers
    • edit offers
    • retrieve offers
    • retrieve category ID
    • retrieve category parameters

    Moreover, you can:

    • use shipping price list
    • transfer photos
    • create drafts to complete them later
    • use an external ID to link your offers with products in a warehouse
    22MAR
    2018

    New test environment - Allegro Sandbox

    A new test environment – Allegro Sandbox – is available at https://allegro.pl.allegrosandbox.pl. The new improved environment is more stable compared to the previous version. Try it to test current or new solutions.

    Unlike WebAPI Sandbox, Allegro Sandbox is always up to date and has all the features of the live site. Moreover, some new features may be first released on Allegro Sandbox.

    To learn more about the new environment, click here.

    We will deactivate current test environment soon:
    Attention! We will handle TLS 1.0 at new test environment only to April 2, so use TLS 1.1 or 1.2 as soon as possible.
    13MAR
    2018

    We cease to support https://ssl.allegro.pl

    Pursuant to our previous announcement we cease to support https://ssl.allegro.pl beacause we changed the domain address in the OAuth authorization process from https://ssl.allegro.pl to https://allegro.pl.

    From this moment, you should log on to https://allegro.pl only. Make sure to update the domain address in your system.

    7MAR
    2018

    GitHub instead of Facebook

    We merged all Facebook profiles of Allegro.pl with the main one.

    According to a survey we conducted a few weeks ago GitHub is the the best choice to provide technical support for API. You can find our repository here.

    All matters concerning API are described in Issues tab.

    6MAR
    2018

    We will cease to support https://ssl.allegro.pl

    In November 2017, we changed the domain address in the OAuth authorization process from https://ssl.allegro.pl to https://allegro.pl.

    Pursuant to our previous announcement we will cease to support https://ssl.allegro.pl on March 13. Once the domain is disabled, you should log on to https://allegro.pl only. Make sure to update the domain address in your system before March 13.

    28FEB
    2017

    Technical break

    We would like to inform that on February 28, between 02:00 and 04:00, Allegro are going to do some maintenance works. REST API Allegro will be unavailable.

    23FEB
    2018

    We are changeing the domain name allegroapi.io to allegro.pl

    From today our websites related to REST API will be available on the domain allegro.pl.

    If you provide the current website address, you will be redirected to the new domain.

    The change concerns:

    We also encourage you to change the address which you use in REST API from https://allegroapi.io on https://api.allegro.pl. We will maintain the current address by at least a year, we will inform you in advance about the planned date of its exclusion.

    14FEB
    2018

    Resource that will help you check when a fee is charged.

    As of August 2017, fees will be charged every 10 days. Therefore, we provide you with a resource that will help you check when a fee is charged.

    13FEB
    2018

    Quantitative discount and promotional sets - new field in response

    We have added new field in response for methods

    New field ‘status’ has two possible value:

    • ACTIVE - means that you have sufficient stock of items in your offer, so the promotion is ready to use.
    • SUSPENDED - means that you have too small stock of products, so the promotion is inactive. To use this promotion, fulfill the stock.

    IMPORTANT! Currently, this field will be always ACTIVE for Promotional Sets

    1FEB
    2018

    Quantitative discount

    Promotions resource gets a new feature – as of today, you can use it to manage quantitative discounts. Use them to offer discounts for a single item when purchasing a certain number of them. Example: if a customer buys three pairs of contact lenses, the fourth pair is discounted 50%.

    17JAN
    2018

    We offer resources to manage contacts

    Recently, we have introduced classified ads. Now, we offer you resources that will help you manage contacts in REST API

    24NOV
    2017

    Change the domain address in authorization process

    The domain address in an OAuth authorization process will change from https://ssl.allegro.pl to https://allegro.pl. Allegro REST API website has already been updated.

    Important! We plan to disable https://ssl.allegro.pl domain on March. Once the domain is disabled, you will be able to log on to https://allegro.pl. only. Make sure to update the domain address in your software.

    9NOV
    2017

    Bulk editing of offers

    New resources for bulk editing of offers are available. Use them to assign additional services such as gift wrapping, upstairs delivery, installation, etc.

    2NOV
    2017

    New additional services

    We do what we can to make sure your offers are as adjusted to the needs of shoppers as possible. Therefore, as of today you can manage additional services via API.

    30OCT
    2017

    Fee calculator

    After introducing classifieds ads, it is time to update a fee calculator in REST API.

    26OCT
    2017

    Technical break

    We would like to inform that on October 29 from 1:50 to 3:30 there will be a technical break due to change of time from summer to winter. During that time service will be unavailable, and the Allegro website will display a notice board announcing a technical break.

    Offers scheduled to end during the technical break, will be extended by 24 hours.

    In addition, PayU will not be available between 02:00 and 05:00.

    26OCT
    2017

    Allegro.pl sp. z o.o. will merge with Grupa Allegro sp. z o.o.

    On November 2, 2017, Allegro.pl sp. z o.o. will merge with Grupa Allegro sp. z o.o. All the rights and obligations of Grupa Allegro sp. z o.o. will be assumed by Allegro.pl sp. z o.o.

    It means that as of November 2, 2017, the administrator of your personal data will change its name. However, rules for protection and processing of personal data will remain unchanged. You have the right to access and correct your personal data as well as ask for discontinuation of its processing.

    In relation to the change, we will update Allegro User Agreement and terms and conditions of other services provided by Allegro.pl sp. z o.o. New Allegro User Agreement will be available here. Content that will be added is marked green and content that will be deleted is marked red.

    18OCT
    2017

    New promotional features

    We are glad to inform you about the introduction of new promotional features. From now on, sellers can offer a set of various items at a reduced price.

    9OCT
    2017

    New resources to download sales feedback

    We have introduced new resources that will help you retrieve received feedback and feedback statistics. Previous resources are marked as depracated and will be removed within six months. Therefore, we encourage you to use the new ones.

    19SEP
    2017

    Fee calculator

    A fee calculator that allows Sellers to check the fees charged in categories is available via REST API. Therefore, on October 19th we will deactivate doGetPaymentData, a method that returns inaccurate data.

    14AUG
    2017

    Points of service

    Our sellers can enjoy a new feature, i.e. Points of service. They can define a list of such points that will be displayed in the Shipping and payment section of their offers with personal pickup.

    Allegro REST API features the new resources to support Points of service: REST API Allegro.

    26JUL
    2017

    Technical break

    We would like to inform that on July 27 from 3:00 to 5:30 there will be a technical break due to maintenance. During that time you may experience disruption in operation of Allegro WebAPI or REST API.

    Offers scheduled to end during the technical break, will be extended by 24 hours.

    29JUN
    2017

    Technical break

    We would like to inform that on June 29 from 3:00 to 5:30 there will be a technical break due to maintenance. During that time you may experience disruption in operation of Allegro WebAPI or REST API.

    Offers scheduled to end during the technical break, will be extended by 24 hours.

    22JUN
    2017

    New resources to download sales feedback

    We have published two endpoints to download sales feedback.

    29MAY
    2017

    Technical break

    We would like to inform that on May 31 from 1:00 to 5:00 there will be a technical break due to maintenance. During that time you may experience disruption in operation of Allegro WebAPI or REST API, in particular you may experience payments problems.

    Offers scheduled to end during the technical break, i.e. between 1:00 and 5:00 on May 31, 2017 will be extended by 24 hours.

    11MAY
    2017

    Sandbox will be unavailable

    Today, on May 11, Sandbox will be unavailable from 12:00 due to maintenance. The service will be restored the next day.

    Remember that during the break, apart from no access to the test environment, all created data is permanently removed (e.g. additional users or purchase transactions).

    11MAY
    2017

    Technical break

    We would like to inform that on May 12 from 4:00 to 5:00 there will be a technical break due to maintenance. During that time you may experience disruption in operation of Allegro WebAPI or REST API, in particular you may experience logon problems.

    Offers scheduled to end during the technical break, i.e. between 4:00 and 5:00 on May 12, 2017 will be extended by 24 hours.

    06APR
    2017

    Removal of resources - “Publish your offer on Allegro.de too”

    We have removed two endpoints that allowed sellers to publish their offers on Allegro.de.

    05APR
    2017

    New resources - “List of offer conditions”

    We have introduced three new endpoints that allow you to retrieve lists of offer conditions.

    15MAR
    2017

    Technical break

    We would like to inform that on March 15, between 1:00 and 4:00, Allegro are going to do some maintenance works. REST API Allegro might be unavailable.

    06FEB
    2017

    Technical break

    We would like to inform that on February 8, between 6:00 and 7:00, Allegro are going to do some maintenance works. During the break, You could encounter a temporary problems with doing new offers and changing existing offers by API.