Shoptet API (1.0.0)

Created in cooperation with the Ministry of Industry and Trade of the Czech Republic within the "The Country for the Future" programme.

This documentation provides information about the interface for developers who would like to gain access to Shoptet

e-shops. For more information about Shoptet, see https://www.shoptet.cz/.

The API is available in two access modes:

  • for "Shoptet partner” developers who create the interconnection with the services and extend the Shoptet system's functions for public usage. For more information about API and conditions, under which it can be used, see https://developers.shoptet.com/addons/.

  • direct private access to eshop data for eshop owner - available only for Premium Members. See https://developers.shoptet.com/premium for more information about API access.

Basic principles

How to call API

API supports communication in JSON format. The URL for calling API requests is https://api.myshoptet.com. The API calls

(endpoints and message formats) are common for private as well as addons access, it however uses different authentication

and authorization principles.

For Addons

API is made to create the supplements for the Shoptet system and uses OAuth2 authorization principles.

To access the API it is necessary to implement a web service at your side, which will communicate with our OAuth server.

In your e-shop administration, which you are using to work with our API, you must search in the API Partner section for the Access to API tab.

Here, you will find your clientID and addresses, from where you can call our OAuth server.

The work with API begins with e-shop addon installation. (The installation process can be tested in the addon detail in the Users section, where you can cause the installation for your e-shop.)

In your addon detail, in the Settings section, enter URL to gain a OAuth code. The URL must be linked to your server, where the script is prepared, which is able to gain an OAuth access token.

At this address, you will receive the HTTP request with a GET parameter code, when installing the addon, with unique value (a 255 character long string).

The code provided only has short-term validity and can be used only once. With this code, request our OAuth server to provide an OAuth access token.

Such a request shall follow within the same script that received the code.

Do not put off gaining the OAuth access token for a later time, and do not reply to our request with a 200 OK status, until you gain the OAuth access token.

The address for you to call, and an example of implementation, can be found in e-shop administration in the Access to API section.

As a response you will obtain a JSON with your OAuth access token. Save this token securely. Never send this token to the client computer, and use it only

for communication between the servers and for gaining the temporary token for access to API.

If you have successfully received an OAuth access token, your script must end with the HTTP status code “200”.

Now you have your OAuth access token, which links your addon with a specific e-shop, perhaps you would like to communicate with the e-shop via API.

From your server, call https://<eshop-address.tld>/action/ApiOAuthServer/getAccessToken address with HTTP header Authorization: Bearer <OAuth access token>.

As the reply, you will receive a JSON containing an API access token value and the token expiration time value. An example of calling can be found in e-shop administration in the Access to API section.

It is possible to request a maximum of 5 valid tokens.

The API access token will enable you to call an individual URL of our API, for example https://api.myshoptet.com/api/eshop. Send the API access token in each request in the HTTP headerShoptet-Access-Token.

You can have several valid API access tokens available at any one time. Should the validity of the API access token expire, you will receive a HTTP status code 401 and message about token expiration.


{
    "data": 'null',
    "errors": [
        {
            "errorCode": "expired-token",
            "message": "Token is expired. Please ask for new one.",
            "instance": "unknown"
        }
    ]
}

If your token does not have the access right for a specific endpoint, you will obtain a reply with HTTP status code 403 Forbidden.


{
    "data": 'null',
    "errors": [
        {
            "errorCode": "invalid-token-no-rights",
            "message": "Your access token \"afd..123\" has no defined rights for this resource.",
            "instance": "access-token"
        }
    ]
}

For private API access (Premium)

You can create API access tokens simply in the eshop administration. Send them in the request header Shoptet-Private-API-Token.

You can automatically access all API endpoints.

Rate limiting

Rate limiting is only at the level of server overload protection (DDoS), whereas the quantity of queries or total volume of data are unlimited.

These are therefore the limits of the maximum number of coincident active connections. A maximum of 50 from a single IP address, and a maximum of

3 connections for a single token. If the limit is exceeded, the HTTP code 429 is returned. See also Nginx configuration:

    limit_conn per_ip 50;
    limit_conn per_token 3;
    limit_conn_status 429;

Some URLs, for example for bulk operations, can have their own specific limits, which are mentioned in this documentation.

Locks

Write endpoints (DELETE, PATCH, POST, PUT methods) can take longer and may be prone to two concurrent matching requests.

To avoid problems with retrying identical write requests, we have added the locking function of these requests to the application.

If you execute the same request two times in quick succession, the second request receives error response with a 423 code.

The lock is only valid for a specific called URL, for the duration of the request processing, but no longer than 5 seconds.

API versioning

Current version of API: v1.0

The client must send a Content-Type header with value of application/vnd.shoptet.v1.0,

where v1.0 is the API version supported by the client. If there is any change in the API, then we are trying to make it

reverse compatible, therefore it is not necessary to regularly update your connection after each change in our interface.

The version is the same for all endpoints described here.

Server response format

All JSON responses from the server have the same format, as a base.

If any of the sections is not present in the response, a null value is then received.

Example of call for addons:


curl --include \
    -H 'Shoptet-Access-Token: 123456-a-123-XXXXXXXXXXXXXXXXXXXXXXXXX' \
    -H 'Content-Type: application/vnd.shoptet.v1.0' \
   'https://api.myshoptet.com/api/eshop'

Example of call for private API access:


curl --include \
    -H 'Shoptet-Private-API-Token: 123456-a-123-XXXXXXXXXXXXXXXXXXXXXXXXX' \
    -H 'Content-Type: application/vnd.shoptet.v1.0' \
   'https://api.myshoptet.com/api/eshop'

Example of response:


HTTP/2 200

date: Fri, 13 Jul 2018 15:57:29 GMT

content-type: application/vnd.shoptet.v1.0+json; charset=utf-8


{
    "data": {
        "contactInformation": {
            "eshopName": "www.domena-eshopu.cz",
            "url": "https:\/\/www.domena-eshopu.cz\/",
            "companyId": "28935675",
           ...
        }
        ...
    },
    "errors": 'null'
}

The basic structure of the response in the event of an error is as follows:


{
    "data": 'null',
    "errors": [
        {
            "errorCode": "missing-access-token",
            "message": "Missing access token. Please add `Shoptet-Access-Token` header to your request.",
            "instance": "unknown"
        }
    ]
}

Most of the endpoints are synchronous, i.e. your answer is provided immediately and contains the data requested. There

are however some endpoints, where either the request or the response processing takes longer time. These are implemented as

Asynchronous requests. Your request will be queued and you

receive only job identification in the response. You will be notified using a

webhook when the job is completed and your results

downloadable. Be aware, that registration of webhook job:finished is required to be able to run asynchronous requests.

If webhook is not registered, you will receive an error response with HTTP status code 403 and job won't be queued.

Webhook job:finished is also emitted when the job is failed so there is need to check the Detail of job to get the result of the job. If an error occurs during an asynchronous request, the job is automatically marked as failed 3 hours after its creation, and in this case, the job:finished webhook is not emitted.

Some attributes may be added to the new API version, or the sequence of attributes can be changed.

Your software, therefore, shall not rely on either of these.

If some attributes are renamed or removed, you will be informed in an additional

Deprecated header + Sunset

If you are calling some endpoint in a version that will not be supported in the future, you will receive a response with the header

X-Shoptet-Deprecated. If you detect this header within the response and its presence is logged,

you should be aware of the support termination for a specific endpoint in advance and thus have enough time for correction.

Furthermore, you shall also receive the response with aSunset header with the date when the support for this endpoint is to be terminated.

Status codes

When processing the response, the client shall first detect, what response status code was received.

For GET requests for responses with 200 code, it is not necessary to explore the errors part of the response.

For PATCH/PUT requests, which can process more records at the same time and some records

are not processed successfully, these end with a 200 response code and the errors key contains info on skipped rows.

The unknown record is returned with a 404 code, etc. These responses have the error field filled in, where you can

find detailed info about the error.

The following errors might be expected:

  • 400 - Some of the validations on item level have failed. There is no reason to retry, it will fail always.

  • 401 - Invalid token or the token has expired (for addons access tokens). You have to ask for another one.

  • 403 - Forbidden. The token has no rights to the endpoint called. The endpoints must be allowed for an addon and the eshop must have approved them. Valid for addons access tokens, private tokens can always access all endpoints. Can be also returned when required module for request is missing.

  • 404 - Either the endpoint is wrong; or most commonly, an entity identifier, which is part of the URL, does not exist.

  • 409 - Conflict - the action could not be completed for some consistency rules, such as duplicate data or relation, which would be broken.

  • 413 - Payload too large - update requests can sometimes contain multiple entities to be amended. There is however a limit (varying for each request), how many can be specified within one request. If you breach the limit, you will get this error and nothing will be updated.

  • 422 - Unprocessable entity - we were not able to parse the request - it does not match the expected format. Something is wrong with the request as whole, it might not be a correct JSON or it does not match the expected JSON schema. There is no reason to retry, it will always fail.

  • 423 - Locked - for update and some read request we apply locks, usually on an URL level, which should avoid consistency problems possibly occuring from parallel updates. See chapter about locks. Retry later, try to avoid parallel update requests.

  • 500 - General server error. Yes, this might happen to our software, too. Most commonly this is a temporary database issue and it might (but might not), work a few minutes later. We monitor all such errors and we try to analyze and fix them.

  • 503 - System maintenance. Most commonly we move a database to another database cluster or a database migration is pending and it will be available in a few minutes. Please try later.

Paging

Some endpoints can return larger quantity of records. Such endpoints do not return the entire result, but support pagination of results.

You can page using page (int) and itemsPerPage (int) parameters. The first page has number 1. If you require a different

quantity of items per page, use the itemsPerPage parameter. CAUTION: the number of items per page can be decreased only, the default

value is maximum. The default value can be different for each endpoint.

When paging, check the total number of items, if not altered (totalCount), then the

items on pages could be shifted and some of them could be missed or processed twice.

Section on demand

Some endpoints return the data sections as optional, on demand. The request is done by giving the section name in the

include parameter. Part of the data is returned each time, the other section only on demand. This makes the responses smaller for those, who do not need the data

, thus saving the volume of data transmitted and shortening the time to process the request.

For example, for "Eshop Info" endpoint, you will gain basic info when simply calling [GET] /api/eshop, but payment

methods and transport options only when using [GET] /api/eshop?include=paymentMethods,shippingMethods.

More values are separated by a comma, no sequencing, no upper/lower case differentiation. Other blocks are available on demand

and each endpoint informs you which identifier to request.

Translations

For proper functionality in translations you will have to get module Foreign languages (Cizí jazyky) activated on customer e-shop. Multi-language support in API is handled by query parameter language, which can be used in whole API. If parameter is not set, default shop language is used.

Read endpoints (HTTP verb GET) will return corresponding language version of texts where applicable.

For write endpoints, first use POST endpoint to create entity and then use PATCH endpoint with corresponding language query parameter to set language fields.

Please note that in some endpoints (typically surcharge/filtering/variant parameters) you must use the identifier's currently selected language variant (which is filtered in list).

Files

For files upload, there are Files endpoints.

The file is uploaded to a temporary storage which is not accessible publicly. The file is kept there for 7 days and then deleted.

After you upload a file, you may copy it to some API entities in their endpoints - you specify filename returned in response of upload job.

Please note that currently only images (png, jpg, gif) are allowed filetypes for file upload.

Product images

Shoptet saves the product images in their original size and then prepares several sizes for standardized usage (called

image cuts). These cuts are created in advance and saved on the disk, so they are readily available. The list of cuts is

the same for each e-shop, and each e-shop can theoretically have different cut sizes. In practice, their size is given

by the template and most templates use the same sizes. The list of provided cuts is given by

the Image cuts code list.

The /api/eshop?include=imageCuts endpoint returns the imageCuts field in the response, where each cut has the actual

size defined, and the URL base path. There are two base URLs (example for classic.shoptet.cz, cut detail):

  • urlPath: "https://classic.shoptet.cz/user/shop/detail/"

  • cdnPath: "https://cdn-api.myshoptet.com/usr/classic.shoptet.cz/user/shop/detail/"

Use the urlPath in case you need an up-to-date image right now. Use the url for your backend processing and you

will retrieve the images only once. Images retrieved via urlPath are not cached. You can use image name or SEO version

of the image name - see below.

Use the cdnPath in case you want to use the image url on the frontend and users of your application will display it,

e.g. if you provide an alternative frontend, mobile application etc. The images are cached and provided with lower

latency. Use cdnName retrieved from the product detail endpoint (or similar) - see below.

Once you determine the URL based on the purpose and image cut size (for example detail for product detail, or related

for product preview), just append the filename you need. The filename can be retrieved from Product detail endpoint.

Although the e-shop is behind the content delivery network (Cloudflare CDN), API still returns the same domain. Whether

the e-shop is behind the Cloudflare CDN, you can find out from response headers (CDN-Loop: cloudflare header).

The product detail endpoint /api/products/{guid}?include=images returns the image field data.images[] in the same

sequence, as these are entered in administration. The file name name (for example 100.jpg) needs to be connected

to the URL cut and then you have complete path to the image of a given cut (size), for example

https://classic.shoptet.cz/user/shop/detail/100.jpg. You can also use seoName, which also contains a description

of the image - you will be redirected to the same image. The cdnName is intended for use with the cdnUrl only.

The fields look like: (excerpt)

    "name": "106.png",
    "description": "shamrock 2115611 640",
    "seoName": "106_shamrock-2115611-640.png",
    "cdnName": "106_shamrock-2115611-640.png?5b2a41f5"

One of the images mentioned for the product can be selected as the default image for the product variant. The selected

image is in data.variants[].image item and contains the name of the image – this can be searched for in the image

list, in the name item. Should the variant have no preselected default image, the parameter image is null.

If data.variants[].isProductDefaultImage is true, then the default product image is given. If it is false, then it is the default variant image.

The item data.items[].mainImage contains the main image in order detail - this is either a default variant image,

or, if not set (or product does not have variants), the default product image is given. The structure is the same as

in product details, but not all images are given here, only the default one – representative image. The full path can

be gained by assembling the urlPath from the e-shop info and the name or seoName items, given for the order item.

Similarly, the product list gives data.products[].mainImage, which mentions the initial image for each product.

Code lists

Image cuts

ValueDescription
origoriginal image (in the original resolution)
bigbig image (typically 1024x768 px)
detailimage detail (typically 360x270 px)
categorysize for listing in category (typically 216x105 px)

Product visibility

ValueDescription
hiddenHide product
visibleShow product
blockedCannot be ordered
show-registeredShow only to logged-in users
block-unregisteredDo not allow order to logged-out users
cash-desk-onlyShow only in cash desk
detail-onlyDo not show e-shop navigation

Product types

ValueDescription
productProduct
bazarSecond-hand product
serviceService
gift-certificateGift (deprecated)
product-setProduct set

Types of order items

ValueDescription
productProduct
bazarSecond-hand product
serviceService
shippingTransportation
billingPayment method
discount-couponDiscount coupon
volume-discountVolume discount
giftGift
gift-certificateGift certificate
generic-itemNon-specific item
product-setProduct set
product-set-itemProduct set item
depositDeposit

Sorting of products in category

ValueDescription
defaultDefault
most-sellingMost selling first
cheapestCheapest first
most-expensiveMost expensive first
oldestOldest first
newestNewest first
alphabeticallyAlphabetically
alphabetically-descAlphabetically, descending
product-codePer product code
product-code-descPer product code, descending
category-priorityCategory priority
category-priority-descCategory priority, descending

Webhook event types

ValueDescriptionIdentifier meaning
brand:createBrand creation eventString (code) - brand unique code
brand:updateBrand change eventString (code) - brand unique code
brand:deleteBrand deleting eventString (code) - brand unique code
creditNote:createCredit note creation eventNumber (code) of credit note
creditNote:deleteCredit note deleting eventNumber (code) of credit note
creditNote:updateCredit note change eventNumber (code) of credit note
customer:createNew customer was createdCustomer GUID
customer:updateCustomer was updated. Throws 409 Conflict when try to register simultaneously with customer:disableOrders or customer:enableOrdersCustomer GUID
customer:disableOrdersAn event disabled the customer, and his future orders will be automatically cancelled. Throws 409 Conflict when try to register simultaneously with customer:updateCustomer GUID
customer:enableOrdersAn event enabled the customer's future orders. Throws 409 Conflict when try to register simultaneously with customer:updateCustomer GUID
customer:importImport of 1 and more customers was executedFixed string "customers"
customer:deleteCustomer was deletedCustomer GUID
deliveryNote:createDelivery note creation eventNumber (code) of delivery note
deliveryNote:deleteDelivery note deleting eventNumber (code) of delivery note
deliveryNote:updateDelivery note change eventNumber (code) of delivery note
discountCoupon:createDiscount coupon creating eventString (code) - discount coupon unique code
discountCoupon:deleteDiscount coupon deleting eventString (code) of discount coupon
discountCoupon:updateDiscount coupon updating eventString (code) - discount coupon unique code
eshop:currenciesCurrencies settings change eventID of eshop
eshop:billingInformationBilling information (i.e. eshop billing address) change eventID of eshop
eshop:designDesign settings (template, colors, fonts, layout)ID of eshop
eshop:mandatoryFieldsMandatory fields of customer were updatedID of eshop
eshop:projectDomainDomain of eshop was changedID of eshop
invoice:createInvoice creation eventNumber (code) of invoice
invoice:deleteInvoice deleting eventNumber (code) of invoice
invoice:updateInvoice change eventNumber (code) of invoice
job:finishedThe asynchronous request was finishedJob id
mailingListEmail:createE-mail addition event into the e-mail distribution listName (code) of e-mail distribution list
mailingListEmail:deleteE-mail deleting event from the e-mail distribution listName (code) of e-mail distribution
order:cancelOrder cancel event. Webhook is emitted when order status is set to canceled. Throws 409 Conflict when try to register simultaneously with order:updateNumber (code) of order
order:createOrder creation eventNumber (code) of order
order:deleteOrder deleting eventNumber (code) of order
order:updateOrder change event. Throws 409 Conflict when try to register simultaneously with order:cancelNumber (code) of order
orderStatusesList:changeOrder status list change event. Emitted when order status is created, updated or deletedOrder status ID
paymentMethod:changePayment method change eventPayment method GUID
proformaInvoice:createProforma invoice creation eventNumber (code) of proforma invoice
proformaInvoice:deleteProforma invoice deleting eventNumber (code) of proforma invoice
proformaInvoice:updateProforma invoice change eventNumber (code) of proforma invoice
proofPayment:createProof of payment creation eventNumber (code) of proof payment
proofPayment:deleteProof of payment deleting eventNumber (code) of proof payment
proofPayment:updateProof of payment change eventNumber (code) of proof payment
shippingMethod:changeShipping method change eventShipping method GUID
shippingRequest:cancelledShipping request was not chosen for order deliveryshippingRequestCode associated with the cart
shippingRequest:confirmedShipping request was chosen for order deliveryshippingRequestCode associated with the cart
stock:movementStock change eventStock ID
stock:inStock (*)Stock change event - sum across all of the stocks raised above 0 (beta, see below)Number (code) of product
stock:soldOut (*)Stock change event - sum across all of the stocks reached 0 (beta, see below)Number (code) of product
stock:minStockSupplyReached (*)Stock change event - sum across all of the stocks reached minimum stock supply value, if this limit is set for product (beta, see below)Number (code) of product

(*) These webhooks are considered beta/experimental, for more information, please visit the X-url

Mass Webhooks

These webhooks are sent when a mass change of entities is performed. The payload contains a json serialized list of IDs of changed entities.

Purpose of these webhooks is to downgrade number of requests, while i.e. administrator performs mass change of orders status at once etc.

So instead of emitting one event for every order, we emit one event for all of them.

For now, if some mass event is performed, we also sent "single" webhook event for every updated entity as usual, but it will be changed in future, so please watch release changes for more info

ValueDescriptionIdentifier meaning
discountCoupon:massCreateMass create of discount coupons eventJson serialized list of string (code) of discount coupons
discountCoupon:massDeleteMass delete of discount coupons eventJson serialized list of string (code) of discount coupons
invoice:massUpdateMass change of invoices eventJson serialized list of number (code) of invoices
order:massUpdateMass change of orders eventJson serialized list of number (code) of orders

System Webhooks

These webhooks cannot be registered via API, they are setup in Partners' Addon administration section instead.

ValueDescription
addon:suspendThe addon was suspended by the eshop or by Shoptet operations staff
addon:approveThe addon was approved (resumed) after it was suspended
addon:terminateThe addon was terminated by the eshop or by Shoptet operations staff
addon:uninstallThe addon was uninstalled by the eshop admin or the eshop was terminated

URL address from endpoint Eshop info

See endpoint Eshop info

IdentDescription
admin-orders-listListing of orders in administration
admin-customers-listList of customers in administration
oauthOAuth server address, used for e-shop user verification

List of product catalogues

Provider (identification)Description
glamiGlami
googleGoogle
heurekaHeuréka
zboziZboží.cz

Invoice Billing Methods

idDescription
1COD (cz: Dobírka)
2Wire transfer (cz: Převodem)
3Cash (cz: Hotově)
4Card (cz: Kartou)

VAT modes

Value
Normal
One Stop Shop
Mini One Stop Shop
Reverse charge
Outside the EU

Postman collection

If you use Postman as an API platform for building and using APIs, we provide you a complex collection of Shoptet API.

You have 2 options how to import our postman collection (created from openApi schema - openapi.yaml ) into your postman client

Fork Shoptet API Collection from Shoptet Public API Workspace (recommended)

Also check postman documentation for more details: Fork a collection.

Step 1: Navigate to Shoptet Public API Workspace

  • Launch Postman on your desktop or in the browser.

  • In the search bar in the top header of app, type Shoptet Public API and select collection from Shoptet public API Workspace.

Step 2: Locate the Shoptet API Collection

  • Once inside the Shoptet Public API Workspace, go to the Collections tab.

  • Find the Shoptet API collection.

Step 3: Fork the Collection

  • Click on the Shoptet API collection to open it.

  • In the collection view, click the Fork button in the top-right corner.

  • In the fork dialog, choose a name for your forked collection.

  • Select the workspace where you want to save the forked collection.

  • It’s recommended to check watch original collection to get notified about changes in the original collection.

  • Click Fork Collection.

Step 4: Access Your Forked Collection

  • Navigate to the workspace where you saved the forked collection.

  • You’ll now find the forked Shoptet API collection under the Collections tab, ready for you to use and modify.

Now you have your own copy of the Shoptet API collection! If you want to add changes from the original collection, you can do so by click on pull changes in collection settings.

Import openapi.yaml into Postman as a Collection

Step 1: Upload the openapi.yaml File

  • Download the openapi.yaml file from our developers repository.

  • Launch Postman on your desktop or in the browser.

  • In the top-left corner of Postman, click the Import button.

  • A pop-up window will appear.

  • Drag and drop your openapi.yaml file into the window, or click Upload Files and browse to the file's location.

Step 2: Verify OpenAPI Import

  • Postman will automatically recognize the OpenAPI schema.

  • It will display a preview of the API schema.

Step 3: Import as Collection

  • Once the file is recognized, click Import.

  • Postman will convert the OpenAPI schema into a collection of requests, based on the defined endpoints in the openapi.yaml file.

Step 4: Access the Imported Collection

  • After the import is successful, go to the Collections tab.

  • You’ll find your new collection, named after the OpenAPI schema, containing all the API requests generated from the file.

Now you can explore the API endpoints and use them directly within Postman!

Collection settings

  1. Click the Shoptet API collection name.

  2. Go to Authorization tab.

  3. Set your access token into the value of Shoptet-Access-Token key.

  4. Go to Variables tab.

  5. You can set baseUrl variable here.

Last changes

Last API changes are published on the [API news] page (https://developers.shoptet.com/category/api/).

Download OpenAPI description
Languages
Servers
https://api.myshoptet.com/

Eshop

This endpoint is used for general information about the e-shop settings.

Operations

Products

Product endpoints are used for managing products in the e-shop and also for its related modules.

Operations

Price lists

Price lists are used for setting up different prices for products for different customer groups.

Operations

Orders

Order endpoints are used for managing orders in the e-shop.

Operations

List of orders

Request

List of orders in e-shop and cash desks. Endpoint supports pagination. For default calls, it returns 20 orders,

using the parameter ?itemsPerPage=100, you can request up to 100 orders at a time. Temporarily disabled, only 20 orders per page is supported. We apologize for the inconvenience.

The list can be filtered according to status, transport, payment, date of creation, order number and customer number.

The code (code) is the order identifier. Although this is usually a number, it is necessary to take into account that this might also include

letters, dash, etc.

Query
statusIdstring

Purchase order filtering, according to order status id.

shippingGuidstring

Purchase order filtering, according to forwarder GUID.

shippingCompanyCodestring

Purchase order filtering, according to forwarder company code.

paymentMethodGuidstring

Purchase order filtering, according to payment method.

creationTimeFromstring

Purchase order filtering, according to date of creation. ISO 8601 format ("2017-12-12T22:08:01+0100").

creationTimeTostring

Purchase order filtering, according to date of creation. ISO 8601 format ("2017-12-12T22:08:01+0100").

codeFromstring

Purchase order filtering, according to order code.

codeTostring

Purchase order filtering, according to order code.

customerGuidstring

Purchase order filtering, according to customer number.

emailstring

Purchase order filtering, according to customer e-mail. The accurate match is searched for, regardless of capitalization.

phonestring

Purchase order filtering, according to customer phone. International format only (+420123456789)

productCodestring

Order filter by product's code that is in order.

changeTimeFromstring

Purchase order filtering, according to date of last update. ISO 8601 format ("2017-12-12T22:08:01+0100").

changeTimeTostring

Purchase order filtering, according to date of last update. ISO 8601 format ("2017-12-12T22:08:01+0100").

sourceIdstring

Order source filtering according to source id. For more information, see List of order sources endpoint.

Headers
Content-Typestringrequired
Default application/vnd.shoptet.v1.0
curl -i -X GET \
  'https://api.myshoptet.com/api/orders?changeTimeFrom=string&changeTimeTo=string&codeFrom=string&codeTo=string&creationTimeFrom=string&creationTimeTo=string&customerGuid=string&email=string&paymentMethodGuid=string&phone=string&productCode=string&shippingCompanyCode=string&shippingGuid=string&sourceId=string&statusId=string' \
  -H 'Content-Type: application/vnd.shoptet.v1.0' \
  -H 'Shoptet-Access-Token: YOUR_API_KEY_HERE'

Responses

OK

Bodyapplication/vnd.shoptet.v1.0+json; charset=utf-8
dataobjectrequired
data.​ordersArray of objectsrequired
data.​orders[].​codestringrequired

order number. Caution! This does not have to be just a number, it can also contain letters, a dash, etc.

data.​orders[].​guidstringrequired

global unique permanent order identifier (can be null for old orders)

data.​orders[].​creationTimestring or null(typeDateTime)^[0-9]{4}-[01][0-9]-[0123][0-9]T[012][0-9]:[0...required

date and time, when the order was created. ISO 8601 format.

data.​orders[].​changeTimestring or null(typeDateTime)^[0-9]{4}-[01][0-9]-[0123][0-9]T[012][0-9]:[0...required

date and time of the order's last change. ISO 8601 format.

data.​orders[].​fullNamestring or nullrequired

customer full name (can be null)

data.​orders[].​companystring or nullrequired

company name (can be null)

data.​orders[].​emailstring or nullrequired

purchaser e-mail (can be null)

data.​orders[].​phonestring or null

purchaser phone number (can be null)

data.​orders[].​remarkstring or nullrequired

customer remark (can be null).

data.​orders[].​customerGuidstring(typeGuidUnlimited)<= 36 charactersrequired

customer identifier, if the customer is registered in the e-shop (can be null)

data.​orders[].​cashDeskOrderbooleanrequired

flag, whether the order is from the cash desk (as opposed to the e-shop)

data.​orders[].​adminUrlstringrequired

URL to administration leading to order detail. URL keeps the administration language settings.

data.​orders[].​statusobject or nullrequired
data.​orders[].​status.​namestring or nullrequired

status name

data.​orders[].​status.​idnumberrequired

status identifier

data.​orders[].​sourceobject or null
data.​orders[].​shippingobject(shipping)required
data.​orders[].​shipping.​guidstring(typeGuid)<= 36 characters^[0-9a-f]{8}-([0-9a-f]{4}-){3}[0-9a-f]{12}$required

transport type identifier

data.​orders[].​shipping.​namestringrequired

description of transport method (Czech post, PPL, in person..)

data.​orders[].​paymentMethodobject(paymentMethod)required
data.​orders[].​paymentMethod.​guidstring(typeGuid)<= 36 characters^[0-9a-f]{8}-([0-9a-f]{4}-){3}[0-9a-f]{12}$required

payment method identifier (can be null)

data.​orders[].​paymentMethod.​namestringrequired

description of payment method

data.​orders[].​priceobject(price)required

price of the order

data.​orders[].​price.​vatstring or null(typePrice)^(-)?[0-9]+\.[0-9]{2}$required

VAT value, two decimal places

data.​orders[].​price.​toPaystring or null(typePrice)^(-)?[0-9]+\.[0-9]{2}$required

total price to pay

data.​orders[].​price.​currencyCodestring(typeCurrencyCode)^[a-zA-Z]{3}$required

currency code. List of available currencies within the e-shop can be found in endpoint GET /api/eshop.

data.​orders[].​price.​withoutVatstring or null(typePrice)^(-)?[0-9]+\.[0-9]{2}$required

price excluding tax

data.​orders[].​price.​withVatstring or null(typePrice)^(-)?[0-9]+\.[0-9]{2}$required

price including tax

data.​orders[].​price.​exchangeRatestring(typeExchangeRate)^[0-9]+\.[0-9]{8}$required

currency rate of the receipt for the default currency of the shop. This value is saved together with the price and reflects the historical value valid in the instant of the order creation. If the shop changes the default currency, the value still refers to the original currency!

data.​orders[].​price.​partialPaymentAmountstring or null(typePrice)^(-)?[0-9]+\.[0-9]{2}$

can be value expressed in percents or as exact money value expression (with up to two decimal places) - depends on partialPaymentType value

data.​orders[].​price.​partialPaymentTypestring

'percents' = partial payment as percentage from total price | 'absolute' = exact expression of partial payment in money

data.​orders[].​paidboolean or nullrequired

flag, whether the order was paid. In addition to true a false, can also be null, if the payment status is unknown.

data.​paginatorobject(paginator)required
data.​paginator.​totalCountintegerrequired

total number of available records

data.​paginator.​pageintegerrequired

current page

data.​paginator.​pageCountintegerrequired

total available of pages

data.​paginator.​itemsOnPageintegerrequired

number of currently returned records

data.​paginator.​itemsPerPageintegerrequired

required number of records per page

errorsArray of objects or null(Errors)required
errors[].​errorCodestringrequired

Short text error identification

errors[].​messagestringrequired

Descriptive error message

errors[].​instancestringrequired

Identification of the entity referenced

Response
application/vnd.shoptet.v1.0+json; charset=utf-8
{ "data": { "orders": [], "paginator": {} }, "errors": [ {} ] }

Order insertion

Request

This endpoint enables insert the order into Shoptet, which was created in other system. You can use it for an import

from an older e-shop solution, or to transfer orders from external sales channels.

A large amount of info can be set, but for regular usage only a few attributes are needed. Values of other

attributes are added as per their default values. The detailed information can be found in the right pane, after

clicking on title "Order insertion" above (search for "Request" and "Attributes” sections).

Request is sent in JSON format in its body. Simple example (detailed example can be found in call example in right pane):


{
    "data": {
        "email": "foo@bar.cz",
        "externalCode": "123",
        "paymentMethodGuid": "6f2c8e36-3faf-11e2-a723-705ab6a2ba75",
        "shippingGuid": "8921cdc1-051b-11e5-a8d3-ac162d8a2454",
        "billingAddress": {
            "fullName": "Jan Novák",
            "street": "Rovná",
            "city": "Rovina",
            "zip": "12300"
        },
        "currency": {
            "code": "CZK"
        },
        "items": [
            {
                "itemType": "product",
                "code": "32/ZEL",
                "vatRate": "21.00",
                "itemPriceWithVat": "121.00"
            },
            {
                "itemType": "billing",
                "name": "Platba převodem",
                "vatRate": "21.00",
                "itemPriceWithVat": "0"
            },
            {
                "itemType": "shipping",
                "name": "PPL",
                "vatRate": "21.00",
                "itemPriceWithVat": "59.00"
            }
        ]
    }
}

Whether the field is mandatory, apart from the basic definition, also depends on whether the order was created via the cash desk

(cashDeskOrder: true) or via e-shop. Some fields from invoicing, delivery and contact data

are mandatory or optional, as per e-shop settings (see also e-shop administration Settings > Customers > Mandatory fields).

When the order is created, it is checked, whether the e-shop includes products with the respective code (can be suppressed with

GET parameter suppressProductChecking=true),

the products from the order are deducted from the stock (can be suppressed with the GET parameter suppressStockMovements=true), documentation is created for the order (can be suppressed with the GET parameter suppressDocumentGeneration=true), a confirmation e-mail is sent (can be suppressed with the GET parameter suppressEmailSending=true) and a webhook is executed for the new order.

**Parameters suppressProductChecking=true and suppressStockMovements=true are to be used only for orders that will not be changed or deleted in the future.

Editing or deleting such an order can damage the consistency of warehousing.**

Parameter suppressHistoricalMandatoryFields=true can be used to disable mandatory fields checks, but only for "historical"

orders (creationTime is older than 24 hours). Keep in mind even historical orders should be kept consistent and complete

as much as possible to allow their processing for statistics, volume calculations etc.

Setting the mandatory items for invoicing and the delivery address can be different between individual e-shops. The mandatory items corresponds to the settings

for ordering from the basket.

Parameters suppressHistoricalPaymentChecking and suppressHistoricalShippingChecking allow corresponding field (paymentMethodGuid and/or shippingGuid)

to be null. In that case, if an billing/shipping item is provided in items list, name field must be filled in that item.

To remove products from the stock, the shop (or product) setting as to whether the inventory can be negative or not is respected.

If a negative value is not permitted for shopping and the order cannot be covered from the current inventory, the order is not created and the API

returns an error message in the errors field.

The order's minimum size or maximum number of items as per the settings of e-shop are not checked.

The endpoint only checks the same parameters as the order detail.

The order can be inserted while using currencies setup in the eshop (see /api/eshop). The exchange rate related to the

eshop default currency is optional. If not provided, the current eshop exchange rate will be used.

For historical orders the exchange rate should be provided using the historical value of the order's creation date.

Shoptet eshops do not store historical exchange rates.

Warning: for SK and CZ different exchange rate format is used. You should use the same form as you get from the endpoint

/api/eshop. We will internally convert it to the correct format to be compatible with eshop statistics calculations.

Because of the conversion, the value of exchangeRate in the response will be different (inverse) to the one you had sent.

When entering the order, the initial welcome e-mail is always sent. Even though the order status is set differently to the initial value,

the e-mail associated with a status change is not sent, but the system welcome e-mail is (to e-shop operator and customer).

When creating the receipt (invoice, proforma invoice, delivery note) the receipt is created with the current date and the 14 days due date, even though

creationTime is given from the past.

Examples of how to work with the order and items statuses, and how to ensure the correct insertion of a discount, can be found in a

separate article at developers.shoptet.com

After the order is successfully created, you will receive a response with a 201 code and a response structure matching the order detail,

which is returned by /api/orders/<code> endpoint.

Please note following rules

  • code .. maxLength 10 characters

  • email .. maxLength 100 characters

  • phone .. maxLength 32 characters

  • externalCode .. maxLength 255 characters

  • billingAddress.company .. maxLength 100 characters

  • billingAddress.fullName .. maxLength 100 characters

  • billingAddress.street .. maxLength 100 characters

  • billingAddress.houseNumber .. maxLength 16 characters

  • billingAddress.city .. maxLength 100 characters

  • billingAddress.district .. maxLength 64 characters

  • billingAddress.additional .. maxLength 64 characters

  • billingAddress.zip .. maxLength 100 characters

  • billingAddress.regionName .. maxLength 128 characters

  • billingAddress.regionShortcut .. maxLength 16 characters

  • billingAddress.companyId .. maxLength 18 characters

  • billingAddress.vatId .. maxLength 16 characters

  • billingAddress.taxId .. maxLength 16 characters

  • deliveryAddress.company .. maxLength 255 characters

  • deliveryAddress.fullName .. maxLength 64 characters

  • deliveryAddress.street .. maxLength 100 characters

  • deliveryAddress.houseNumber .. maxLength 16 characters

  • deliveryAddress.city .. maxLength 100 characters

  • deliveryAddress.district .. maxLength 64 characters

  • deliveryAddress.additional .. maxLength 64 characters

  • deliveryAddress.zip .. maxLength 100 characters

  • deliveryAddress.regionName .. maxLength 128 characters

  • deliveryAddress.regionShortcut .. maxLength 16 characters

  • notes.trackingNumber .. maxLength 32 characters

  • items.name .. maxLength 250 characters

  • items.variantName .. maxLength 128 characters

  • items.brand .. maxLength 64 characters

  • items.supplierName .. maxLength 255 characters

  • items.code .. maxLength 64 characters

  • items.additionalField .. maxLength 255 characters

  • items.amountUnit .. maxLength 16 characters

Query
suppressDocumentGenerationstring

suppress the generation of linked documents.

Default "false"
Example: suppressDocumentGeneration=true
suppressEmailSendingstring

suppress sending the linked information e-mails.

Default "false"
Example: suppressEmailSending=true
suppressProductCheckingstring

suppress the product existence check as per code and GUID

Default "false"
Example: suppressProductChecking=true
suppressStockMovementsstring

suppress deduction of the products from stock

Default "false"
Example: suppressStockMovements=true
suppressHistoricalMandatoryFieldsstring

set the flag that disables mandatory fields checking

Default "false"
Example: suppressHistoricalMandatoryFields=true
suppressHistoricalPaymentCheckingstring

set the flag that paymentMethodGuid can be null

Default "false"
Example: suppressHistoricalPaymentChecking=true
suppressHistoricalShippingCheckingstring

set the flag that shippingGuid can be null

Default "false"
Example: suppressHistoricalShippingChecking=true
Headers
Content-Typestringrequired
Default application/vnd.shoptet.v1.0
Bodyapplication/vnd.shoptet.v1.0+json
dataobjectrequired
data.​creationTimestring

time of order creation. Optional, current time is the default value.

data.​codestring[ 1 .. 10 ] characters

Unique identifier for an e-shop order. Caution! This does not have to be just a number, it can also contain letters, a dash, etc.

data.​languagestringnon-empty

Language of order. Default: default eshop language. (optional)

data.​externalCodestring[ 1 .. 255 ] charactersrequired

order identification within the external system (mandatory, must be unique).

data.​cashDeskOrderboolean

flag, if the order was created via the cash desk. Optional. false is the default value.

data.​statusIdnumber

Order status. Optional. If not indicated, the default status of the order is used, as per e-shop settings. If the status definition sets the payment flag, the parameter paid is set to true. if the request also mentions paid, the paid variant has priority. If the status definition has selected the setting of item statuses, the status is also set for items. Otherwise, the initial status is the set based on e-shop defaults. If the item has status set explicitly (see below items[].statusId), the value from the item shall be used.

data.​sourceIdnumber or null

Order source id. Optional. If not indicated, no source will be used (null). If sourceId is positive, cashDeskOnly must also be set to true, otherwise if sourceId is negative, cashDeskOnly must be set to false, otherwise error will be returned. Current possible values of sourceId can be determined by calling the list of order sources endpoint.

data.​emailstring[ 1 .. 100 ] characters

customer e-mail (can be omitted only when ordering via cash desk).

data.​phonestring or null[ 1 .. 32 ] characters

phone number of the customer. Optional, if not set as mandatory item in shop settings.