Integration Rules and Conventions

These rules apply to every integration method — Open API V2, Open API V3, and native connectors. They are not API-version-specific.

Accepted image formats

All endpoints and integration methods that accept image uploads or image URLs support the following formats only:

image/png
image/jpeg

Other formats (GIF, BMP, WebP, SVG) are not accepted and will be silently ignored or rejected.

Accepted account statuses

When setting or updating a participant's status, the following values are accepted:

REGISTERED
ACTIVE
INVITED
UPLOADED

External IDs

Participant accounts and exhibitor profiles support an external_id field. Setting an External ID on creation allows future operations to target the same record without knowing the internal platform ID — useful for syncing data from an external system of record (CRM, registration platform, etc.).

External IDs are stored at the environment level. They are unique per entity type within the environment.

The `send_email` parameter

The send_email=true parameter (available when creating or updating accounts and exhibitors) triggers a credentials email on every request it is included in — not only on record creation.

Do not hardcode this parameter in sync scripts, loops, or recurring integration jobs. Only include it when you explicitly intend to trigger an email for a specific operation. Accidental mass-emailing is the most common integration incident and is not reversible.

This applies to both API calls and native connector configurations that expose a "send welcome email" option.