# Create definitions key rows rowId debt-schedules scheduleId issue

Issue a business debt schedule: the revision named in the body becomes the one that stands, so it can be sent out and quoted against. Use it when the schedule is final, not while it is being filled in.

Access class: `def:read`.

## Endpoint

`POST /v1/definitions/{key}/rows/{rowId}/debt-schedules/{scheduleId}/issue`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| key | path | string | Yes |
| rowId | path | string | Yes |
| scheduleId | path | string | Yes |

## Request body

Content type: `application/json`.

```json
{
  "body": {
    "revision": 1.5
  },
  "params": {
    ":key": "string",
    ":rowId": "",
    ":scheduleId": ""
  },
  "query": {}
}
```

## Responses

### 201

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "content": "string",
    "created_at": "string",
    "document_id": "",
    "id": "",
    "revision": 1,
    "source": "string",
    "source_detail": "string",
    "status": "string"
  }
}
```

### default

a refusal: `{"error": "<what a person needs to read>"}`. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.

Content type: `application/json`.

```json
{
  "error": "string"
}
```