Leap JSON Introduction

Introduction

Leap JSON is a specification that dictates how a client should request resources and how a server should respond to the request.

Leap JSON requires use the Leap JSON media-type application/vnd.leap+json for exchanging data.

Conventions

The keywords “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.

Client Responsibilities

• Clients MUST send all Leap JSON data in request documents with the header Content-Type: application/vnd.leap+json without any media-type parameters.
• Clients that include the Leap JSON content type in their Accept header MUST specify the media type there at least once without any media type parameters.
• Clients MUST ignore any parameters for the application/vnd.leap+json media type received in the Content-Type header of Response documents.

Server Responsibilities

• Servers MUST send all Leap JSON data in the response documents with the header Content-Type: application/vnd.leap+json without any media type parameters.
• Servers MUST respond with a 415 Unsupported Media Type status code if a request specifies the Content-Type along with any media type parameters.