RCS Error Codes

This document provides information about the error codes you would receive when executing the RCS REST APIs.

The following is the list of error codes for RCS:

Status Code	Message	Description
`200`	Ok	The request completed successfully.
`201`	Created	A new resource has been created successfully. The resource’s URI is available from the response’s Location header.
`204`	No Content	An update to an existing resource has been applied successfully.
`400`	Bad Request/Invalid error	The request was malformed. The response body will include an error providing further information.
`401`	Unauthorized	The request is missing or contains an invalid authorization header. Every request should include, depending on your setup, either a basic or a token-based authorization header.
`403`	Forbidden	Unauthorised Access to Resources.
`404`	Not Found	The requested resource did not exist.
`409`	Conflict (Subject already)	A request could not be completed due to a conflict with the current state of the target resource.
`413`	Message too large	The request is larger than the server is willing or able to process.
`429`	Throttling	The user has sent too many requests within a certain amount of time.
`500`	Service Unavailable	The request is not processed by RCS AGG (aggregator)/internal server error.
`501`	Not Implemented	A generic error message, given when an unexpected condition is encountered, and no more specific message is suitable.
`502`	Bad Gateway	The server was acting as a gateway or proxy and received an invalid response from the upstream server.
`503`	SERVICE_UNVAILABLE	Temporal error, try again later.
`504`	Timeout	The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.