mollie-api-java

Developer-friendly & type-safe Java SDK specifically catered to leverage mollie-api-java API.

Migration

This documentation is for the new Mollie's SDK. You can find more details on how to migrate from the old version to the new one here.

Summary

SDK Installation

Getting started

JDK 11 or later is required.

The samples below show how a published SDK artifact is used:

Gradle:

implementation 'com.mollie:mollie:0.22.1'

Maven:

<dependency>
    <groupId>com.mollie</groupId>
    <artifactId>mollie</artifactId>
    <version>0.22.1</version>
</dependency>

How to build

After cloning the git repository to your file system you can build the SDK artifact from source to the build directory by running ./gradlew build on *nix systems or gradlew.bat on Windows systems.

If you wish to build from source and publish the SDK artifact to your local Maven repository (on your filesystem) then use the following command (after cloning the git repo locally):

On *nix:

./gradlew publishToMavenLocal -Pskip.signing

On Windows:

gradlew.bat publishToMavenLocal -Pskip.signing

SDK Example Usage

Example

package hello.world;

import com.mollie.mollie.Client;
import com.mollie.mollie.models.components.Security;
import com.mollie.mollie.models.errors.ErrorResponse;
import com.mollie.mollie.models.operations.ListBalancesRequest;
import com.mollie.mollie.models.operations.ListBalancesResponse;
import java.lang.Exception;

public class Application {

    public static void main(String[] args) throws ErrorResponse, Exception {

        Client sdk = Client.builder()
                .testmode(false)
                .security(Security.builder()
                    .apiKey(System.getenv().getOrDefault("API_KEY", ""))
                    .build())
            .build();

        ListBalancesRequest req = ListBalancesRequest.builder()
                .currency("EUR")
                .from("bal_gVMhHKqSSRYJyPsuoPNFH")
                .limit(50L)
                .idempotencyKey("123e4567-e89b-12d3-a456-426")
                .build();

        ListBalancesResponse res = sdk.balances().list()
                .request(req)
                .call();

        if (res.object().isPresent()) {
            // handle response
        }
    }
}

Asynchronous Call

An asynchronous SDK client is also available that returns a CompletableFuture<T>. See Asynchronous Support for more details on async benefits and reactive library integration.

package hello.world;

import com.mollie.mollie.AsyncClient;
import com.mollie.mollie.Client;
import com.mollie.mollie.models.components.Security;
import com.mollie.mollie.models.operations.ListBalancesRequest;
import com.mollie.mollie.models.operations.async.ListBalancesResponse;
import java.util.concurrent.CompletableFuture;

public class Application {

    public static void main(String[] args) {

        AsyncClient sdk = Client.builder()
                .testmode(false)
                .security(Security.builder()
                    .apiKey(System.getenv().getOrDefault("API_KEY", ""))
                    .build())
            .build()
            .async();

        ListBalancesRequest req = ListBalancesRequest.builder()
                .currency("EUR")
                .from("bal_gVMhHKqSSRYJyPsuoPNFH")
                .limit(50L)
                .idempotencyKey("123e4567-e89b-12d3-a456-426")
                .build();

        CompletableFuture<ListBalancesResponse> resFut = sdk.balances().list()
                .request(req)
                .call();

        resFut.thenAccept(res -> {
            if (res.object().isPresent()) {
            // handle response
            }
        });
    }
}

Asynchronous Support

The SDK provides comprehensive asynchronous support using Java's CompletableFuture<T> and Reactive Streams Publisher<T> APIs. This design makes no assumptions about your choice of reactive toolkit, allowing seamless integration with any reactive library.

Why Use Async?

Asynchronous operations provide several key benefits:

Non-blocking I/O: Your threads stay free for other work while operations are in flight
Better resource utilization: Handle more concurrent operations with fewer threads
Improved scalability: Build highly responsive applications that can handle thousands of concurrent requests
Reactive integration: Works seamlessly with reactive streams and backpressure handling

Reactive Library Integration

The SDK returns Reactive Streams Publisher<T> instances for operations dealing with streams involving multiple I/O interactions. We use Reactive Streams instead of JDK Flow API to provide broader compatibility with the reactive ecosystem, as most reactive libraries natively support Reactive Streams.

Why Reactive Streams over JDK Flow?

Broader ecosystem compatibility: Most reactive libraries (Project Reactor, RxJava, Akka Streams, etc.) natively support Reactive Streams
Industry standard: Reactive Streams is the de facto standard for reactive programming in Java
Better interoperability: Seamless integration without additional adapters for most use cases

Integration with Popular Libraries:

Project Reactor: Use Flux.from(publisher) to convert to Reactor types
RxJava: Use Flowable.fromPublisher(publisher) for RxJava integration
Akka Streams: Use Source.fromPublisher(publisher) for Akka Streams integration
Vert.x: Use ReadStream.fromPublisher(vertx, publisher) for Vert.x reactive streams
Mutiny: Use Multi.createFrom().publisher(publisher) for Quarkus Mutiny integration

For JDK Flow API Integration: If you need JDK Flow API compatibility (e.g., for Quarkus/Mutiny 2), you can use adapters:

// Convert Reactive Streams Publisher to Flow Publisher
Flow.Publisher<T> flowPublisher = FlowAdapters.toFlowPublisher(reactiveStreamsPublisher);

// Convert Flow Publisher to Reactive Streams Publisher
Publisher<T> reactiveStreamsPublisher = FlowAdapters.toPublisher(flowPublisher);

For standard single-response operations, the SDK returns CompletableFuture<T> for straightforward async execution.

Supported Operations

Async support is available for:

Server-sent Events: Stream real-time events with Reactive Streams Publisher<T>
JSONL Streaming: Process streaming JSON lines asynchronously
Pagination: Iterate through paginated results using callAsPublisher() and callAsPublisherUnwrapped()
File Uploads: Upload files asynchronously with progress tracking
File Downloads: Download files asynchronously with streaming support
Standard Operations: All regular API calls return CompletableFuture<T> for async execution

Authentication

Per-Client Security Schemes

This SDK supports the following security schemes globally:

Name	Type	Scheme
`apiKey`	http	HTTP Bearer
`oAuth`	oauth2	OAuth2 token

You can set the security parameters through the security builder method when initializing the SDK client instance. The selected scheme will be used by default to authenticate with the API for all operations that support it. For example:

package hello.world;

import com.mollie.mollie.Client;
import com.mollie.mollie.models.components.Security;
import com.mollie.mollie.models.errors.ErrorResponse;
import com.mollie.mollie.models.operations.ListBalancesRequest;
import com.mollie.mollie.models.operations.ListBalancesResponse;
import java.lang.Exception;

public class Application {

    public static void main(String[] args) throws ErrorResponse, Exception {

        Client sdk = Client.builder()
                .security(Security.builder()
                    .apiKey(System.getenv().getOrDefault("API_KEY", ""))
                    .build())
                .testmode(false)
            .build();

        ListBalancesRequest req = ListBalancesRequest.builder()
                .currency("EUR")
                .from("bal_gVMhHKqSSRYJyPsuoPNFH")
                .limit(50L)
                .idempotencyKey("123e4567-e89b-12d3-a456-426")
                .build();

        ListBalancesResponse res = sdk.balances().list()
                .request(req)
                .call();

        if (res.object().isPresent()) {
            // handle response
        }
    }
}

Idempotency Key

This SDK supports the usage of Idempotency Keys. See our documentation on how to use it.

package com.example.app;

import com.mollie.mollie.Client;
import com.mollie.mollie.models.components.*;
import com.mollie.mollie.models.operations.*;
import java.lang.Exception;
import java.lang.RuntimeException;

public class App 
{
    public static void main(String[] args) throws ErrorResponse, Exception {
        try {
            Client sdk = Client.builder()
                    .security(Security.builder()
                        .apiKey(System.getenv().getOrDefault("API_KEY", ""))
                        .build())
                .build();

            String idempotencyKey = "<some-idempotency-key>";

            CreatePaymentResponse res = sdk.payments().create()
                .idempotencyKey(idempotencyKey)
                .paymentRequest(PaymentRequest.builder()
                    .description("My first payment")
                    .redirectUrl("https://example.org/redirect")
                    .amount(Amount.builder()
                        .currency("EUR")
                        .value("10.00")
                        .build())
                    .build())
                .call();

            CreatePaymentResponse res2 = sdk.payments().create()
                .idempotencyKey(idempotencyKey)
                .paymentRequest(PaymentRequest.builder()
                    .description("My first payment")
                    .redirectUrl("https://example.org/redirect")
                    .amount(Amount.builder()
                        .currency("EUR")
                        .value("10.00")
                        .build())
                    .build())
                .call();

            String paymentId1 = res.paymentResponse().orElseThrow().id().orElseThrow();
            String paymentId2 = res2.paymentResponse().orElseThrow().id().orElseThrow();
            System.out.println(paymentId1);
            System.out.println(paymentId2);
            if (paymentId1.equals(paymentId2)) {
                System.out.println("Payments are the same");
            } else {
                System.out.println("Payments are different");
            }
        } catch (Exception e) {
            throw new RuntimeException(e);
        }
    }
}

Add Custom User-Agent Header

The SDK allows you to append a custom suffix to the User-Agent header for all requests. This can be used to identify your application or integration when interacting with the API, making it easier to track usage or debug requests. The suffix is automatically added to the default User-Agent string generated by the SDK. You can add it when creating the client:

Client sdk = Client.builder()
    .security(Security.builder()
        .apiKey(System.getenv().getOrDefault("API_KEY", ""))
        .build())
    .customUserAgent("insert something here")
.build();

Add Profile ID and Testmode to Client

The SDK allows you to define the profileId and testmode in the client. This way, you don't need to add this information to the payload every time when using OAuth. This will not override the details provided in the individual requests.

Client sdk = Client.builder()
    .security(Security.builder()
        .apiKey(System.getenv().getOrDefault("OAUTH_KEY", ""))
        .build())
    .testmode(true)
    .profileId("pfl_...")
.build();

Available Resources and Operations

Available methods

balances()

list - List balances
get - Get balance
getPrimary - Get primary balance
getReport - Get balance report
listTransactions - List balance transactions

balanceTransfers()

create - Create a Connect balance transfer
list - List all Connect balance transfers
get - Get a Connect balance transfer

capabilities()

list - List capabilities

captures()

create - Create capture
list - List captures
get - Get capture

chargebacks()

list - List payment chargebacks
get - Get payment chargeback
all - List all chargebacks

clientLinks()

create - Create client link

clients()

list - List clients
get - Get client

customers()

create - Create customer
list - List customers
get - Get customer
update - Update customer
delete - Delete customer
createPayment - Create customer payment
listPayments - List customer payments

delayedRouting()

create - Create a delayed route
list - List payment routes

invoices()

list - List invoices
get - Get invoice

mandates()

create - Create mandate
list - List mandates
get - Get mandate
revoke - Revoke mandate

methods()

list - List payment methods
all - List all payment methods
get - Get payment method

onboarding()

get - Get onboarding status
submit - Submit onboarding data

organizations()

get - Get organization
getCurrent - Get current organization
getPartner - Get partner status

paymentLinks()

create - Create payment link
list - List payment links
get - Get payment link
update - Update payment link
delete - Delete payment link
listPayments - Get payment link payments

payments()

create - Create payment
list - List payments
get - Get payment
update - Update payment
cancel - Cancel payment
releaseAuthorization - Release payment authorization

permissions()

list - List permissions
get - Get permission

profiles()

create - Create profile
list - List profiles
get - Get profile
update - Update profile
delete - Delete profile
getCurrent - Get current profile

refunds()

create - Create payment refund
list - List payment refunds
get - Get payment refund
cancel - Cancel payment refund
all - List all refunds

salesInvoices()

create - Create sales invoice
list - List sales invoices
get - Get sales invoice
update - Update sales invoice
delete - Delete sales invoice

settlements()

list - List settlements
get - Get settlement
getOpen - Get open settlement
getNext - Get next settlement
listPayments - List settlement payments
listCaptures - List settlement captures
listRefunds - List settlement refunds
listChargebacks - List settlement chargebacks

subscriptions()

create - Create subscription
list - List customer subscriptions
get - Get subscription
update - Update subscription
cancel - Cancel subscription
all - List all subscriptions
listPayments - List subscription payments

terminals()

list - List terminals
get - Get terminal

wallets()

requestApplePaySession - Request Apple Pay payment session

webhookEvents()

get - Get a Webhook Event

webhooks()

create - Create a webhook
list - List all webhooks
update - Update a webhook
get - Get a webhook
delete - Delete a webhook
test - Test a webhook

Global Parameters

Certain parameters are configured globally. These parameters may be set on the SDK client instance itself during initialization. When configured as an option during SDK initialization, These global values will be used as defaults on the operations that use them. When such operations are called, there is a place in each to override the global value, if needed.

For example, you can set profileId to `` at SDK initialization and then you do not have to pass the same value on calls to operations like list. But if you want to do so you may, which will locally override the global setting. See the example code below for a demonstration.

Available Globals

The following global parameters are available.

Name	Type	Description
profileId	java.lang.String	The identifier referring to the profile you wish to retrieve the resources for. Most API credentials are linked to a single profile. In these cases the `profileId` can be omitted. For organization-level credentials such as OAuth access tokens however, the `profileId` parameter is required.
testmode	boolean	Most API credentials are specifically created for either live mode or test mode. In those cases the `testmode` query parameter can be omitted. For organization-level credentials such as OAuth access tokens, you can enable test mode by setting the `testmode` query parameter to `true`. Test entities cannot be retrieved when the endpoint is set to live mode, and vice versa.
customUserAgent	java.lang.String	Custom user agent string to be appended to the default Mollie SDK user agent.

Example

package hello.world;

import com.mollie.mollie.Client;
import com.mollie.mollie.models.components.Security;
import com.mollie.mollie.models.errors.ErrorResponse;
import com.mollie.mollie.models.operations.ListBalancesRequest;
import com.mollie.mollie.models.operations.ListBalancesResponse;
import java.lang.Exception;

public class Application {

    public static void main(String[] args) throws ErrorResponse, Exception {

        Client sdk = Client.builder()
                .testmode(false)
                .profileId("<id>")
                .customUserAgent("<value>")
                .security(Security.builder()
                    .apiKey(System.getenv().getOrDefault("API_KEY", ""))
                    .build())
            .build();

        ListBalancesRequest req = ListBalancesRequest.builder()
                .currency("EUR")
                .from("bal_gVMhHKqSSRYJyPsuoPNFH")
                .limit(50L)
                .idempotencyKey("123e4567-e89b-12d3-a456-426")
                .build();

        ListBalancesResponse res = sdk.balances().list()
                .request(req)
                .call();

        if (res.object().isPresent()) {
            // handle response
        }
    }
}

Retries

Some of the endpoints in this SDK support retries. If you use the SDK without any configuration, it will fall back to the default retry strategy provided by the API. However, the default retry strategy can be overridden on a per-operation basis, or across the entire SDK.

To change the default retry strategy for a single API call, you can provide a RetryConfig object through the retryConfig builder method:

package hello.world;

import com.mollie.mollie.Client;
import com.mollie.mollie.models.components.Security;
import com.mollie.mollie.models.errors.ErrorResponse;
import com.mollie.mollie.models.operations.ListBalancesRequest;
import com.mollie.mollie.models.operations.ListBalancesResponse;
import com.mollie.mollie.utils.BackoffStrategy;
import com.mollie.mollie.utils.RetryConfig;
import java.lang.Exception;
import java.util.concurrent.TimeUnit;

public class Application {

    public static void main(String[] args) throws ErrorResponse, Exception {

        Client sdk = Client.builder()
                .testmode(false)
                .security(Security.builder()
                    .apiKey(System.getenv().getOrDefault("API_KEY", ""))
                    .build())
            .build();

        ListBalancesRequest req = ListBalancesRequest.builder()
                .currency("EUR")
                .from("bal_gVMhHKqSSRYJyPsuoPNFH")
                .limit(50L)
                .idempotencyKey("123e4567-e89b-12d3-a456-426")
                .build();

        ListBalancesResponse res = sdk.balances().list()
                .request(req)
                .retryConfig(RetryConfig.builder()
                    .backoff(BackoffStrategy.builder()
                        .initialInterval(1L, TimeUnit.MILLISECONDS)
                        .maxInterval(50L, TimeUnit.MILLISECONDS)
                        .maxElapsedTime(1000L, TimeUnit.MILLISECONDS)
                        .baseFactor(1.1)
                        .jitterFactor(0.15)
                        .retryConnectError(false)
                        .build())
                    .build())
                .call();

        if (res.object().isPresent()) {
            // handle response
        }
    }
}

If you'd like to override the default retry strategy for all operations that support retries, you can provide a configuration at SDK initialization:

package hello.world;

import com.mollie.mollie.Client;
import com.mollie.mollie.models.components.Security;
import com.mollie.mollie.models.errors.ErrorResponse;
import com.mollie.mollie.models.operations.ListBalancesRequest;
import com.mollie.mollie.models.operations.ListBalancesResponse;
import com.mollie.mollie.utils.BackoffStrategy;
import com.mollie.mollie.utils.RetryConfig;
import java.lang.Exception;
import java.util.concurrent.TimeUnit;

public class Application {

    public static void main(String[] args) throws ErrorResponse, Exception {

        Client sdk = Client.builder()
                .retryConfig(RetryConfig.builder()
                    .backoff(BackoffStrategy.builder()
                        .initialInterval(1L, TimeUnit.MILLISECONDS)
                        .maxInterval(50L, TimeUnit.MILLISECONDS)
                        .maxElapsedTime(1000L, TimeUnit.MILLISECONDS)
                        .baseFactor(1.1)
                        .jitterFactor(0.15)
                        .retryConnectError(false)
                        .build())
                    .build())
                .testmode(false)
                .security(Security.builder()
                    .apiKey(System.getenv().getOrDefault("API_KEY", ""))
                    .build())
            .build();

        ListBalancesRequest req = ListBalancesRequest.builder()
                .currency("EUR")
                .from("bal_gVMhHKqSSRYJyPsuoPNFH")
                .limit(50L)
                .idempotencyKey("123e4567-e89b-12d3-a456-426")
                .build();

        ListBalancesResponse res = sdk.balances().list()
                .request(req)
                .call();

        if (res.object().isPresent()) {
            // handle response
        }
    }
}

Error Handling

Handling errors in this SDK should largely match your expectations. All operations return a response object or raise an exception.

ClientError is the base class for all HTTP error responses. It has the following properties:

Method	Type	Description
`message()`	`String`	Error message
`code()`	`int`	HTTP response status code eg `404`
`headers`	`Map<String, List<String>>`	HTTP response headers
`body()`	`byte[]`	HTTP body as a byte array. Can be empty array if no body is returned.
`bodyAsString()`	`String`	HTTP body as a UTF-8 string. Can be empty string if no body is returned.
`rawResponse()`	`HttpResponse<?>`	Raw HTTP response (body already read and not available for re-read)

Example

package hello.world;

import com.mollie.mollie.Client;
import com.mollie.mollie.models.components.Security;
import com.mollie.mollie.models.errors.ErrorResponse;
import com.mollie.mollie.models.operations.ListBalancesRequest;
import com.mollie.mollie.models.operations.ListBalancesResponse;
import java.lang.Exception;

public class Application {

    public static void main(String[] args) throws ErrorResponse, Exception {

        Client sdk = Client.builder()
                .testmode(false)
                .security(Security.builder()
                    .apiKey(System.getenv().getOrDefault("API_KEY", ""))
                    .build())
            .build();

        ListBalancesRequest req = ListBalancesRequest.builder()
                .currency("EUR")
                .from("bal_gVMhHKqSSRYJyPsuoPNFH")
                .limit(50L)
                .idempotencyKey("123e4567-e89b-12d3-a456-426")
                .build();

        ListBalancesResponse res = sdk.balances().list()
                .request(req)
                .call();

        if (res.object().isPresent()) {
            // handle response
        }
    }
}

Error Classes

Primary errors:

ClientError: The base class for HTTP error responses.
- com.mollie.mollie.models.errors.ErrorResponse: An error response object. *

Less common errors (6)

Network errors:

java.io.IOException (always wrapped by java.io.UncheckedIOException). Commonly encountered subclasses of IOException include java.net.ConnectException, java.net.SocketTimeoutException, EOFException (there are many more subclasses in the JDK platform).

Inherit from ClientError:

* Check the method documentation to see if the error is applicable.

Server Selection

Override Server URL Per-Client

The default server can be overridden globally using the .serverURL(String serverUrl) builder method when initializing the SDK client instance. For example:

package hello.world;

import com.mollie.mollie.Client;
import com.mollie.mollie.models.components.Security;
import com.mollie.mollie.models.errors.ErrorResponse;
import com.mollie.mollie.models.operations.ListBalancesRequest;
import com.mollie.mollie.models.operations.ListBalancesResponse;
import java.lang.Exception;

public class Application {

    public static void main(String[] args) throws ErrorResponse, Exception {

        Client sdk = Client.builder()
                .serverURL("https://api.mollie.com/v2")
                .testmode(false)
                .security(Security.builder()
                    .apiKey(System.getenv().getOrDefault("API_KEY", ""))
                    .build())
            .build();

        ListBalancesRequest req = ListBalancesRequest.builder()
                .currency("EUR")
                .from("bal_gVMhHKqSSRYJyPsuoPNFH")
                .limit(50L)
                .idempotencyKey("123e4567-e89b-12d3-a456-426")
                .build();

        ListBalancesResponse res = sdk.balances().list()
                .request(req)
                .call();

        if (res.object().isPresent()) {
            // handle response
        }
    }
}

Custom HTTP Client

The Java SDK makes API calls using an HTTPClient that wraps the native HttpClient. This client provides the ability to attach hooks around the request lifecycle that can be used to modify the request or handle errors and response.

The HTTPClient interface allows you to either use the default SpeakeasyHTTPClient that comes with the SDK, or provide your own custom implementation with customized configuration such as custom executors, SSL context, connection pools, and other HTTP client settings.

The interface provides synchronous (send) methods and asynchronous (sendAsync) methods. The sendAsync method is used to power the async SDK methods and returns a CompletableFuture<HttpResponse<Blob>> for non-blocking operations.

The following example shows how to add a custom header and handle errors:

import com.mollie.mollie.Client;
import com.mollie.mollie.utils.HTTPClient;
import com.mollie.mollie.utils.SpeakeasyHTTPClient;
import com.mollie.mollie.utils.Utils;

import java.io.IOException;
import java.net.URISyntaxException;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;
import java.io.InputStream;
import java.time.Duration;

public class Application {
    public static void main(String[] args) {
        // Create a custom HTTP client with hooks
        HTTPClient httpClient = new HTTPClient() {
            private final HTTPClient defaultClient = new SpeakeasyHTTPClient();
            
            @Override
            public HttpResponse<InputStream> send(HttpRequest request) throws IOException, URISyntaxException, InterruptedException {
                // Add custom header and timeout using Utils.copy()
                HttpRequest modifiedRequest = Utils.copy(request)
                    .header("x-custom-header", "custom value")
                    .timeout(Duration.ofSeconds(30))
                    .build();
                    
                try {
                    HttpResponse<InputStream> response = defaultClient.send(modifiedRequest);
                    // Log successful response
                    System.out.println("Request successful: " + response.statusCode());
                    return response;
                } catch (Exception error) {
                    // Log error
                    System.err.println("Request failed: " + error.getMessage());
                    throw error;
                }
            }
        };

        Client sdk = Client.builder()
            .client(httpClient)
            .build();
    }
}

Custom HTTP Client Configuration

You can also provide a completely custom HTTP client with your own configuration:

import com.mollie.mollie.Client;
import com.mollie.mollie.utils.HTTPClient;
import com.mollie.mollie.utils.Blob;
import com.mollie.mollie.utils.ResponseWithBody;

import java.io.IOException;
import java.net.URISyntaxException;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;
import java.io.InputStream;
import java.time.Duration;
import java.util.concurrent.Executors;
import java.util.concurrent.CompletableFuture;

public class Application {
    public static void main(String[] args) {
        // Custom HTTP client with custom configuration
        HTTPClient customHttpClient = new HTTPClient() {
            private final HttpClient client = HttpClient.newBuilder()
                .executor(Executors.newFixedThreadPool(10))
                .connectTimeout(Duration.ofSeconds(30))
                // .sslContext(customSslContext) // Add custom SSL context if needed
                .build();

            @Override
            public HttpResponse<InputStream> send(HttpRequest request) throws IOException, URISyntaxException, InterruptedException {
                return client.send(request, HttpResponse.BodyHandlers.ofInputStream());
            }

            @Override
            public CompletableFuture<HttpResponse<Blob>> sendAsync(HttpRequest request) {
                // Convert response to HttpResponse<Blob> for async operations
                return client.sendAsync(request, HttpResponse.BodyHandlers.ofPublisher())
                    .thenApply(resp -> new ResponseWithBody<>(resp, Blob::from));
            }
        };

        Client sdk = Client.builder()
            .client(customHttpClient)
            .build();
    }
}

You can also enable debug logging on the default SpeakeasyHTTPClient:

import com.mollie.mollie.Client;
import com.mollie.mollie.utils.SpeakeasyHTTPClient;

public class Application {
    public static void main(String[] args) {
        SpeakeasyHTTPClient httpClient = new SpeakeasyHTTPClient();
        httpClient.enableDebugLogging(true);

        Client sdk = Client.builder()
            .client(httpClient)
            .build();
    }
}

Debugging

Debug

You can setup your SDK to emit debug logs for SDK requests and responses.

For request and response logging (especially json bodies), call enableHTTPDebugLogging(boolean) on the SDK builder like so:

SDK.builder()
    .enableHTTPDebugLogging(true)
    .build();

Example output:

Sending request: http://localhost:35123/bearer#global GET
Request headers: {Accept=[application/json], Authorization=[******], Client-Level-Header=[added by client], Idempotency-Key=[some-key], x-speakeasy-user-agent=[speakeasy-sdk/java 0.0.1 internal 0.1.0 org.openapis.openapi]}
Received response: (GET http://localhost:35123/bearer#global) 200
Response headers: {access-control-allow-credentials=[true], access-control-allow-origin=[*], connection=[keep-alive], content-length=[50], content-type=[application/json], date=[Wed, 09 Apr 2025 01:43:29 GMT], server=[gunicorn/19.9.0]}
Response body:
{
  "authenticated": true, 
  "token": "global"
}

WARNING: This should only used for temporary debugging purposes. Leaving this option on in a production system could expose credentials/secrets in logs. Authorization headers are redacted by default and there is the ability to specify redacted header names via SpeakeasyHTTPClient.setRedactedHeaders.

NOTE: This is a convenience method that calls HTTPClient.enableDebugLogging(). The SpeakeasyHTTPClient honors this setting. If you are using a custom HTTP client, it is up to the custom client to honor this setting.

Another option is to set the System property -Djdk.httpclient.HttpClient.log=all. However, this second option does not log bodies.

Development

Maturity

This SDK is in beta, and there may be breaking changes between versions without a major version update. Therefore, we recommend pinning usage to a specific package version. This way, you can install the same version each time without breaking changes unless you are intentionally looking for the latest version.

Contributions

While we value open-source contributions to this SDK, this library is generated programmatically. Any manual changes added to internal files will be overwritten on the next generation. We look forward to hearing your feedback. Feel free to open a PR or an issue with a proof of concept and we'll do our best to include it in a future release.

Name		Name	Last commit message	Last commit date
Latest commit History 98 Commits
.github/workflows		.github/workflows
.speakeasy		.speakeasy
docs		docs
gradle/wrapper		gradle/wrapper
spring		spring
src/main/java/com/mollie/mollie		src/main/java/com/mollie/mollie
.gitattributes		.gitattributes
.gitignore		.gitignore
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE.md		LICENSE.md
MIGRATION.md		MIGRATION.md
README.md		README.md
RELEASES.md		RELEASES.md
USAGE.md		USAGE.md
build-extras.gradle		build-extras.gradle
build.gradle		build.gradle
gradle.properties		gradle.properties
gradlew		gradlew
gradlew.bat		gradlew.bat
publishing.gradle		publishing.gradle
settings.gradle		settings.gradle

License

mollie/mollie-api-java

Folders and files

Latest commit

History

Repository files navigation

mollie-api-java

Migration

Summary

Table of Contents

SDK Installation

Getting started

How to build

SDK Example Usage

Example

Asynchronous Call

Asynchronous Support

Authentication

Per-Client Security Schemes

Idempotency Key

Add Custom User-Agent Header

Add Profile ID and Testmode to Client

Available Resources and Operations

Global Parameters

Available Globals

Example

Retries

Error Handling

Example

Error Classes

Server Selection

Override Server URL Per-Client

Custom HTTP Client

Debugging

Debug

Development

Maturity

Contributions

SDK Created by Speakeasy

About

Resources

License

Contributing

Security policy

Uh oh!

Stars

Watchers

Forks

Uh oh!

Uh oh!

Languages