# Paid ticket endpoint

`identifier` - this could be either ticket id or ticket code.

Will set ticket status to `open`.

Response status codes:

<table><thead><tr><th width="150">Status Code</th><th>Interpretation</th></tr></thead><tbody><tr><td>200</td><td>OK - Everything worked as expected</td></tr><tr><td>400</td><td>Bad Request. Please check error code in response body (see <a data-mention href="/pages/1INgng7U9kxpIeKAfEVj">/pages/1INgng7U9kxpIeKAfEVj</a>)</td></tr><tr><td>403</td><td>Forbidden. You do not have access for such request</td></tr></tbody></table>

Error response (status=400):

```json
{
    "code": 100,
    "message": "{feature} feature not implemented yet"
}
```

Error response (status=400):

```json
{
    "code": 102,
    "message": "Ticket with `{ticket-id}` identifier is not found"
}
```

Error response (status=400):

```json
{
    "code": 117,
    "message": "Ticket has to have `reserved` status in order to do this action"
}
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.betstack.io/bet-engine-api/paid-ticket-endpoint.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.