POST Verify Identity / Re-Login

Re-verify and refresh the saved login for an existing identity. Wire re-runs the catalog's login wheel and refreshes the stored session cookies in place. Works for all identity types:

• Vault-sourced credential — omit params (or send {}). The engine re-reads the login fields from the bound vault entry.
• Manually-entered credential (Plaid-style, no bound source) — send the catalog's login params. There is nothing to re-resolve, so the fields are required.

This is the same endpoint the dashboard Re-verify action uses, for both kinds of credential.

The password is never stored. Only the issued session cookies are persisted, encrypted. When the cookies expire (see expires_at), call this endpoint again to mint fresh ones.

It behaves like POST /v1/wire/login, but targets a known identity_id instead of finding-or-creating an identity.

Request Body

{
  "identity_id": "7c3f1a2b-4d5e-6f7a-8b9c-0d1e2f3a4b5c",
  "params": {
    "username": "alice@example.com",
    "password": "..."
  }
}

Response

{
  "status": "verified",
  "credential": {
    "id": "11111111-2222-3333-4444-555555555555",
    "identity_id": "7c3f1a2b-4d5e-6f7a-8b9c-0d1e2f3a4b5c",
    "credential_type": "credentials",
    "status": "active",
    "source_id": "f1e2d3c4-0000-0000-0000-000000000000",
    "source_ref": {
      "entry": { "container": "abcd1234", "key": "wxyz5678" }
    },
    "expires_at": "2026-06-09T10:00:00Z",
    "metadata": {},
    "created_at": "2026-06-08T10:00:00Z",
    "updated_at": "2026-06-08T10:00:00Z"
  }
}

source_id and source_ref appear only for vault-sourced credentials; they are omitted for manually-entered ones.

Error Responses

All errors return JSON of the form { "status": "error", "error": { "code": "...", "message": "..." } }. The wheel's raw error text is never echoed; only the typed code is surfaced.

Validation / setup — request rejected before the wheel runs:

Source resolution — only when re-reading a vault-bound credential, before the wheel runs:

Wheel ran (HTTP 200, status: "error") — the request was well-formed and the wheel ran, but sign-in didn't complete. Treat any status != "verified" as failure.

HTTP 200 with status: "error" is used for "the request was well-formed and the wheel ran, but the sign-in itself didn't complete." Treat any status != "verified" as failure regardless of HTTP code.

Code Examples

# (a) vault-sourced credential — no params; fields re-read from the bound entry
curl https://api.anakin.io/v1/wire/credentials/verify \
  -X POST \
  -H "X-API-Key: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{ "identity_id": "7c3f1a2b-4d5e-6f7a-8b9c-0d1e2f3a4b5c" }'

# (b) manual credential — send the catalog's login params
curl https://api.anakin.io/v1/wire/credentials/verify \
  -X POST \
  -H "X-API-Key: your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "identity_id": "7c3f1a2b-4d5e-6f7a-8b9c-0d1e2f3a4b5c",
    "params": {
      "username": "alice@example.com",
      "password": "your_password"
    }
  }'

import requests

response = requests.post(
    'https://api.anakin.io/v1/wire/credentials/verify',
    headers={'X-API-Key': 'your_api_key'},
    json={
        'identity_id': '7c3f1a2b-4d5e-6f7a-8b9c-0d1e2f3a4b5c',
        'params': {
            'username': 'alice@example.com',
            'password': 'your_password',
        },
    },
)

data = response.json()
if data['status'] == 'verified':
    credential_id = data['credential']['id']
    # Use credential_id with /v1/wire/task
else:
    print(f"Verify failed: {data['error']['code']} — {data['error']['message']}")

const response = await fetch('https://api.anakin.io/v1/wire/credentials/verify', {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    identity_id: '7c3f1a2b-4d5e-6f7a-8b9c-0d1e2f3a4b5c',
    params: {
      username: 'alice@example.com',
      password: 'your_password',
    },
  }),
});

const data = await response.json();
if (data.status === 'verified') {
  const credentialId = data.credential.id;
  // Use credentialId with /v1/wire/task
} else {
  console.error(`Verify failed: ${data.error.code} — ${data.error.message}`);
}

Rate limit

10 requests per minute per user (each call runs a real sign-in against the target site).

Related

• GET /v1/wire/identities — list identities + credentials
• POST /v1/wire/login — single-call find-or-create credentials login
• POST /v1/wire/login — Create Identity / Login (password or vault locator)
• POST /v1/wire/task — use the returned credential.id to run an authenticated action
• Identity sources overview — the whole flow, connect through bind