Data Formats and Transport Protocol

Transport Protocol

The only available transport protocol of the Pricefx backend is HTTP(S). Standard HTTP headers and return codes as defined in RFC 2616 are used. The Pricefx API entirely relies on a defined URL scheme and additional data as part of a standard HTTP POST request. If no request body is required, HTTP GET can be used too (unless stated otherwise).

Data Format

The payload of the HTTP requests and responses are formatted in JSON by default.

JSON is described in RFC 4627 and at json.org.

attention

The JSON request should be properly identified by HTTP Header Content-Type set to application/json.

Encoding

All strings are UTF-8 encoded.

TLS Versions

Pricefx servers use following TLS protocol versions:

  • TLS 1.2
  • TLS 1.3