Amplify Shared Services Save PDF Selected topic Selected topic and subtopics All content Miscellaneous 1 minute read Miscellaneous commonly used formats. Common Date and Time Format for Responses All date-time instances in responses share the same format, as per RFC 3339. Format: date-time, with time-offset utilizing the time-numoffset definition. Example: 2020-03-11T08:38:11.000+0000. Common Date Format for Responses All date instances in responses share the same format, as per profile of ISO 8601 at RFC 3339. Format: full-date utilizing the date-fullyear "-" date-month "-" date-mday definition. Example: 2024-05-21. Common Date and Time Format for Requests All date-time instances in requests need to adhere to the following format, as per RFC 3339. Format: date-time, with time-offset set to Z. Example: 2020-03-01T01:02:03Z. Last modified March 18, 2022: Deleted or moved the description summary text from the front matter (#33) (142bf2a) Related Links
Miscellaneous 1 minute read Miscellaneous commonly used formats. Common Date and Time Format for Responses All date-time instances in responses share the same format, as per RFC 3339. Format: date-time, with time-offset utilizing the time-numoffset definition. Example: 2020-03-11T08:38:11.000+0000. Common Date Format for Responses All date instances in responses share the same format, as per profile of ISO 8601 at RFC 3339. Format: full-date utilizing the date-fullyear "-" date-month "-" date-mday definition. Example: 2024-05-21. Common Date and Time Format for Requests All date-time instances in requests need to adhere to the following format, as per RFC 3339. Format: date-time, with time-offset set to Z. Example: 2020-03-01T01:02:03Z. Last modified March 18, 2022: Deleted or moved the description summary text from the front matter (#33) (142bf2a)