Developer tools and APIs

Integrate and automate Checkout with multi-language SDK support and programmatic configuration APIs.

Ask about this Page
Copy for LLM
View as Markdown

After completing this page, you should be able to:

  • Integrate Checkout API functionality using .NET, Java, or TypeScript SDKs in your preferred technology stack.

  • Use the Applications API and Payment Integrations API to programmatically manage Checkout configuration.

  • Understand when to use both APIs together versus independently for different configuration scenarios.

2025 brought significant improvements to the developer experience with Checkout, introducing SDK support across multiple programming languages and new management APIs for programmatic configuration. These tools enable teams to work with Checkout in their preferred technology stack and automate infrastructure-as-code workflows.

Checkout API SDK support

In October 2025, Checkout API support was added to commercetools SDKs for multiple programming languages, making it easier to integrate Checkout into any technology stack.

This multi-language SDK support enables teams to work with Checkout using their preferred technology stack, whether building frontend applications in TypeScript, backend services in Java, or enterprise applications in .NET.

Checkout management APIs

In October 2025, we introduced two new APIs in public beta, bringing programmatic control to Checkout configuration and eliminating the need to manually configure settings through the Merchant Center.
The Checkout Applications API gives you programmatic control over Checkout applications. You can create Checkout applications through code, modify application configurations as requirements change, retrieve information about existing applications, remove applications that are no longer in use, and manage settings consistently across different environments.
The Payment Integrations API provides programmatic access to your payment integrations inside the Checkout applications. This API allows you to configure which payment methods are available to customers and query your active integrations to understand your current payment setup.

Together, these APIs mean you no longer need to configure Checkout applications or payment integrations manually through the Merchant Center—everything can be managed through API calls.

Work with both APIs

The two APIs serve different purposes and can be used together or independently depending on your needs.

When you're creating a new Checkout application from scratch, you'll typically use both APIs in tandem. The Applications API handles the foundational application setup—defining the application name, checkout mode, supported countries, and return URLs. The Payment Integrations API then configures which payment methods and Connectors the application will use.
For updates to existing applications, you have more flexibility. You can use either API on its own to make targeted changes. For instance, if you want to add a new payment method to an existing application, you'd only need the Payment Integrations API—no need to change the application configuration. Similarly, if you need to add an allowed origin URL for security purposes, you'd use just the Applications API without affecting payment settings.

The two APIs enable infrastructure-as-code approaches for managing Checkout, making it easier to implement DevOps practices like version control, automated deployments, and consistent configuration across multiple environments.

Test your knowledge