Skip to content

Shopping APIs — page 2

88 shopping APIs for e-commerce, products and marketplaces, best documented first.

ticketmaster publish api

Shopping

Contact Us

No auth10 endpoints

Just Eat UK

Shopping

# Just Eat API Just Eat offers services for our various business partners and our consumer applications. How you interact with the API depends on the services you wish to interact with. ## Security ### HTTPS All api calls and callbacks require HTTPS. Your service will need a valid SSL certificate and be accessible via the standard SSL port (port 443). ## Making an API request Some API calls require an API key, to authenticate the partner calling the API. ``` PUT https://uk-partnerapi.just-eat.io/orders/abcd1234 HTTP/1.1 Authorization: JE-API-KEY abcd123456789 ``` Other calls require a user token in the form of a JWT. ``` GET https://uk.api.just-eat.io/consumer/me/orders/uk HTTP/1.1 Authorization: Bearer abcd123456789 ``` ## Date Formats ### Date and time formats All dates and times should use the [ISO 8601 standard for representation of dates and times](https://en.wikipedia.org/wiki/ISO_8601). #### For instance: * DueDateWithUtcOffset: `"2015-05-26T14:52:35.5444292+01:00"` - Local time: `14:52` - UTC time: `13:52` - UTC offset: `+1hr` (due to daylight time saving) * DueDateWithUtcOffset: `"2015-02-03T11:10:00.0000000+00:00"` - Local time: `11:10` - UTC time: `11:10` - UTC offset: `0` (no daylight time saving, local time is equivalent to UTC) Note that the offset may be for a timezone different to your own, so you should alway convert to your own local time for display purposes (e.g. on receipts and terminals). ### Callback timestamps Timestamps sent to Just Eat should be recorded as the current local time (including any changes needed to account for daylight saving) with an accompanying offset that shows the difference between the recorded local time and the current UTC time. If it is not possible to record timestamps in local time, timestamps may be recorded in UTC time with a 00:00 offset. ## Async Webhooks Some of the webhooks on the platform are configured as being 'async' webhooks. These are for long-running operations, and work as follows: 1. Your webhook is invoked with a `?callback={returnUrl}` query string parameter. The `returnUrl` is a unique URL that you will need to send the async response to. 2. Return an immediate `202 Accepted` response from the webhook endpoint, to indicate that you have received the request. 3. Perform the long-running operation. This can be deemed either a _success_; or a _failure_. 4. If the result is a _**success**_, return the following: ``` POST {returnUrl} HTTP/1.1 { "status": "Success", "message": "{successMessage}", "data": {} // webhook-specific response object } ``` 5. Otherwise, if the result is a _**failure**_, return the following: ``` POST {returnUrl} HTTP/1.1 { "status": "Failure", "message": "{failureMessage}", "data": {} // webhook-specific response object } ```

API key98 endpoints

Product Library API

Shopping

The Product Library API is used for managing merchant's product information and product images.

OAuth32 endpoints

Buy Marketing API

Shopping

The Marketing API retrieves eBay products based on a metric, such as Best Selling, as well as products that were also bought and also viewed.

OAuth1 endpoints

ChannelShipper & Royal Mail Public API

Shopping

Import your orders, retrieve your orders and generate labels.

API key12 endpoints

Jumpseller API

Shopping

# Endpoint Structure All URLs are in the format: ```text https://api.jumpseller.com/v1/path.json?login=XXXXXX&authtoken=storetoken ``` The path is prefixed by the API version and the URL takes as parameters the login (your store specific API login) and your authentication token. <br/><br/> *** # Version The current version of the API is **v1**. If we change the API in backward-incompatible ways, we'll increase the version number and maintain stable support for the old urls. <br/><br/> *** # Authentication The API uses a token-based authentication with a combination of a login key and an auth token. **Both parameters can be found on the left sidebar of the Account section, accessed from the main menu of your Admin Panel**. The auth token of the user can be reset on the same page. ![Store Login](/images/support/api/apilogin.png) The auth token is a **32 characters** string. If you are developing a Jumpseller App, the authentication should be done using [OAuth-2](/support/oauth-2). Please read the article [Build an App](/support/apps) for more information. <br/><br/> *** # Curl Examples To request all the products at your store, you would append the products index path to the base url to create an URL with the format: ```text https://api.jumpseller.com/v1/products.json?login=XXXXXX&authtoken=XXXXX ``` In curl, you can invoque that URL with: ```text curl -X GET "https://api.jumpseller.com/v1/products.json?login=XXXXXX&authtoken=XXXXX" ``` To create a product, you will include the JSON data and specify the MIME Type: ```text curl -X POST -d '{ "product" : {"name": "My new Product!", "price": 100} }' "https://api.jumpseller.com/v1/products.json?login=XXXXXX&authtoken=XXXXX" -H "Content-Type:application/json" ``` and to update the product identified with 123: ```text curl -X PUT -d '{ "product" : {"name": "My updated Product!", "price": 99} }' "https://api.jumpseller.com/v1/products/123.json?login=XXXXXX&authtoken=XXXXX" -H "Content-Type:application/json" ``` or delete it: ```text curl -X DELETE "https://api.jumpseller.com/v1/products/123.json?login=XXXXXX&authtoken=XXXXX" -H "Content-Type:application/json" ``` <br/><br/> *** # PHP Examples Create a new Product (POST method) ```php $url = 'https://api.jumpseller.com/v1/products.json?login=XXXXX&authtoken=XXXXX; $ch = curl_init($url); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_setopt($ch, CURLOPT_HTTPHEADER, array('Content-Type: application/json')); curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "POST"); //post method curl_setopt($ch, CURLOPT_POSTFIELDS, '{ "product" : {"name": "My updated Product!", "price": 99} }'); $result = curl_exec($ch); print_r($result); curl_close($ch); ``` <br/><br/> *** # Plain JSON only. No XML. * We only support JSON for data serialization. * Our node format has no root element. * We use snake_case to describe attribute keys (like "created_at"). * All empty value are replaced with **null** strings. * All API URLs end in .json to indicate that they accept and return JSON. * POST and PUT methods require you to explicitly state the MIME type of your request's body content as **"application/json"**. <br/><br/> *** # Rate Limit You can perform a maximum of: + 240 (two hundred forty) requests per minute and + 8 (eight) requests per second If you exceed this limit, you'll get a 403 Forbidden (Rate Limit Exceeded) response for subsequent requests. The rate limits apply by IP address and by store. This means that multiple requests on different stores are not counted towards the same rate limit. This limits are necessary to ensure resources are correctly used. Your application should be aware of this limits and retry any unsuccessful request, check the following Ruby stub: ```ruby tries = 0; max_tries = 3; begin HTTParty.send(method, uri) # perform an API call. sleep 0.5 tries += 1 rescue unless tries >= max_tries sleep 1.0 # wait the necessary time before retrying the call again. retry end end ``` Finally, you can review the Response Headers of each request: ```

No auth142 endpoints

Catalog API

Shopping

The Catalog API allows users to search for and locate an eBay catalog product that is a direct match for the product that they wish to sell. Listing against an eBay catalog product helps insure that all listings (based off of that catalog product) have complete and accurate information. In addition to helping to create high-quality listings, another benefit to the seller of using catalog information to create listings is that much of the details of the listing will be prefilled, including the listing title, the listing description, the item specifics, and a stock image for the product (if available). Sellers will not have to enter item specifics themselves, and the overall listing process is a lot faster and easier.

OAuth2 endpoints

Octopart

Shopping

Electronic part data for manufacturing, design, and sourcing

API key

Billbee API

Shopping

Documentation of the Billbee REST API to connect a Billbee account to external aplications. ## Endpoint The Billbee API endpoint base url is https://api.billbee.io/api/v1 ## Activation You have to enable the API in the settings of your Billbee account. In addition you need a Billbee API Key identifying the application you develop. To get an API key, send a mail to [email protected] and send us a short note about what you are building. ## Authorization & security Because you can access private data with the Billbee API, every request has to be sent over https and must * Contain a valid API Key identifying the application/developer. It has to be sent as the HTTP header X-Billbee-Api-Key * Contain a valid user login with billbee username and api password in form of a basic auth HTTP header ## Throttling Each endpoint has a throttle of max 2 requests per second per combination of API Key and Billbee user. When you exceed these 2 calls, the API will return a HTTP 429 status code

API key76 endpoints

Printful

Shopping

Printful's official API to manage and integrate their services

OAuth

Printify

Shopping

Printify's official API to manage and integrate their services

OAuth

Charity API

Shopping

The Charity API allows third-party developers to search for and access details on supported charitable organizations.

OAuth2 endpoints

SpectroCoin Merchant

Shopping

This is an API designed for merchants who are using SpectroCoin services and wishes to integrate them locally.

No auth1 endpoints

Shopify

Shopping

Manage sales channels, customers, products, and discounts for a retail business

OAuth

Compliance API

Shopping

Service for providing information to sellers about their listings being non-compliant, or at risk for becoming non-compliant, against eBay listing policies.

OAuth3 endpoints

FraudLabs Pro Fraud Detection

Shopping

Online payment fraud detection service. It helps merchants to minimize chargebacks and therefore maximize the revenue. It can be used to detect fraud for various kinds of payment method, such as credit card, paypal, cod and so on. Please visit https://www.fraudlabspro.com to learn more.

No auth2 endpoints

BirkinBagStock

Shopping

Independent Hermès resale index: inventory, market prices, auction calendar and results

No authCORS

Marketplace Fee Data

Shopping

Seller fee schedules for 21 e-commerce marketplaces and payment processors as JSON

No authCORS

OneFindMe

Shopping

Search AliExpress in any language: price, rating and orders for the delivery country

No authCORS

Profitvana

Shopping

Seller fees for 31 marketplaces and payment processors, verified monthly

No authCORS

BuyWhere

Shopping

Real-time product catalog API for AI agents across merchants in 7 countries (SG, MY, TH, VN, PH, ID, US)

API key

CartScout

Shopping

Price, stock, variants and GTIN from Shopify, WooCommerce, Walmart and eBay product pages

API key

Descripio Amazon Reviews

Shopping

Amazon product reviews for 12 marketplaces

API key

OpenTiendas

Shopping

Official e-commerce API and webhooks

API key

More categories