# API response\_code NOT\_FOUND

**Error Description**

Customers may encounter an API response indicating NotFound. This response typically appears as:

```xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
  <response xmlns="....." response_code="NOT_FOUND" generated_at="2023-05-25T09:52:49+00:00">
    <message>No data for the event: sr:match:41345021:prematch</message>
  </response
```

**Applies to**

UOF SDK - All

**Symptoms**

When utilizing Sport Event or Market methods, if the result is not cached within the SDK, it triggers a call to the appropriate API endpoint. Due to the nature of the API, these requests may occasionally fail. If the HTTP status code received is NOT\_FOUND, it may indicate either an incorrect request ID or that the API service is temporarily unable to provide the expected results. Such cases are reflected in the REST logs via response\_code with the value NOT\_FOUND. Depending on the exception handling strategy employed, users may receive an exception in the calling code.

**Resolution**

1. Verify the validity of the request (e.g., correct match ID, competitor ID, etc.).
2. Retry the request later on (no throttling for failed requests); sometimes, this error may be due to a temporary API issue.
3. For non-critical data, implementing a retry strategy in a separate thread invoked at a later time is recommended.

<br>