> For the complete documentation index, see [llms.txt](https://annotationdocs.telusinternational.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://annotationdocs.telusinternational.com/error-codes/error-codes.md). # Error Codes All successful responses are returned with HTTP Status code 200. In case of failure, TELUS International API returns a JSON error response with the parameters that detail the reason for the failure with HTTP status code 400. | Error Code | Reason | | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | auth-failure | Unauthorized request. The authentication key provided is incorrect | | unauthorized | Unauthorized request. You do not have access to the requested resource. Please make sure that you have access to the project you are trying to access.se | | FS\_0001 | Reference ID for the job is already in use. Make sure the reference\_id is unique for each job. | | FS\_0002 | reference\_id is missing. Make sure to provide a unique reference\_id for a job | | FS\_0003 | Job data provided is not valid. Please check the JSON structure. | | FS\_0004 | The job data is empty. Make sure you provide the data for job creation as defined [here](/basic-operations/create-a-job.md) | | FS\_0005 | work\_flow\_id was not provided. Make sure to provide the work\_fow\_id for creating jobs | | FS\_0007 | Attachment could not be accessed or copied | | FS\_00011 | Type of the job is invalid. Make sure the type of the job is either TEST or NON\_TEST | | FS\_00012 | Job priority weight is invalid. Make sure the priority weight is in the range of 1-9 | | GE\_0001 | One or more parameter in the payload is invalid. For example, batch\_id is not a UUID | | FS\_0000 | Something went wrong on our end. Please try again after some time. | | FS\_0008 | Something went wrong on our end. Please try again after some time. | | api\_error | Something went wrong on our end. Please try again after some time. | | core.webutil.auther | Unauthorized request. You do not have access to the requested resource. Please make sure that you have access to the project you are trying to access. | | core.webutil.token\_auth | Unauthorized request. The authentication key provided is incorrect | | BATCH\_CREATION | A batch with this name already exists. Make sure to provide a unique batch name for a batch. | | invalid\_request\_error | Invalid pageToken provided, please provide the correct page\_token to access the results | | resource\_error | The resource ID provided is incorrect. Check that your requests are specifying a correct project ID, batch ID, or Job ID. | --- # 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://annotationdocs.telusinternational.com/error-codes/error-codes.md?ask=&goal= ``` `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.