> For the complete documentation index, see [llms.txt](https://docs.tiny.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tiny.plus/api/endpoints/capability-statements.md).

# Capability statements

{% hint style="warning" %}
Submission packs are invite only for now, so these requests answer only for accounts we've invited; [`/me`](https://docs.tiny.plus/api/endpoints/me.md#integrations) carries `integrations.submissions`.
{% endhint %}

A capability statement is the firm's approved account of what it does, written for a sector or a client: its `audience`, an optional `audience_company`, and the `body`. Submission packs draw on the approved ones, and the AI draft of a pack's statement starts from the nearest approved one. They come with submission packs, a Pro plan feature an account admin turns on under Account Settings → Submissions.

Capability statements live at `/v2/capability_statements`. They support every request on the [Records](https://docs.tiny.plus/api/endpoints/records.md) page: list, get, history, create, update, delete and search.

## Who sees a statement

Records admins and anyone with the Submissions role read and change every statement; the person who made one owns it. To everyone else a statement is read as its owner allows, as for any record whose type is for its owners.

## Approval

`record_status` is `draft` or `approved`. Only a records admin or someone with the Submissions role can move a statement to `approved`; the change stamps `approved_by` (the team member) and `approved_date`. Changing the `body` of an approved statement puts it back to `draft` and clears the stamp, unless the person changing it could approve it, in which case it stays approved under their name. Only approved statements go into a pack.

| Case                                                    | Response                                                                                                                                           |
| ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| `record_status: approved` from someone without the role | `400 {"error": "A processing error occurred while adding this record."}` on a create; the update saves nothing and answers as a failed write does. |

## Creating a statement

```bash
curl -X POST "https://api.tiny.plus/v2/capability_statements" \
  -H "Authorization: Bearer {{user_access_token}}" \
  -H "Content-Type: application/json" \
  -d '{
        "name": "Health",
        "audience": "Public health clients",
        "body": "We have delivered hospital and aged care work for twenty years...",
        "record_status": "draft"
      }'
```

```javascript
{
    "id": "219202"
}
```
