Get Started with Pricing API

Read through the following information to integrate our web browser REST API:

Authentication

The Pricing API does not require authentication.

Header Values

The most relevant REST request header values for our Pricing API are the following:

Field Name	Description	Example Values	Required
`Accept`	Format of the function call response that is desired.	`application/json` or `application/xml`	Yes
`Accept-Language`	Contact's language preferences, in order of priority.	`fr-CH, fr;q=0.9, en;q=0.8, de;q=0.7, *;q=0.5`	No

In this example, the requested resource is a json object and the preferred languages are Swiss French, French, English, and German, respectively:

curl --request GET \
  --url 'https://pricingapi.cleverbridge.com/prices?client_id=864&product_id=97772&internalproduct_id=&currency=USD&country=US&coupon=BD3-1KK-UN3&price_rule=' \
  --header 'accept: application/json' \
  --header 'accept-language: fr-CH, fr;q=0.9, en;q=0.8, de;q=0.7, *;q=0.5'

Status Codes

All Cleverbridge REST-based APIs use conventional HTTP response codes.

Status Code	Description
200	Successful completion of the call.
400	Bad Request (incomplete message, required fields missing, incorrectly formatted XML/JSON).
401	Unauthorized Request. Authentication with Cleverbridge failed (ID/password issue). Not applicable to Pricing API.
402	Request failed: Invalid parameters.
404	Not Found: The other unique identifier set and passed in the call is invalid or does not exist (the subscription ID, for example).
429	Too Many Requests: Rate limit reached.
500	Request failed due to server error on the Cleverbridge side.

Rate Limits

The Cleverbridge platform limits you to a maximum of 30 requests per second from an IP address or range.

All API requests count towards the rate limit. For more details, see Rate Limits in Get Started for REST APIs.