connectors
Meta's way back from its consent page, at Phase 5's address
A platform's consent page sends the browser here (design 15.0 §3.1.2).
The state is redeemed once and must come back to the person who left; the code is traded with no database session open; identity and grant are read; the login is stored (tokens sealed) and audited. The browser goes to the portal's return_to with connector and result=connected, or result=error and reason = denied, missing_permissions (stored all the same), refused or failed (a link back that does not hold among them).
get/channels/meta/callback
Request
- Base URLhttps://app.zalster.com (the document declares no server; this is the origin it was published from)
- Authnone declared
Query parameters
statestring nullable
The state the consent page was given
codestring nullable
The code to trade for a token
auth_codestring nullable
TikTok's code to trade for a token
errorstring nullable
Set when the consent page was declined
error_descriptionstring nullable
Why, in the platform's words
Changes
No recorded changes to this operation across all 1 revision of this API.