1. REST API for Oracle MICROS Simphony Configuration and ContentConfiguration and Content API Guide
  2. Introduction
  3. Oracle Food and Beverage API Design Standards
  4. Multiple response formats

Multiple response formats

FBGBU APIs support multiple response formats in some rare cases, in addition to application/json. In this case:

All supported response formats will be advertised (for example included in an array in the "produces" section of the relevant path in a Swagger specification).

To request a given response format the client must send that format in the "Accept" HTTP header (see RFC7231).

The API will supply only the format requested by the client in the "Accepts" HTTP header.

If the path supports multiple response formats and the API prefers one format over another, this will be specified using the "q" parameter (inbuilt into HTTP as "content type negotiation" per RFC7231).