Informz uses a specific methodology for managing time and time zones in XML calls that retrieve data from our API.
All dates are stored in the Informz database with the Eastern Standard Time Zone (EST). When pulled using API, these are converted to Coordinated Universal Time (UTC).
Date fields returned from the Informz API have the following format: YYYY-MM-DDThh:mm:ss.sZ
- YYYY is the four-digit year.
- MM is the two-digit month (01 for January, etc.).
- DD is the two-digit day of the month (01 through 31).
- T represents the beginning of the clock timestamp.
- hh is the two-digit hour (00 through 23).
- mm is the two-digit minute (00 through 59).
- ss is the two-digit second (00 through 59).
- s is the decimal fraction of the second.
- Z is the UTC indicator.
For example, 19 June, 2017 at 3:46:18 pm would be: 2017-06-19T15:46:18.8130000Z
Note that UTC can offset the date between EST and GMT, depending on the time of year, because of Daylight Saving Time (UTC does not change due to Daylight Saving Time while many country's local times do). Sometimes the API returns a value four hours later than what the database has while other times it may be five.
All exceptions caught and handled by AAPI will return as a soap fault of type InformzAAPIFault. Each fault will contain a code and a reason.
- The code is a "camel case," machine readable string that represents a generic classification of the error message.
- The reason is a human-readable description that contains details of why the fault is occurring.
The following error codes may be returned.