Skip to main content
This page covers the data formats and conventions used across all Swoogo API requests and responses.

​
IDs

All resource identifiers (event_id, registrant_id, session_id, etc.) must be transmitted as integer values.

​
Date and time

Timestamps follow the ISO 8601 standard:

​
Time zones

Time zone values must use one of the zone identifiers the API supports. United States zones use POSIX-style names (e.g., US/Eastern, US/Central, US/Mountain, US/Pacific, US/Alaska, US/Arizona), while most other zones use region/city names (e.g., Europe/London, Europe/Paris, Asia/Tokyo, Australia/Sydney, America/Los_Angeles, America/Mexico_City). UTC is also accepted.
Timezone abbreviations (e.g., EST, EDT, PST, CET) are not accepted. Some IANA identifiers are also not accepted — most notably America/New_York, which must be submitted as US/Eastern.

​
Currencies

Currency values use the ISO 4217 three-letter format (e.g., USD, EUR, GBP). See the full list of ISO 4217 currency codes.

​
Addresses

  • Countries — Use ISO 3166 Alpha-2 codes (e.g., US, GB, DE, AU)
  • States and provinces — Use standard 2-character abbreviations (e.g., CA, NY, ON)

​
Boolean values

Booleans are formatted differently in requests vs. responses.

​
Phone numbers

The API uses E.164 format — the international standard that includes the country code without spaces or special characters.
If the E.164 format isn’t provided, the system attempts to assign a country code automatically, but accuracy is not guaranteed. Always include the country code prefix.

​
Expand parameter

Certain GET endpoints support the expand parameter to include related objects in the response. Pass a comma-separated list of singular object type names:
Using expand caps the maximum page size at 200 items per page.