# GET /api/v1/inboxes/:id/security-check

Auth: Bearer

HTML: https://cooperemail.com/docs/reference/security-check

## Summary

Grade one agent inbox against ten launch checks in one call. The response is inbox_id, address, checked_at, summary counts, and checks. status is pass, warn, fail, or info. info means Cooper does not store that control, and the detail says so. The checks are key scope, inbound screening, allowed senders, send limits, webhook signing, human approval, monthly send cap and Idempotency-Key, domain reputation, tenant isolation, and the event log. The result lists key id, key prefix, and webhook ids. It does not return the API key, the key hash, or a webhook signing value. An inbox-scoped key can grade only its own inbox. Another account is HTTP 404 inbox_not_found. No key is HTTP 401 unauthorized. Requires inbox_read. MCP: cooper_security_check. inbox_id is optional when the key is limited to one inbox. Example: curl https://cooperemail.com/api/v1/inboxes/inb_example/security-check -H "Authorization: Bearer $COOPER_API_KEY".

## Request

This call has no JSON body.

## Response

HTTP 200. Sample values illustrate the schema.

```json
{
  "inbox_id": "inb_example",
  "address": "ada@example.com",
  "checked_at": "2026-10-18T12:00:00.000Z",
  "summary": {
    "pass": 1,
    "warn": 1,
    "fail": 1,
    "info": 1,
    "total": 1
  },
  "checks": [
    {
      "id": "inb_example",
      "title": "string",
      "status": "pass",
      "detail": "string"
    }
  ]
}
```

## Errors

- HTTP 404 inbox_not_found
- HTTP 403 permission_denied

The live `message` is the sentence for that code. Branch on `code`.

```json
{
  "error": {
    "type": "not_found",
    "code": "inbox_not_found",
    "docs_url": "https://cooperemail.com/docs#inbox_not_found"
  }
}
```

## Idempotency

Idempotency-Key is 1 to 256 characters of letters, digits, and - . _ ~. The same key and the same request within 24 hours returns the original response with HTTP 200 and Idempotent-Replayed: true. A different request is HTTP 409 idempotency_key_conflict. A second call while the first is running is HTTP 409 idempotency_request_in_progress. An empty or invalid key is HTTP 400 invalid_idempotency_key. A definitive refusal removes the key. An ambiguous failure keeps it and the same request returns HTTP 409 idempotency_outcome_unknown. client_id is checked first when both are set. Done keys expire after 24 hours. Unknown keys are kept for 7 days.
