Go back to Partigi API Documentation

HTTP Status Codes

The Partigi API attempts to return appropriate HTTP status codes for every request.

• 200 OK: Your request was a successful!
• 400 Bad Request: The request was invalid.  An accompanying error message will explain why. 
• 401 Not Authorized: The request hasn't the necessary credentials. Refer to our Authentication page.
• 404 Not Found: The URI requested is invalid or the resource requested does not exists.
• 406 Not Acceptable: The format of the request is not acceptable. Please, use only the formats allowed for each method.
• 500 Internal Server Error: There is an error in the application. Please, notice us about it and we will fix it as soon as possible.
• 502 Bad Gateway: Partigi is having a massage.
• 503 Service Unavailable: Partigi is over capacity.

Error Messages

Partigi API always show errors in plain text format, showing the name of the exception raised during the request:

Partigi::BadAPIRequestParams

Exceptions

Invalid OAuth Request

The request is trying to access a protected resource and has not been authenticated successfully. Refer to our Authentication page for more information.

Invalid OAuth-Readonly Request

The request hasn't been signed correctly. Remember that all API request has to be signed now. Refer to our Authentication page for more information.

BadAPIRequestRequiredParams

The request hasn't all the required parameters. You can check all required parameters in the Partigi API Documentation page.

BadAPIRequestParams

The format of the parameters is invalid. You can check the allowed parameters in the Partigi API Documentation page.

BadAPIRequestMethod

The HTTP method is not the right one. You can check the valid HTTP methods in the Partigi API Documentation page.

BadAPIFriendshipSource

The source of the Frienship is invalid or doesn't exist

BadAPIFriendshipTarget

The target of the Frienship is invalid or doesn't exist

Go back to Partigi API Documentation