Tender provider integrations overview

You can use the Toast tender API to integrate your tender provider with the Toast platform. The tender API supports the Hotel property management system integration and enables a hotel restaurant to directly bill a guest at the hotel, for example, by using their room number or name.

In addition, the tender API allows you to apply discounts from a third-party system and refund payments and discounts on a check.

The API can be defined by:

  • Transaction requests

  • Transaction responses

  • Error codes

Transaction types define the action to take and the related payload. Transactions between the Toast platform and the tender provider during a tender transaction are represented in the following figure.

Your implementation is responsible for returning the response synchronously.

Tender integrations define a single HTTPS endpoint. In your implementation, all requests are posted to this single endpoint. Requests from restaurants configured to use your service are sent to this endpoint. For example, you can name your endpoint to be:


Each POST request to the endpoint includes:

  • A TenderTransaction object in the message body.

  • The following header parameters:

    Header Parameter



    The type of tender transaction that occurred. Requests are filtered based upon this parameter.


    The unique identifier of the restaurant, defined by the Toast platform. This parameter determines which restaurant is sending the request.


    A unique identifier of the tender transaction, defined by the Toast platform.


    A JSON Web Token (JWT) that you can use to authenticate the request. Verify the token using the public key that you get from the Toast user management service. For more information, see Authenticating outbound API requests.

For more information about the transaction descriptions, workflows and examples, see Transaction descriptions.

Error handling

Your tender interface implementation must return the following HTTPS responses to the requests that it receives from the Toast POS system.

200 means OK and has pre-defined success status in the response

  • ACCEPT - The tender service provider processed the transaction successfully.

400 means a bad request. The transactionStatus value of the TenderTransactionResponse object is one of:

  • ERROR_INVALID_TOAST_TRANSACTION_TYPE - Your implementation does not handle the transaction type supplied in the request. Return this response when the request transaction type is defined by the tender API but you decided not to support it.

  • ERROR_INVALID_INPUT_PROPERTIES - The JSON values specified in the tenderTransaction object in the request body do not match the requirements of the transaction type.

  • ERROR_INVALID_TOKEN - The authentication token supplied in the Authorization header parameter is invalid or cannot be validated. For information about request authentication, see Authenticating outbound API requests.

  • ERROR_INVALID_RESTAURANT - The restaurant identifier included in the Toast-Restaurant-External-ID header parameter of the request is not recognized by the tender provider integration implementation. You receive the identifiers for your connected restaurants when implementing the tender API.

  • ERROR_TRANSACTION_DOES_NOT_EXIST - The reverse request, specified by a TENDER_REVERSE, is for a transaction that does not exist."

  • ERROR_TRANSACTION_CANNOT_BE_REVERSED - The transaction specified by a TENDER_REVERSE request cannot be reversed.

  • ERROR_ACCOUNT_INVALID - The tender identifier is not in the set of identifiers that correspond to the current restaurant. For example, if a guest account is entered incorrectly, your implementation returns this status.

  • ERROR_INSUFFICIENT_FUNDS - The tender account does not have sufficient payment to make a payment or tit specified in a TENDER_RETRIEVE_PAYMENTS or TENDER_RETRIEVE_GRATUITY.

  • ERROR_UNABLE_TO_PROCESS - The transaction cannot be processed by the partner. This can be due to an issue that occurred on the partner's end.

500 means Internal Server Error

Latency requirements

The Toast platform expects a 500ms average response time from your tender API endpoint. The maximum response time must be 5 seconds, after which we may close the socket and send another request. Response times should be as short as possible because there will be a server waiting.


  • You cannot use the tender API to pay for checks using the orders API or Toast online ordering. The tender API is only supported at the Toast platform.

  • You cannot use the tender API with contactless pay.