Error Codes

Picsart uses conventional HTTP response codes to indicate the success or failure of an API request.

Error Code	Message	Description
200	Success	Congratulations, your call was successful. This code indicates that the API request was successfully processed by the server.
400	Bad request	The server could not understand the request due to invalid syntax or input parameters that did not meet the requirements. This error commonly occurs when the request contains incorrect or missing parameters. Developers should carefully review the request and ensure it follows the correct API format and includes all mandatory parameters.
401	Unauthorized	Although the HTTP standard specifies "unauthorized," semantically, this response means "unauthenticated." That is, the client must authenticate itself to get the requested response. Check if the APIKEY is provided in either the request header or in the query string. Developers must verify if the API key is provided in either the request header or the query string. If the key is missing or invalid, the server will reject the request with this error code.
402	Payment Required	Payment required. It indicates that the client must make a payment to access the requested resource, either because all pre-purchased credits have been used up or because the client has reached a subscription limit without an enabled overdraft option.
403	Forbidden	The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401, the client's identity is known to the server. Developers should review the permissions associated with the user or API key making the request to ensure it has sufficient privileges to access the requested resource.
404	Not Found	Not found. Verify that the request URL is spelled correctly and that the API you are trying to access exists. For example, ensure that you are not trying to access the wrong revision of an API. If the requested resource does not exist, the server will respond with this error code. Developers should double-check the URL and API version being used in the request.
405	Method Not Allowed	Method not allowed. You specified a method that is not supported. For example, you used the GET verb for an API call that requires the POST verb. Developers should review the allowed methods for each API endpoint and ensure they use the correct HTTP verb in their request.
406	Not Acceptable	The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request. Currently when a call is made to Picsart Creative APIs, services don't require the client to accept application/json responses which is the standard output format for our services. Even if Accept header is not provided or the specified value doesn't include the application/json value, Picsart Creative APIs will still ignore that and process the request gracefully. Nevertheless, Picsart recommends always providing Accept: application/json and intends to make it required. If not provided, Picsart will interpret this as the client is really and actually not able to process JSON responses and will not process the request.
413	Request Entity Too Large	Request Entity Too Large. This error occurs when the size of the request exceeds the server's limit. Developers should optimize the payload size or use chunked transfer encoding for large payloads to avoid this error. The maximum file size supported is published on Input and Output Formats document.
415	Unsupported Media Type	The media format of the requested data is not supported by the server, so the server rejects the request. Typically, this error occurs on POST or PUT requests when the Content-type HTTP header is set to the wrong value. For example, an HTTP 415 error is returned if you POST the following to an API that only supports JSON: $ curl https://api.picsart.io/tools/demo/upscale -X POST -H "Content-type:text/xml" -d '' For GET requests, use the Accept header instead of the Content-type header.
422	Unprocessable Content	Unprocessable Content response status code indicates that the server understands the content type of the request entity, and the syntax of the request entity is correct, but it was unable to process the contained instructions. This is primarily used when the input parameters are validated against the defined requirements and those are not met. For example, it can be a case when output format is defined as TIFF when it's not supported on Picsart Creative APIs or when the provided input image URL points to a 404 Not Found resources or meets a 429 Too Many Requests.
429	Too Many Request	The rate limit was exceeded on the Quota. This error indicates that the client has made too many requests in a given time period, exceeding the allowed quota. Developers should review their API usage patterns and adhere to the rate limits defined by Picsart to avoid this error.
431	Request Header Fields Too Large	Request header fields too large. This error occurs when the size of the request headers exceeds the server's limit. Developers should review and optimize the headers to fit within the server's capacity.
500	Internal Server Error	The server encountered an unexpected condition that prevented it from fulfilling the request. If the error persists, check the service status at status.picsart.io to verify if there are any ongoing issues or maintenance. If the problem persists, developers can reach out for further assistance using the provided contact details.
503	Service Unavailable	The service is temporarily unavailable. Check the current status at status.picsart.io to determine if there are any ongoing maintenance or temporary outages. If the service remains unavailable, developers may need to wait until the issue is resolved, or they can contact Picsart's technical support for further assistance.

For high error rates, you can check the service status at status.picsart.io to get updates and subscribe for notifications, including upcoming maintenance. In case you don’t see the problem escalated on the Status page, please contact us with a Request type of ‘Troubleshooting’ or send a direct email to [email protected]. The support team will promptly follow up and assist in resolving the problem.