HTTP Response Codes

This section outlines the common error codes and resolutions you may encounter while using the Yuno API.

Yuno uses standard HTTP response codes to indicate the success or failure of API requests.

Codes in the 2xx range usually indicate success. Codes in the 4xx range indicate an error that occurred based on the information provided (e.g., a missing parameter, etc.), and codes in the 5xx range indicate an internal error.

Example

{
  "code": "INVALID_REQUEST",
  "messages": [
    "Invalid request."
  ]
}

Response attributes for errors

code string
Attribute for error code state.

message array of strings
Error message that is returned.

See what codes are returned by Yuno's Rest API.

HTTP Status CodeCodeDescription
400 Bad RequestINVALID_REQUESTInvalid request.
INVALID_PARAMETERSInvalid parameters: list - [parameter_name].
MISSING_PARAMETERSMissing parameters: list - [parameter_name].
INVALID_STATUSInvalid transaction status.
COUNTRY_NOT_SUPPORTEDCountry not supported.
CURRENCY_NOT_ALLOWEDCurrency is not allowed for this country.
CUSTOMER_ID_DUPLICATEDThe customer id for the merchant is duplicated.
INVALID_AMOUNTInvalid amount for the payment method.
INVALID_ACCOUNT_IDInvalid Yuno's account id
INVALID_TRANSACTIONInvalid transaction id
INVALID_API_VERSIONInvalid API Version.
INVALID_TRANSACTION_TYPEInvalid transaction type for the request.
CHARGEBACK_IN_PROCESSChargeback in place for this transaction.
UNAVAILABLE_PAYMENT_METHODUnavailable payment method.
NOT_FOUNDResource not found.
UNEXPECTED_RESPONSEUnexpected service response.
BAD_REQUESTThere was a bad error executing the request.
INVALID_REPORT_IDReport id must be UUID.
INVALID_REPORT_TYPEInvalid report type.
INVALID_DATE_FORMATStart/end date format must be yyyy-MM-dd'T'HH:mm:ss.SSS'Z'.
REPORT_MAX_RANGE_ERRORMax range date is two months.
REPORT_RANGE_ERRORStart date must be before end date. Start/end date must be after now.
REPORT_STATUS_ERRORReport is not ready yet, status is %s.
REPORT_EMPTYReport requested is empty.
PAYMENT_METHOD_NOT_FOUND[For Subscriptions] - Payment method associated to the customer not found
PAYMENT_METHOD_STATUS_INVALID[For Subscriptions] - The payment method is a state that does not allow payments to be made.
INCORRECT_PAYMENT_METHOD_TYPE[For Subscriptions] - The type of payment method of the request does not correspond to the vaulted_token.
SUBSCRIPTION_NOT_FOUND[For Subscriptions] - Subscription not found.
INVALID_STATE[For Subscriptions] - The subscription state does not support the action requested.
INVALID_DATE[For Subscriptions] - The subscription can not be resume due to a conflict with the availability dates. Please update availability dates and try again if you want to keep using the subscription
INVALID_PARAMETERS[For Subscriptions] - Invalid parameters: list - [parameter_name].
INVALID_CUSTOMER_FOR_TOKENThe token used for this transaction is associated with another customer object.
401 UnauthorizedINVALID_CREDENTIALSInvalid Credentials.
EXPIRED_CREDENTIALSExpired Credentials.
UNKNOWN_IP_ADDRESSUnregistered IP address.
INVALID_TOKENInvalid Token.
TOKEN_IN_USEThe token provided is currently being used in another request.
403 ForbiddenAUTHORIZATION_REQUIREDThe merchant has no authorization to use this API.
404 Not foundPAYMENT_NOT_FOUNDPayment not found.
TRANSACTION_NOT_FOUNDTransaction of payment not found.
CUSTOMER_NOT_FOUNDCustomer not found.
CHECKOUT_SESSION_NOT_FOUNDCheckout session not found or inactive.
REPORT_NOT_FOUNDReport id not found.
405 Method not allowedUNSUPPORTED_METHODMethod not supported.
500 Internal Server ErrorINTERNAL_ERRORInternal error.
504 Gateway TimeoutREQUEST_TIMEOUTRequest Timeout.