Allegro WebAPI

Programming interface of the Allegro platform


Last change: 01.09.2011 r.
This method allows for loading identifiers of after-sales forms previously completed by a logged-in user (arranged chronologically - the latest on top). It can be used e.g. for pre-filling out a new form with data selected earlier by the user.

  1. session-id | string | required
    User's session identifier received using the doLogin(Enc) method.
  2. payment-type | int | required
    Payment method for which all delivery and payment option forms are to be returned (mask: 1 - PayU, 2 -standard transfer, 4 - COD).
  3. user-role | int | required
    Role of a logged-in user in a context of loaded forms (1 - seller, 2 - buyer).
  4. filling-time-from | long | non-required
    Start date of time range (in the Unix time format) to load a list of filled-out after-sale forms.
  5. filling-time-to| long | nonrequired
    End date of time range (in the Unix time format) to stop loading a list of filled-out after-sale forms.

Sample structure of method call

$dogetfilledpostbuyforms_request = array(
   'session-id' => '22eb99326c6be29aa16d07d622bcfbcbee94ad54846f2f4e03_1',
   'payment-type' => 1,
   'user-role' => 2,
   'filling-time-from' => 1309392000,
   'filling-time-to' => 1309824000

  1. filled-post-buy-forms | FilledPostBuyFormsStruct
    Structure with identifiers of after-sale forms that have been filled out
    1. transactions-ids | long[]
      Transaction ID array. Details of each transaction can be obtained using doGetPostBuyFormsDataForBuyers/doGetPostBuyFormsDataForSellers methods.

Sample structure of server reply

$dogetfilledpostbuyforms_response = array(
   'filled-post-buy-forms' => array(
      'transactions-ids' => array(4481748, 4567893))

    Incorrect payment method identifier.
    Incorrect or empty role of a logged user.
    Internal system error due to loading PayU transactions.
    Invalid session identifier or the session has expired.
    The session-generating WebAPI key has been deactivated (the owner did not accept the User Agreement).

Allegro is not to be held liable for consequences of using examples of the published code. It does not guarantee its correct operation either. The code you see serves as an example only and may contain errors.