Preorder API

Stores can offer to their customers the possibility to purchase a publication in advance, before the official start of sale date. When a preorder is declared, the store must warn the warehouse with the preorder API. As soon as the publication becomes available for sale, a regular sale must be posted with the sales API. The customer identifier (customer_id) must match what was used to make the preorder. Download of the publication will be available as soon as the actual sale is declared on the platfom. The download can be initiated through the Download API.

Publications available for preorders

The following rules can be used in order to determine wich publications are available for preorders:

1. State is not available for sale:

2. <ProductAvailability>40</ProductAvailability>

3. Date from wich it is allowed to take preorders :

<PublishingDate>

<PublishingDateRole>09</PublishingDateRole>

<DateFormat>14</DateFormat>

<Date>20131107T000000-0500</Date>

</PublishingDate>

1. The expected start of sale date is indicated in the ONIX feed like this, always in the future :

<SupplyDate>

<SupplyDateRole>02</SupplyDateRole>

<DateFormat>14</DateFormat>

<Date>2012-10-25T00:00:00-04:00</Date>

</SupplyDate>

Declaration

Adresse : /api/organisations/[organisation_id]/publications/[publication_id]/preorders

Mehod : POST

Security : HTTP/BASIC (User and password)

Parameters

organisation_id : (Mandatory)

Id of the organisation doing the sale

publication_id : (Mandatory)

Identifier (ISBN, EAN or custom key) of the publication

for : (Mandatory)

epub or pdf

customer_id : (Mandatory)

Customer id for the preorder

Responses

200 : created

The preorder was created.

401

User authentification error.

404

The publication was not found.