Overview of standards used by the Tradecloud API
Your integration must support these standards.
The Basic HTTP authentication scheme, which transmits credentials as user-id/password pairs, encoded using Base64.
The Hypertext Transfer Protocol is a stateless application-level protocol for distributed, collaborative, hypertext information systems.
The JSON syntax does not assign any significance to the ordering of name/value pairs.
Therefor XML based transformations expecting ordering will break.
JSON Web Tokens are an open, industry standard RFC 7519 method for representing claims securely between two parties.
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.
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.
Transport Layer Security is a cryptographic protocol designed to provide communications security over a computer network.
A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource.
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.
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