Getting Started Overview¶
The first step is requesting access from the A2Z team. After access is approved, use the path that matches your use case.
1) Request Access From A2Z¶
Request the following onboarding values from the A2Z/Personify team:
client_idclient_secret- Whitelisted OIDC
redirect_uri X-Tenant-Idvalue for API callsEventIdfor the event(s) your application will access- Environment URLs (production/stage as applicable)
Also tell A2Z which API service domains you need (for example: Exhibitor, Event, Company, Financial, Floorplan, Conference) so access can be granted to the correct services.
See REST API > Swagger Links for the current service list.
2) Choose Your Use Case¶
SSO/OIDC (Exhibitor SSO)¶
Use this when an exhibitor needs to SSO from Event Portal into your application.
Typical outcomes:
- User is authenticated and returned to your app via
redirect_uri - Your app can retrieve user claims (
id_tokenand/or UserInfo) stateis used to restore event/session context
Start here:
Standard API Access (Server-to-server)¶
Use this when your backend service needs data from A2Z APIs without end-user login.
Typical outcomes:
- Obtain bearer token using OAuth 2.0
client_credentials - Call APIs with required headers (
Authorization,X-Tenant-Id) - Use pagination conventions consistently
Start here:
See Authentication > API Authentication.
Suggested Implementation Sequence¶
- Request access and receive onboarding values from A2Z.
- Configure OIDC
redirect_uriand validate login callback behavior. - Implement API auth with
client_credentials. - Call target APIs with
AuthorizationandX-Tenant-Id. - Add exhibitor lookup and user selection handling where needed.
Environment Placeholders¶
- IdP authorize endpoint:
https://prod.personifyauth.com/connect/authorize - IdP token endpoint:
https://prod.personifyauth.com/connect/token - IdP UserInfo endpoint:
https://prod.personifyauth.com/connect/userinfo - API base URL:
https://api-stage.psfye.net