> ## Documentation Index > Fetch the complete documentation index at: https://docs.licensesearcher.com/llms.txt > Use this file to discover all available pages before exploring further. # Errors > How the LicenseSearcher API signals success and failure. LicenseSearcher uses conventional HTTP response codes to indicate the success or failure of an API request. * Codes in the `2xx` range indicate success. * Codes in the `4xx` range indicate an error caused by the request (for example, a missing parameter or an out-of-scope state). * Codes in the `5xx` range indicate an error with LicenseSearcher's servers. ## HTTP status codes | Code | Status | Meaning | | ----------- | ----------------- | -------------------------------------------------------------------------------------------------------- | | `200` | OK | Everything worked as expected. | | `400` | Bad Request | The request could not be accepted, often because a required parameter is missing. | | `401` | Unauthorized | No valid API key was provided. | | `403` | Forbidden | Your API key does not have permission to access this resource (for example, a state it isn't scoped to). | | `404` | Not Found | The requested resource does not exist, or the state isn't supported. | | `429` | Too Many Requests | Too many requests hit the API too quickly. Try again later. | | `500`–`504` | Server Errors | Something went wrong on LicenseSearcher's side. | Requests that return a `4xx` status code are billed to your account. See [Authentication](/authentication#billing-and-security) for details.