---
title: "Create a new Monerium integration"
method: POST
path: "/api/v1/integrations/monerium"
tags: ["IBAN"]
---

# Create a new Monerium integration

`POST /api/v1/integrations/monerium`

Creates a new Monerium integration for the authenticated user and associates it with the authenticated user's EOA address.
All operations on Monerium are done through their API, this endpoint is just a way to reuse the GP KYC to open an account on Monerium.

- If the user does not have a Monerium account, this endpoint will create a new one and associate it with the authenticated user's EOA address.
- If the user already has a Monerium account, you do not need to call this endpoint again.

Just use the Monerium API directly to request access to the user's monerium account.
Check their documentation for more information: https://monerium.dev/api-docs/v2

## Request body

- object
  - `signature` string — Signature of the message "I hereby declare that I am the address owner." This signature is created by signing the message with the user's wallet. The exact message can be retrieved from the /api/v1/ibans/signing-message endpoint. The signature is used to verify ownership of the address on Monerium. Format: Ethereum signature string (e.g., "0x1234...").

## Response `200`

Successfully created a new Monerium integration

- MoneriumIntegrationResponse
  - `data` object
    - `success` boolean, required — Indicates whether the Monerium integration was successfully created
    - `status` number, required — HTTP status code of the operation
    - `description` string, required — Human-readable description of the operation result
    - `responseData` object, nullable — Raw response data from Monerium API (only present on errors)
    - `moneriumProfileId` string, nullable — The Monerium profile ID assigned to the user (only present on success)
    - `iban` string, nullable — The assigned IBAN number (only present on success)
    - `bic` string, nullable — The assigned BIC code (only present on success)
    - `responseHeaders` object, nullable — Headers from the Monerium API response (only present on errors)

## Other responses

- `400` — Validation error on Monerium side.
- `401` — Unauthorized Error
- `404` — User not found.
- `422` — Validation errors on GP side.
- `500` — Internal Server Error

---

[API](https://skmtc.net/gnosispay/apis/gnosispay-api.md) · [All operations](https://skmtc.net/gnosispay/apis/gnosispay-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/gnosispay/gnosispay-api/versions/e0a09962c187/schema)