# POST /api/v1/regent-slack/intake-triage

> Triage a forwarded contract or invoice and post an interactive Slack card

- **Tag:** regent-slack
- **Operation ID:** `regent_slack_send_intake_triage_card`

## Description

Evaluates duplicate bill risk, multi-month prepaid amortization, 1099/W-9 compliance, and Smart Pay working-capital float, then posts an interactive Slack Block Kit card with 1-click actions.

## Authentication

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

## Request body

Schema: `RegentSlackIntakeTriageRequest`

- `channel` (string · required) — Slack channel or DM ID to post the intake triage card to
- `vendor_name` (string · required)
- `amount_cents` (integer · required) — Total bill or contract amount in cents
- `description` (string) — Invoice or contract description
- `due_date` (string) — Optional due date (YYYY-MM-DD)
- `service_months` (integer) — Contract service duration in months (>1 triggers prepaid amortization preview)
- `bill_number` (string)
- `has_w9_on_file` (boolean) — Override W-9 status; auto-detected from vendor tax_id when omitted

## Responses

### 201 — Successful Response

Schema: `SuccessEnvelope_RegentSlackIntakeTriageResult_`

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

### 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/regent-slack/intake-triage' \
  -H 'Authorization: Bearer dz_your_token' \
  -H 'x-business-id: YOUR_BUSINESS_ID' \
  -H 'Content-Type: application/json' \
  -d '{
  "channel": "string",
  "vendor_name": "string",
  "amount_cents": 0
}'
```

### JavaScript

```javascript
const response = await fetch('https://api.ondayzero.com/api/v1/regent-slack/intake-triage', {
  method: 'POST',
  headers: {
    Authorization: 'Bearer dz_your_token',
    'x-business-id': 'YOUR_BUSINESS_ID',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "channel": "string",
  "vendor_name": "string",
  "amount_cents": 0
}),
});
const data = await response.json();
```

### Python

```python
import httpx

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

payload = {'channel': 'string', 'vendor_name': 'string', 'amount_cents': 0}

response = httpx.post("https://api.ondayzero.com/api/v1/regent-slack/intake-triage", headers=headers, json=payload)
data = response.json()
```

## See also

- HTML version: https://www.ondayzero.com/docs/reference/regent-slack/regent-slack-send-intake-triage-card
- OpenAPI slice: https://www.ondayzero.com/docs/reference/regent-slack/regent-slack-send-intake-triage-card/openapi.json
- Other endpoints in **regent-slack**: https://www.ondayzero.com/docs/reference/regent-slack (markdown bundle: https://www.ondayzero.com/docs/reference/regent-slack.md, OpenAPI: https://www.ondayzero.com/docs/reference/regent-slack/openapi.json)
- Endpoint catalog: https://www.ondayzero.com/docs/reference/index.md