Going live

Check service configuration, access, recovery, and support before launch.

Use this checklist after your integration works against authorized test data. Make the first production request deliberately and verify its event and organization before enabling unattended imports.

Configuration and access

• Confirm the production API origin and event UUIDs.

• Put credentials in your secret manager and verify the account’s active status and organizer rights.

• Use HTTPS and exclude credentials from browser code and logs.

• Confirm that provider connections point to the intended HubSpot or Mailchimp account.

Data and recovery

• Parse the exact envelope and optional fields from the OpenAPI operation.

• Preserve UUID strings, decimal money, event currencies, and applicable timezones.

• Upsert by ID, apply deletion IDs from supported change responses, and reconcile periodically.

• Handle authentication errors, pagination endings, throttling, and transient failures.

• Recover with a full import after a missed weekly delta window.

• Check data volume against the 75,000 order and 10,000 attendee snapshot limits.

• Before retrying a write with an uncertain outcome, re-read the resource. There is no general idempotency-key contract; creations and emails can be repeated.

Visitor experience

For embedded shops, test the actual registration and payment journey on mobile and desktop. Include a direct shop link, ensure form errors remain visible, and verify confirmation and payment handoff.

Operations

Set monitoring for failed imports and unexpected drops in returned record counts. Record a sanitized request/status when an import fails. Define who can rotate credentials, change access, and contact support.

Keep a version of the OpenAPI contract with your integration and review the developer changelog when updating it.