# POST /api/v1/agents/staff/logins

> Save a login (superuser)

- **Tag:** agents
- **Operation ID:** `agents_staff_logins_create`

## Description

Save a username and password (and optionally a two-factor setup key) for one exact host. The same owner, host and username (any case) replaces the saved one. AGENT_022 for an address that is not a website, AGENT_023 for a two-factor key that cannot be read. Superusers only.

## Authentication

Bearer token in `Authorization` header.
Required header: `x-business-id: <business uuid>`.

## Parameters

- `business_id` (query, string, optional) — The business whose logins these are
- `firm_id` (query, string, optional) — The advisory firm whose logins these are

## Request body

Schema: `LoginCreate`

- `scope` (string) (one of: business, firm)
- `host` (string · required) — Host or URL of the sign-in page; stored as its exact host.
- `username` (string)
- `password` (string · required)
- `totp` (string) — Two-factor setup key (base32) or otpauth:// link.
- `label` (string)
- `role_ids` (array · string) — Roles that may use it; null = every role.

## Responses

### 201 — Successful Response

Schema: `SuccessEnvelope_LoginOut_`

- `success` (boolean)
- `message` (string)
- `code` (string)
- `data` (LoginOut)

### 400 — Bad Request - Invalid input

Schema: `ErrorResponse`

- `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`.
- `message` (string · required) — Human-readable explanation, safe to show to end users.
- `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`).
- `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied.
- `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

### 401 — Unauthorized - Missing or expired token, an MCP OAuth token used against the REST API, or no access to this business

Schema: `ErrorResponse`

- `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`.
- `message` (string · required) — Human-readable explanation, safe to show to end users.
- `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`).
- `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied.
- `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

### 403 — Forbidden - Insufficient permissions

Schema: `ErrorResponse`

- `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`.
- `message` (string · required) — Human-readable explanation, safe to show to end users.
- `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`).
- `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied.
- `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

### 422 — Validation Error

Schema: `ErrorResponse`

- `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`.
- `message` (string · required) — Human-readable explanation, safe to show to end users.
- `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`).
- `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied.
- `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

## Code samples

### cURL

```bash
curl -X POST 'https://api.ondayzero.com/api/v1/agents/staff/logins' \
  -H 'Authorization: Bearer dz_your_token' \
  -H 'x-business-id: YOUR_BUSINESS_ID' \
  -H 'Content-Type: application/json' \
  -d '{
  "host": "string",
  "password": "string"
}'
```

### JavaScript

```javascript
const response = await fetch('https://api.ondayzero.com/api/v1/agents/staff/logins', {
  method: 'POST',
  headers: {
    Authorization: 'Bearer dz_your_token',
    'x-business-id': 'YOUR_BUSINESS_ID',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "host": "string",
  "password": "string"
}),
});
const data = await response.json();
```

### Python

```python
import httpx

headers = {
    "Authorization": "Bearer dz_your_token",
    "x-business-id": "YOUR_BUSINESS_ID",
}

payload = {'host': 'string', 'password': 'string'}

response = httpx.post("https://api.ondayzero.com/api/v1/agents/staff/logins", headers=headers, json=payload)
data = response.json()
```

## See also

- HTML version: https://www.ondayzero.com/docs/reference/agents/agents-staff-logins-create
- OpenAPI slice: https://www.ondayzero.com/docs/reference/agents/agents-staff-logins-create/openapi.json
- Other endpoints in **agents**: https://www.ondayzero.com/docs/reference/agents (markdown bundle: https://www.ondayzero.com/docs/reference/agents.md, OpenAPI: https://www.ondayzero.com/docs/reference/agents/openapi.json)
- Endpoint catalog: https://www.ondayzero.com/docs/reference/index.md