Introduction

Sections

Theme switcher

Introduction

Let us introduce you to the revolutionary world of CryptoMate APIs, a gateway to effortless global transactions. In this era of rapid technological advancement, harnessing the power of Blockchain technology has never been simpler. With CryptoMate APIs, you can unlock the true potential of this transformative technology while keeping your focus unwaveringly on providing an exceptional customer experience.

Picture this: you have the opportunity to craft incredible applications in an astonishingly short span of time, all thanks to our groundbreaking APIs. Let me walk you through some captivating examples:

Imagine seamlessly integrating crypto assets into your fintech wallet. With our ingenious MPC module, managing diverse wallets across different blockchains becomes as intuitive as invoking just two APIs. Yes, you heard that right - two APIs stand between you and an enhanced financial ecosystem.

Or consider this: sending your customers NFTs as part of a loyalty program, with the ability to effortlessly track every intricate movement. This seemingly complex task becomes a breeze with our Media NFT module, requiring just two APIs. Loyalty meets simplicity.

And for those seeking to embrace the future of commerce, imagine accepting crypto payments with unparalleled ease - a reality achieved by invoking a single API through our Payment module. This single act bridges the gap between traditional and digital currency transactions.

Before embarking on your journey to integrate our API marvels, there's a crucial step: obtaining an API key. This key serves as a digital seal of authenticity, safeguarding your requests and ensuring a secure gateway to our suite of services. Obtaining it is as simple as signing up on our website, where possibilities await.

Now, let's delve into the dynamic environments our APIs thrive in:

Sandbox environment: Here, experimentation is the name of the game. It's the domain of testing and development, where every transaction carries no real-world implications. Your endeavors here shape the future without leaving a trace on the main blockchain.

Production environment: This is where reality takes center stage. The transactions that unfold here are not merely simulations; they're tangible, real-world actions that imprint themselves on the main blockchain.

Let's explore the core operations that anchor our platform:

Wallets: Craft and manage accounts and wallets with unprecedented ease, empowering your users with seamless control over their digital assets.

Media NFT: Immerse yourself in the world of NFTs, creating and managing these unique tokens to captivate your users and offer them a novel experience.

Payments: Redefine transactions by simplifying crypto payments, empowering your users to engage in borderless commerce without the complexities that once stood in their way.

Virtual Wallets: Create easily deposit addresses, concentrate capital, and manage it from a single place. Now, streamline your financial operations and maximize efficiency with our integrated solution.

Cards: Issue virtual or physical cards to your clients. You may choose between debit or credit system based on your requirements.

In conclusion, CryptoMate APIs are more than just a technical innovation - they're a gateway to an era of simplicity, empowerment, and boundless opportunity. It's time to embrace a future where global transactions are as effortless as invoking an API. Welcome to the world of limitless possibilities.


Was this section helpful?

What made this section unhelpful for you?

Base URL

Production:

https://api.cryptomate.me

Sandbox:

https://api.sandbox.cryptomate.me

Was this section helpful?

What made this section unhelpful for you?

Guides

Authentication

To ensure seamless and secure interactions, we've implemented API keys. These keys grant authorized access to our services, safeguarding your application and data. Obtaining your unique API key is a straightforward process – simply sign up, generate your key in your account dashboard, and include it in your API requests' headers. This extra layer of authentication guarantees a smooth and protected experience, enabling you to harness the power of our system with confidence. You can generate API keys programmatically through our Management API or seamlessly via our intuitive dashboard. But it doesn't stop there! Elevate control by assigning specific feature permissions to each API key. This means you decide which areas of our system your key can unlock. Whether you're creating, editing, or managing keys, our API-first approach empowers you to shape your experience. Use it is super easy, just add the header X-API-KEY with the value of your API-KEY and done!.


Was this section helpful?

What made this section unhelpful for you?

Errors

In this guide, we will explore potential challenges that you might come across and discuss effective strategies for managing them. By addressing these issues, you can significantly enhance the efficiency of your development process.


Trace Request

On every response and webhook transaction a header is sent to track it, the name of this header is X-Trace-Id.

This information will be ask on any support request made so we can speed up the solution of any error ocurred.

Error response

If the request has not been successful, you will receive a JSON with the following attributes:

error_code: The error code that has occurred.

message: A message that describes the error.


Example

error_codestring
messagestring
Was this section helpful?

What made this section unhelpful for you?

1 2 3 4 { "error_code": "API_ERROR", "message": "Access denied. The API Key is not authorized to do this operation." }

Error Codes

200-201

The request executed had finished successfully.

400

The request is not valid, due to some unpredictable error. If you are using a POST, PUT or PATCH request, check that the body is valid. If you are using a GET request, check that the parameters are correct. If you are using a DELETE request, check the path.

401

The API Key is not authorized to do this operation. Check that your API Key had been correctly configured.

404

The requested resource does not exist. Some of the information needed to do this request was not found.

412

The request was not completed because an internal validation was not fulfilled. Check that the body of the request is valid.

500

Our APIs are currently experiencing issues. This is an error on our side, we will check as soon as possible. Please contact support and try again later.

Was this section helpful?

What made this section unhelpful for you?

API

Webhooks

Webhooks provide real-time notifications for API events, enabling your platform to receive timely updates about specific activities. Our system sends these notifications to a designated endpoint within your hosted environment, which is configured to adeptly receive and process them.

Leverage webhooks to promptly obtain information about critical API events. These events include occurrences external to your system, such as a new deposit in an MPC wallet or a card transaction at a point-of-sale (POS) terminal.To seamlessly receive and process webhook-enabled events, you need to establish and configure a webhook endpoint within your environment.

Each webhook request consists of a common part and a custom payload specific to the event being communicated. The common part includes standard information such as the event type, sub-type, status and a unique Id of of the notification, while the custom payload contains detailed data relevant to the specific event.

Field

Type

Description

operation

String

Indicator of the operation being informed

sub_operation

String

Indicator of the activity of the operation being informed

operation_id

String

Unique identifier of the operation

status

String

Status of the transaction. Possible values: SUCCESS | CANCELLED | FAILED

reason

String

If the status is FAILED the reason of why ll appear here

data

Object

Variable payload of the notification. The content of this will change depending of the notification type. Complete specification of this will be inside each notification page.

General payload example:

JSON
{
"operation": "TREASURY",
"sub_operation": "DEPOSIT",
"operation_id": "ca0c57d2-b1c9-4bcd-9d5d-8d361cad6fddds1c",
"status": "FINISHED",
"data": { }
}