API documentation

Welcome to the official API documentation for BTC Direct. This page provides all the necessary information to help you integrate seamlessly with our platform. Here, you’ll find details on obtaining API credentials, using the API, and accessing different versions of our endpoints.

Introduction

The BTC Direct API provides a suite of tools to integrate cryptocurrency services into your platform. From buying and selling digital assets to managing users, our API supports a wide variety of use cases. This documentation serves as a guide to help you understand how to work with our API and get started quickly.

This documentation is used when you want to integrate our services into your platform. If you are looking for a way to buy or sell cryptocurrency, please visit our website at btcdirect.eu.

This guide has been written for developers and partners that wish to integrate with BTC Direct using our API services. If you are looking to integrate with our Unified Checkout or Widget services, please refer to the Unified Checkout or Widget documentation.

Obtaining API credentials

To obtain your API credentials, you will need to contact your account manager.

Once you have your credentials, you can begin making requests to our API endpoints. Use your credentials securely and never expose them in client-side code.

API environments

Environment	Base URL
Production	https://api.btcdirect.eu
Sandbox	https://api-sandbox.btcdirect.eu

API versions

The API has two versions. V2 is the newer version with improved endpoints. When integrating, you will typically use a combination of both:

• V1: authentication, user management, sell flow, system information.
• V2: buy checkout, payment methods, prices, offers.

Both versions use the same base URL and authentication mechanism.

Error responses

When a request fails, the API returns an HTTP 400 status code with a JSON body containing the error details:

{
  "errors": {
    "ER325": {
      "code": "ER325",
      "message": "Wallet address is required.",
      "solution": "Provide a valid wallet address in the request."
    }
  }
}

Each error includes a unique error code (e.g. ER325), a human-readable message, and a suggested solution. The full list of error codes per endpoint is available in the OpenAPI specification.

OpenAPI specification

The full OpenAPI (Swagger) specification is available as JSON for each API version:

Version	Production	Sandbox
V1	api.btcdirect.eu/api/v1/doc.json	api-sandbox.btcdirect.eu/api/v1/doc.json
V2	api.btcdirect.eu/api/v2/doc.json	api-sandbox.btcdirect.eu/api/v2/doc.json

You can also browse the specification interactively via the V1 and V2 pages.

FAQ and support

If you encounter any issues or have questions, don’t worry! Your account manager will be happy to help you with any questions you may have.

Answers to common questions can be found in the FAQ page.