Content Types

Content Types

Content Type definitions MUST be RFC 6838-compliant. Types are registered in the IANA list of official media types. Types are further restricted to the following:

content-type	Reference
application/json	RFC 8259
application/json-patch+json	RFC 6902
image/heic	Intentionally blank
image/jpeg	RFC 2045, RFC 2046
image/png	Intentionally blank
multipart/form-data	RFC 2045, RFC 7578

Data Types

The type designators listed below are used in descriptions throughout the Specification, but the relevant RFC or other linked documentation should be consulted for the type's formalized details where not described in this document.

Additional restrictions or requirements associated with the types are listed in dedicated sections below.

Name	Type	Description
array	array	RFC 7159-compliant sequence of values
boolean	boolean	RFC 7159-compliant value (true or false)
date	string	ISO 8601 date without a time part. More details
dateTime	string	ISO 8601 date-time with optional UTC time offset. More details
integer	number	RFC 7159-compliant number value without a fraction or exponent part
number	number	RFC 7159-compliant number value
object	object	RFC 7159-compliant collection of name/value pairs
string	string	RFC 7159-compliant string literal value
uri	string	RFC 3986-compliant URI
uuid	string	Unique ID

Date

• SHOULD be formatted as: yyyy-MM-dd
• Date values are inclusive. That is, startDate and endDate in Special Hours, for example, includes the provided date.
• Value MAY be captured as dateTime (with or without time zone designators). However, only calendar date will be respected.

Occurrences
locationDetails.locationStatus.closedDate
locationDetails.locationStatus.reopenDate
locationDetails.specialHours[].endDate
locationDetails.specialHours[].startDate
showcaseDetails.endDate
showcaseDetails.startDate

Example

2026-12-01

Date-Time

• Offset part MAY be replaced by Z to denote UTC.
• Input data MAY include a decimal fraction added to the lowest order time element using the format: Thh:mm:ss.sss
• Milliseconds precision SHOULD NOT be greater than three (3) digits.
• All system calculated timestamps will include a decimal fraction.
• All system calculated timestamps will:
  • Include decimal fraction.
  • Exclude offset part. Offset will be replaced by Z to denote UTC.

Example

2026-12-01T17:22:19.00Z