Importer: Date Formatting

Teena Blaydes -

Formatting dates may be a little confusing because the system assumes UTC time, unless another timezone is specified.

When using dates or date/times in the API or a CSV, please provide them in one of the following formats:
  • yyyy-mm-dd
    • Example: 2016-11-01

  • yyyy-mm-ddThh:mm:ss 
    • Example: 2016-11-01T12:00:00
      • Remember that this assumes UTC time, so if you're in an eastern timezone, you would see this as 8am. (There's a -4:00 offset)

  • yyyy-mm-ddThh:mm:ss offset (where timezone offset is either + or -, and hh:mm)
    • Example: 2016-11-01T12:00:00-04:00
      • This would show as 12:00pm in the system (if in Eastern) 


  • For most imports, you would use only the date format
  • For imports such as appointments, you may use the date-only format BUT:
    • The time defaults to 00:00
    • When translated from UTC, the appointment will appear to have happened the day before
      • Example: 2016-11-01
        • This will show as: 2016-10-31 at 8:00PM (if in Eastern)

We formatted dates with the time for appointments (or notes)! Why is it not working?

The date/time formatting must be formatted precisely in order for it to take. If only the date is formatted correctly, it won't process any data after that.

  • 2016-11-01T12:00:00-04:00 - Works
  • 2016-11-01 12:00 -400 - Will not work
  • 11/1/2016T12:00:00-04:00 - Will not work (and should result in a "Date must be included" error, depending on the type of import)





Was this article helpful?
3 out of 5 found this helpful
Have more questions? Submit a request