Errors

Listed below are all the possible error codes that the Tippy API can return in case of an error.

Error code	Description
400	Bad Request - This error occurs when the request cannot be processed due to incorrect syntax, missing required fields, or invalid data formats. Ensure the endpoint is correct, all necessary identifiers are included, and the data format matches the API specification.
400	Invalid Parameter - This error indicates that one or more parameters in the request are incorrect or not as expected. The response includes a detailed mapping in the format parameter : error to identify the specific issue(s). Review the request parameters against the API specification for correct values and formats.
401	Unauthorized Request - This error signifies a failure in authentication due to invalid credentials or issues with integration. Potential reasons include an invalid authorization header, incorrect app secret, invalid account token, or incorrect location or device credentials. Verify all credentials are correct and that the integration is active and properly configured.
403	Forbidden Request - This error indicates the server understands the request but refuses to authorize it. Common reasons include a device not associated with the specified location, integration, or account, usage of the wrong app secret, or an account mismatch. Ensure that all devices and accounts are correctly associated and that you are using the correct credentials and permissions.
404	Not Found Error - This error occurs when the server cannot find the requested resource. Common causes include an account, owner, or user with the specified ID not being found, or the identifier does not match any existing records. This is a generic error for when a specific entity or resource cannot be located. Verify the accuracy of all identifiers and ensure the requested entity exists.
422	Unprocessable Entity - This error indicates that the request was well-formed but could not be followed through due to semantic errors. Typical reasons include missing webhook settings, an invalid webhook URL, or a failed webhook request. Ensure that your webhook settings are correctly configured, the URL is valid, and the server is capable of processing the request.
460	Duplicate Transaction Error - This error is triggered when there's an attempt to create a tip intent that duplicates existing data, specifically if a tip intent with the same transaction ID already exists. Check for pre-existing tip intents to avoid this error.
461	Transaction Not Updatable Error - This error indicates that a transaction with the specified ID cannot be updated. This may be due to the transaction's current status or policy restrictions. Verify the transaction's eligibility for updates before attempting modifications.
462	Transaction Already Confirmed Error - This error signifies that an attempt was made to modify or interact with a transaction that has already been confirmed. No further actions, including updates or cancellations, are permitted on confirmed transactions. Ensure to check the transaction's status before attempting any modifications.
463	Transaction Already Canceled Error - This error occurs when there is an attempt to modify or interact with a transaction that has already been canceled. Further actions, including updates or re-initiation, are not allowed on canceled transactions. Verify the transaction's current status to avoid this error.
464	Invalid Location Error - This error indicates issues with location validation. It may occur if the external location ID is incorrect or if the specified location cannot be found during retrieval. Ensure that all location identifiers are accurate and correspond to existing, valid locations within the system.
465	Unauthorized Device Error - Occurs when device credentials cannot be verified. Reasons include: non-existent device ID, device not activated, or attempts to access unauthorized entities. Verify device ID, ensure activation, and confirm entity access is appropriate.
466	Unable to Calculate Total Tip Amount - This error occurs during the tip calculation process at checkout, potentially due to internal issues or complications in communication with external payment processors. If this error persists, please contact support for further assistance.
467	No Tips Provided - Indicates a failure to retrieve tips data during the checkout process, likely due to internal system issues. If you encounter this error, please report it to our support team for assistance.
468	Unauthorized Employee Error - Occurs when there's an attempt to tip employees who are either unknown or not authorized in the transaction. This may include employees not found, non-existent employee IDs, or a mismatch in tip selection and the number of eligible employees. Ensure employee details are correct and authorized for tipping in the transaction.
469	Invalid Transaction Error - This error is triggered when a transaction with the specified ID does not exist or has already expired. It includes scenarios where a tip intent related to the transaction ID cannot be found in the database. Ensure the transaction ID is correct and that the transaction or tip intent has not expired or been removed.
470	Nonrefundable Transaction Error - Occurs when a transaction with the specified ID cannot be refunded, specifically if the tip intent associated with the transaction is in a status that disallows refunds. Only transactions with confirmed tip intents are eligible for refunds. Ensure to review the status of the tip intent before attempting a refund.
471	Invalid Amount Error - Triggered when transaction specifications are incorrect. For all transactions, either provide a single amount or a list of talents with their amounts, not both. For partial refunds specifically, both an amount and at least one talent must be provided. Ensure compliance with these parameters to avoid the error.
472	Non-Transferable Transaction Error - This error occurs when there is an attempt to transfer funds or value for a transaction that has not yet been confirmed. Transfers are only allowed for transactions that have received confirmation. Ensure the transaction status is confirmed before initiating a transfer.
473	Location Mapping Error - Occurs when there is a conflict in location to identifier mappings. This includes cases where another location is already mapped to the provided identifier, or a location with the same address is mapped under a different identifier. Ensure each location has a unique identifier and address mappings are correctly assigned to avoid this error.
474	Unsupported Action Error - This error indicates an attempt to initiate a payment or a transaction that the system cannot process. Possible reasons include restrictions on the type of transaction or issues with the specified transaction ID.
500	Unexpected Error - This error denotes an unforeseen issue, typically stemming from an internal problem. It suggests that the system encountered an unexpected condition which prevented it from fulfilling the request. While specific details may not be available, it is recommended to report this error to the support team for further investigation.
520	Device Communication Error - This error indicates problems in device communication, affecting operations such as activation, starting, or restarting tipping processes, and other general device-related issues. Retry the operation, and if issues persist, check the device's connectivity and configuration.
521	Integration Paused Error - This error occurs when API access is unauthorized because the integration has been paused. Ensure the integration status is active to resume API functionality.