curl --request POST \
--url https://api.anchorbrowser.io/v1/identities/{identityId}/reauthenticate \
--header 'Content-Type: application/json' \
--header 'anchor-api-key: <api-key>' \
--data '{
"sync": true
}'{
"identityId": "<string>",
"async": true,
"sessionId": "<string>",
"auth_status": "authenticated",
"method": "profile"
}{
"error": {
"code": 123,
"message": "<string>"
}
}{
"error": {
"code": 123,
"message": "<string>"
}
}{
"error": {
"code": 123,
"message": "<string>"
}
}{
"error": {
"code": 123,
"message": "<string>"
}
}{
"error": {
"code": 123,
"message": "<string>"
}
}Reauthenticate Identity
Re-authenticates an identity on demand: validates the saved browser profile and runs login if
it is no longer signed in, then persists the refreshed profile and tears the temporary session
down. Equivalent to a session with identity_skip_validation: false that ends after auth.
curl --request POST \
--url https://api.anchorbrowser.io/v1/identities/{identityId}/reauthenticate \
--header 'Content-Type: application/json' \
--header 'anchor-api-key: <api-key>' \
--data '{
"sync": true
}'{
"identityId": "<string>",
"async": true,
"sessionId": "<string>",
"auth_status": "authenticated",
"method": "profile"
}{
"error": {
"code": 123,
"message": "<string>"
}
}{
"error": {
"code": 123,
"message": "<string>"
}
}{
"error": {
"code": 123,
"message": "<string>"
}
}{
"error": {
"code": 123,
"message": "<string>"
}
}{
"error": {
"code": 123,
"message": "<string>"
}
}Authorizations
API key for your Anchor Browser account, sent as the anchor-api-key header on every
request. Create one at app.anchorbrowser.io (API Access),
or obtain one programmatically via the unauthenticated agent-access flow
(POST /v1/agent-access).
Path Parameters
The ID of the identity to reauthenticate
Body
When true (default), wait for authentication to finish and persist the refreshed
profile before returning. When false, start authentication asynchronously.
Response
Identity reauthentication started or completed
The identity that was reauthenticated
Whether authentication is still running in the background
Browser session that ran the reauthentication; its recording shows what happened
authenticated: the identity is signed in again; pending: an async run is still in progress
authenticated, pending How the identity got authenticated: profile = stored profile was still signed in, task = agentic authentication task, mixed = both. Absent while pending.
profile, task, mixed Was this page helpful?