Going-Live Checklist

Use this checklist before enabling a partner integration for production facilities.

Partner Console setup

Your partner profile is complete.
Your logo URL, website, category, and description are accurate.
Your data linking method is configured: Direct Link or Linking Identifier.
Facility linking has been tested with at least one real facility.
The right key type is being used:
- Dryrun for non-destructive write testing.
- Read-only for safe data consumption.
- Live only when you are ready to affect production data.

Authentication and key management

Secret keys are stored server-side only.
Keys are not embedded in client-side applications, mobile apps, public repositories, or support tickets.
Key rotation and revocation have been tested.
Your team knows which key is used by each environment.

Data validation

Required fields are present for every endpoint you call.
Facility identifiers match your configured linking method.
IDs from your system are stable and do not change between syncs.
Large imports are split into batches under the documented limits.
Failed batch items can be identified and resent.

Endpoint testing

Before launch, test every endpoint your integration depends on:

Organisations and facilities can be read.
Members can be saved and updated.
Membership plans, access zones, and access hours sync correctly.
Check-ins are accepted and can be correlated back to your system.
Report snapshots use the expected reporting period and metrics.
Door/Gate Controller flows are tested on real hardware where applicable.

Access Time Window readiness

If the integration supplies Access Time Windows:

Absolute and weekly examples pass the producer certification checklist.
Epochs are unquoted integer Unix seconds; exact [from, to) boundaries have been tested.
UTC defaults, the integration's custom IANA timezones, and relevant daylight-saving transitions have been verified.
One durable, monotonic member/source revision stream coordinates incremental updates, reconciliation, and retries.
Operators understand omitted, complete-replacement, idempotent, conflicting, stale, and explicit-[] behavior.
Every scope_key, including default, has an approved Performance Hub mapping; unknown keys have been tested to fail closed.
The integration's expected refresh cadence, maximum source age, stale-source behavior, and alerts are configured.
An upstream fetch failure has been proven not to emit an empty or partial snapshot.
Stage stream convergence, cancellation/revocation, and physical-door start/end boundaries meet the agreed targets.
Regular rules and permanent grants have been verified as fallback paths, and windows cannot bypass user disablement, blockAllAccess, maintenance, or geofencing.

Access control readiness

For access control integrations:

Your system makes the access decision before calling Performance Hub.
The integration handles device_offline, maintenance_mode_active, and unlock_confirmation_timeout.
Operators understand that a timeout means the unlock was not confirmed.
Your logs store the returned event_id and command_id.
You have a manual fallback process for facility staff.

Error handling and retries

400, 401, 403, 404, 409, and 422 responses are surfaced to operators or support teams rather than retried blindly.
429, 500, 502, 503, and 504 responses use bounded retry logic with backoff.
Repeated failures create an alert in your system.
The integration never drops failed records silently.

Observability

Your logs include endpoint, timestamp, facility identifier, source record ID, request outcome, and response body.
Your support team can search by member ID, facility ID, check-in ID, or unlock event ID.
You have a way to replay or reconcile failed syncs.

Production launch

Performance Hub has confirmed your production access.
At least one production facility has enabled your integration.
Your production key is active.
Your operational and technical contacts are current.
Your support process is documented for customers.

After these checks are complete, your configured integration will appear in the Performance Hub partner directory inside the core Performance Hub platform.