Tradecloud API v2 manual
1.0.0
Search…
⌃K

Standards

Overview of standards used by the Tradecloud API
Your integration must support these standards.

Basic HTTP authentication

The Basic HTTP authentication scheme, which transmits credentials as user-id/password pairs, encoded using Base64.
Published as RFC 7617

HTTP 1.1 and 2.0

The Hypertext Transfer Protocol is a stateless application-level protocol for distributed, collaborative, hypertext information systems.
HTTP 1.1. is published as RFC 7230 and RFC 7231 to 7237.
HTTP 2.0 is published as RFC 7540

ISO Date/Time

Date/time values use ISO 8601 date format YYYY-MM-DD or local date/time format YYYY-MM-DDThh:mm:ss
Published as ISO 8601-1:2019

JSON

JavaScript Object Notation is a lightweight, text-based, language-independent data interchange format.
Published as RFC 8259 and ECMA-404 (PDF)
The JSON syntax does not assign any significance to the ordering of name/value pairs.
Therefor XML based transformations expecting ordering will break.

JWT

JSON Web Tokens are an open, industry standard RFC 7519 method for representing claims securely between two parties.

Media Types

Tradecloud supports a sub set of the RFC 6838 Media Type Specifications.

OpenAPI

The OpenAPI Version 2.0 Specification (OAS 2.0) creates a RESTful interface for easily developing and consuming an API by effectively mapping all the resources and operations associated with it.

REST

Representational state transfer (REST) is not a standard but a software architectural style that defines a set of constraints to be used for creating Web services. The Tradecloud API additionally uses a command and query style.

TLS v1.2

Transport Layer Security is a cryptographic protocol designed to provide communications security over a computer network.
The Tradecloud API only supports TLS v1.2 published as RFC 5246.

URI

A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource.
Published as RFC 3986 with errata.
URLs can only be sent over the Internet using the ASCII character-set.
Since URLs often contain characters outside the ASCII set, the URL has to be converted into a valid ASCII format. URL encoding replaces unsafe ASCII characters with a "%" followed by two hexadecimal digits. URLs cannot contain spaces. URL encoding normally replaces a space with a plus (+) sign or with %20.

UTF-8

ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8
Published as RFC 9259