> For the complete documentation index, see [llms.txt](https://developer.betstack.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.betstack.io/bet-engine-api/error-codes.md).

# Error codes

Full list of error codes for 400 response status code:

<table><thead><tr><th width="135">Error Code</th><th>Interpretation</th></tr></thead><tbody><tr><td>100</td><td>{feature_name} feature not implemented yet</td></tr><tr><td>101</td><td>Error with incoming data</td></tr><tr><td>102</td><td>Ticket with {ticket-id} identifier is not found</td></tr><tr><td>103</td><td>Event with {event-id} identifier is not found</td></tr><tr><td>104</td><td>Events list in ticket object can't be empty</td></tr><tr><td>105</td><td>Team with {team-id} identifier is not found</td></tr><tr><td>106</td><td>Market for bet with {bet-id} identifier is not found</td></tr><tr><td>107</td><td>Event with {event-id} identifier is not available for play because it has already started</td></tr><tr><td>108</td><td>Bookmaker event for event with {event-id} identifier is not found</td></tr><tr><td>109</td><td>Market is blocked</td></tr><tr><td>110</td><td>Ticket odds changed</td></tr><tr><td>111</td><td>Duplicate key for code generation</td></tr><tr><td>112</td><td>Operator with {operator-name} name is not found</td></tr><tr><td>113</td><td>Error while request to PAM {action-name} action</td></tr><tr><td>114</td><td>No webhook url for operator with {operator-id} name</td></tr><tr><td>115</td><td>Operators in request body and in request header are not identical.</td></tr><tr><td>116</td><td>Market with {market-id} code is not allowed.</td></tr><tr><td>117</td><td>Ticket has to have {status} status in order to do this action.</td></tr><tr><td>118</td><td>Events list must contain at least {correct_amount} items.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://developer.betstack.io/bet-engine-api/error-codes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.