Errors
Juice utilizes REST API and regular HTTP response codes to signify the success or failure of requests. Below, you can find some common errors and their potential causes.
200
The request was successful. The intended action was carried out. Note: For charges or verification requests, check the data object to determine the specific outcome (success or failure).
201
A new resource was successfully created.
204
No content is returned.
400
A validation or client-side error occurred, preventing the request from being fulfilled.
401
The request was unauthorized. This could be due to an invalid secret key in the authorization header or the absence of any authorization header.
403
Access Denied.
404
The requested resource could not be found except in the case where a payment session is completed.
422
Some required fields are missing.
500
The request could not be fulfilled due to an error on Juice's server. Please report any encounters with 500 errors.
Last updated