# Developer tools and APIs 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](/checkout/releases/2025-10-08-added-support-for-checkout-api-in-composable-commerce-sdks) for multiple programming languages, making it easier to integrate Checkout into any technology stack. - .NET SDK: we added comprehensive Checkout API support to the .NET Core SDK v2. The SDK provides strongly typed models for Checkout resources and complete client setup for Checkout endpoints. Developers can find [working examples in the SDK repository](https://github.com/commercetools/commercetools-dotnet-core-sdk-v2/tree/master/commercetools.Sdk/Examples) demonstrating common Checkout scenarios, along with [detailed client setup instructions](/certifications/dev-tooling/dotnet-sdk-getting-started.md#set-up-the-client) in the documentation. - Java SDK: the Java SDK also received Checkout API support for both Gradle and Maven build systems. Developers using Gradle can follow the [Gradle setup guide](/certifications/dev-tooling/java-sdk-getting-started.md#gradle) for dependency configuration, while Maven users can reference the [Maven setup guide](/certifications/dev-tooling/java-sdk-getting-started.md#maven) for POM configuration. Both build systems support the same [client class creation process](/certifications/dev-tooling/java-sdk-getting-started.md#create-the-client-class) with complete initialization instructions. - TypeScript SDK: the TypeScript SDK, already widely used in frontend projects, gained full Checkout API support through npm package installation. The SDK provides TypeScript type definitions for all Checkout resources, ensuring type safety throughout development. Developers can follow the [installation guide](/certifications/dev-tooling/ts-sdk-getting-started.md#install-the-typescript-sdk) and [client creation documentation](/certifications/dev-tooling/ts-sdk-getting-started.md#create-the-client) to get started with Checkout API integration. 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](/checkout/releases/2025-10-10-introduced-checkout-applications-api-and-payment-integrations-api-in-public-beta) 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](/checkout/applications-api.md) 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](/checkout/payment-integrations-api.md) 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. ## Related pages - [Area overview page with navigation](/certifications.md) - [Previous page: Customer experience features](/certifications/frontend-developer-refresher-2026/checkout-refresher-2026/customer-experience-features.md) - [Search documentation and API specs](/search.md)