Complete browser sign-in
const url = 'http://127.0.0.1:8080/api/v1/auth/example/callback?state=example&code=example';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'http://127.0.0.1:8080/api/v1/auth/example/callback?state=example&code=example'Available only when account authentication is enabled. Provider configuration is restart-bound. Local logout does not require an external provider. Responses must not be cached.
Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Query Parameters
Section titled “Query Parameters”Responses
Section titled “Responses”Successful sign-in creates an ordinary secure session and opens account settings, or the library home for a managed provider. A sign-in or link started at the native entry instead redirects to its return target with code and state, or with error (access_denied or authentication_failed) and state, and sets no browser session. A link code changes nothing until finish-native-provider-link confirms it.
Structured authentication boundary failure
object
Examplegenerated
{ "code": "example", "detail": "example", "status": 1, "title": "example", "type": "example"}Structured authentication boundary failure
object
Examplegenerated
{ "code": "example", "detail": "example", "status": 1, "title": "example", "type": "example"}Structured authentication boundary failure
object
Examplegenerated
{ "code": "example", "detail": "example", "status": 1, "title": "example", "type": "example"}Structured authentication boundary failure
object
Examplegenerated
{ "code": "example", "detail": "example", "status": 1, "title": "example", "type": "example"}Structured authentication boundary failure
object
Examplegenerated
{ "code": "example", "detail": "example", "status": 1, "title": "example", "type": "example"}