We recommend transmitting all date and time information in all requests to the RetailForce middleware in compliance with ISO 8601. The time and date information returned by the RetailForce middleware in the responses also corresponds to this format.
Exceptions
- fiscalDocumentStartTime - Unix Time Stamp
Format
| Variable | Format | Value | Description |
| Y | YYYY | 0000...9999 | Year |
| M | MM | 01...12 | Month |
| D | DD | 01...31 | Day of the month |
| h | hh | 00...24 | Hour |
| m | mm | 00...59 | Minute |
| s | ss | 00...60 | Second, (60 only as a leap second) |
| f | f | (0...9)+ | decimal fractions, usually of seconds of any accuracy (optional) |
Separator
| Separator | Description |
| T | Separator between date and time specification |
| - | Separator of date elements (hyphen) |
| : | Separator of time elements (colon) |
| . | Separator of integers and decimal fraction (dot) - between "s" and "f" |
| + | Time zone specification - positive offset to UTC (plus sign) |
| - | Time zone specification - negative offset to UTC (minus sign) |
Example:
"createDate": "2023-11-15T17:27:12.46+01:00"
| Example | Description |
| 2023-11-15T17:27:12.46+01:00 | 17:27:12.46 on 15th of November 2023 in the time zone CET (Central European Time) |
| 2023-07-15T17:27:12.46+02:00 | 17:27:12.46 on 15th of July 2023 in the time zone CEST (Central European Summer Time) |
Error handling
Known problems in connection with date/time specifications.
Comments
0 comments
Please sign in to leave a comment.