Resolve a user_code to its verification-page details
Ceremony
Resolve a user_code to its verification-page details
What the signed-in human sees on the verification page before approving: the connector name, the target agent, the consent type, and any bound resource/scope. Requires the human’s Nevermined API key (unauthenticated → BCK.OAUTH.0007) — it is the browser verification-page surface, not the polling device.
POST
Resolve a user_code to its verification-page details
Authorizations
A Nevermined API key: Authorization: Bearer <sandbox:… | live:…>. Environment-prefixed, not a bare JWT — send the whole string.
Body
application/json
Example:
"BCDF-GHJK"
Response
Verification details
Example:
"LangSmith Fleet"
Example:
"did:nv:agent-123"
Example:
"My Weather Agent"
Available options:
credits_purchase, account_access Example:
"credits_purchase"
Example:
"https://api.nevermined.app"
Example:
"openid"
Related topics
FAQAPI VersioningAPI error codesFastAPIProvision an account for the organization (member or customer)