This flow is for partners who need a trusted mapping between an AGG
user.id and their own
internal user ID for rewards, analytics, or reconciliation. The assertion must come from your
backend, not from the browser.How it works
Generate the app secret
Generate or rotate the app secret from the AGG admin dashboard, then store it in your backend
secrets manager. Never expose it to the browser.
Sign the assertion on your backend
Build an HMAC over
{externalId}:{timestamp} using the app secret. This proves the assertion
came from your backend.Send the assertion to the frontend
Return
{ externalId, timestamp, hmac } from your own API after the user is authenticated in
your app.Webhook-assisted linking
If your backend needs to connect new AGG users to existing partner users, subscribe toaccounts.created. The event includes the AGG userId and, when available from magic-link or
OAuth sign-in, email.
Use that email to resolve your internal user record, then complete the normal signed assertion flow
for that authenticated user. After client.linkExternalId(assertion) succeeds, AGG emits
accounts.linked with the AGG userId and your externalId.
accounts.created.data.email is null when AGG does not have an email for the principal, such
as wallet-only sign-in or OAuth providers that do not return email.Examples
Backend signing
- Node.js
- Python
Frontend linking
- SDK
- Hooks
externalId is returned on the updated UserProfile and on future
client.getCurrentUser() calls.