Integration development process

These are the main paths toward developing a Toast integration:

  • Standardized integrations that can apply to all restaurants.

    These integrations typically transition to general availability after their development and beta period are complete.

  • Custom integrations that apply to specific restaurant groups.

    These integrations are built for specific restaurants and do not become generally available for all restaurants.

Integrations for all restaurants

Here is the typical integration development process for integrations on the path toward general availability.

Application

The first step toward becoming a Toast partner is to fill out an application for partnership.

The Toast integrations team reviews your application and responds to you with a decision.

Discovery

Toast receives a high volume of applications for partnership and is not able to integrate with all who are interested.

If the Toast integrations team needs more information about your product to determine whether building an integration is a good next step, the Toast integrations team schedules a discovery call with you.

On this call, the Toast integrations team discusses the Toast API functionality with you and determines whether an integration is technically feasible.

Statement of Work and kickoff

If the Toast integration team plans to move forward with integration development for your product, you receive a Statement of Work (SOW) to formalize the partnership.

After the SOW is finalized, your Toast integration contact holds a development kickoff call to discuss the integration development process and the sandbox environment.

Development

After your kickoff call, the Toast integrations team gives you authentication credentials that correspond to your partner API account. You can use these credentials for testing in the sandbox environment.

Once you have sandbox credentials, you can begin to write and test your code.

As you build your integration, refer to our integration development checklists.

Certification

When you are ready to use your integration for live restaurants in the production environment, reach out to your Toast integrations contact to schedule a certification call. The goal of the certification is to make sure that you and the Toast integrations team feel comfortable introducing your integration to initial customers in the production environment (the beta phase).

The Toast team sends you a survey to collect technical information about your integration. You should submit the survey response at least one business day before your certification call.

The certification call is a one-hour, interactive, demo-style review of your integration's workflows. The demo should reproduce as closely as possible the integration experience you will provide in production.

On the call, you discuss:

  • How you interact with each endpoint.

  • How you poll historical data.

  • If applicable, how you send data to the Toast platform.

  • For any restaurant reports, the alignment between your data and the Toast platform data.

If problems or questions arise during the certification call, the Toast team sends an email message that lists the issues. It is your responsibility to resolve the issues before you can receive production credentials.

Beta

After your integration is certified, the Toast integrations team issues production credentials and your integration will enter its beta phase.

You choose 3-5 restaurants or restaurant groups to participate in the beta phase of your integration. Each restaurant should use the integration in the production environment for several weeks. This gives them enough time to become familiar with the integration and to adopt it in their daily workflows. When you allow customers to become early adopters of your integration, make sure that the restaurants understand that they can become early adopters on the condition that they provide feedback about the integration.

The Toast team contacts the beta restaurants to get feedback. If any major issues arise, the Toast team works with you to address them.

Your organization works with the Toast partner marketing team to develop co-marketing activities and integration marketing copy.

General availability

If your beta customers are satisfied with the integration, and your marketing materials are prepared, the Toast integrations team transitions the integration to general availability. In general availability, your integration is listed on the Toast platform public integrations site.

Moving forward, restaurants are able to add your integration through the Toast platform My Integrations page.

After your integration is generally available, the Toast integrations support team helps you to resolve any customer-specific issues that arise.

Integrations for specific restaurant groups

Here is the process for developing custom integrations for specific restaurant groups.

Application

The first step toward building your own integration is to fill out an application for a custom integration.

Discovery

The Toast API Solutions team schedules a discovery call with you within three weeks of receiving your application.

On this call, the Toast team discusses the Toast API functionality with you and determines whether an integration is technically feasible.

Statement of Work and kickoff

If the Toast integrations team chooses to move forward with integration development for your product, you receive a Statement of Work (SOW) to formalize the scope of services.

After the SOW is finalized, a Toast API Solutions Engineer schedules a development kickoff call to discuss the integration development process and the sandbox environment.

Development

After your kickoff call, the Toast API Solutions team gives you authentication credentials to the sandbox environment. These credentials correspond to your partner API account or restaurant management group API account.

Once you have sandbox credentials, you can begin to write and test your code.

As you build your integration, refer to our integration development checklists.

Certification

When you are ready to take your integration live with your restaurants in the production environment, reach out to the Toast API Solutions team to schedule a certification call. The goal of the certification is to make sure that your integrated solution adheres to Toast API best practices and to understand the final primary workflows being supported.

The API Solutions team sends you a form to collect technical information about your integration. You should submit the completed form at least one business day before your certification call.

The certification call is a one-hour, interactive, demo-style review of your integration's workflows. The demo should reproduce the integration experience you will provide in production as closely as possible. On the call, you discuss:

  • How you interact with each endpoint.

  • If applicable, how you poll historical data.

  • If applicable, how you send data to the Toast platform.

  • For any restaurant reports, the alignment between your data and Toast POS system data.

If problems or questions arise during the certification call, the Toast API Solutions team sends an email message that lists the issues. It is your responsibility to resolve the issues before you can receive production credentials.

Production testing and go-live

After your integration is certified, the Toast API Solutions team issues production credentials. Your integration enters its production QA phase.

The Toast API Solutions team strongly encourages testing in the production environment to ensure that all workflows function as expected.

The Toast API Solutions team assists you with any major issues that arise.

If additional locations would like to use your integration after it is in production at its first mutual customer, you pay an activation fee. This fee varies based on the number of locations that add your integration.

Number of locations

One-time payment value

1-5

$100

6-10

$300

11 or more

$500

To add additional locations, ask the restaurant to send an email to the Toast's API Solutions team that provides:

  • Their permission to be connected to your integration.

  • The names of the locations that will add the integration.