HomeHelp & SupportAPI DocumentationOrgSearch › Response Codes

Response Codes

An example of a JSON response is shown below:

	"status":"201 Created",
	"response":"URL added"

The table below contains the response codes that OrgSearch API calls may return along with more information about them.

200 OK Everything worked correctly.
201 Created Everything worked correctly and a resource was created.
202 Accepted The request has been accepted for processing but the processing has not yet been completed.
400 Bad Request The request was unacceptable. This is often caused by a required parameter missing in the request.
403 Forbidden The API Key doesn't have permissions to access this endpoint. This is often caused by using an incorrect API Key.
404 Not Found The requested endpoint does not exist.
503 Service Unavailable The API is currently unavailable. This may be because of a technical fault or because it is undergoing maintenance.