1XBet docs
    • Intro
    • Deposit
      • Get Orders
        GET
      • Create Order
        POST
    • Withdrawal
      • Get Withdrawal Orders
        GET
      • Create Withdrawal Order
        POST
    • Schemas
      • Schemas
        • OrderCreatedResponse
        • OrderListResponse
        • UserInfo
        • OrderPostRequest
        • WithdrawalOrderPostRequest
        • OrderGetResponse

    Intro

    ElMomento API Integration#

    Welcome, This document provides all the necessary information to integrate with the ElMomento API. Our goal is to make this process as smooth and straightforward as possible.
    This API is designed to handle pay-ins (deposits) and pay-outs (withdrawals) for your clients in a secure and efficient manner. Please review this document carefully and do not hesitate to contact our support team if you have any questions.

    Getting Started#

    API Environments#

    We provide two environments for integration: a Sandbox for testing and a live Production environment.
    EnvironmentBase URLDescription
    Sandboxhttps://pruebas.elmomento.io/apiUse this environment for all initial development and testing. No real transactions will be processed.
    Productionhttps://api.trade.elmomento.io/apiThe live environment for processing real user requests.

    Authentication#

    All requests to the ElMomento API must be authenticated. Authentication is handled via a unique Secret Key and a request signature.
    Your Secret Key is a confidential token that has been provided to you directly by our team. Never expose this key in client-side code or public repositories.
    Every API request requires an M-Signature header. This signature is used to verify the integrity and authenticity of the request body.
    How to Generate the Signature:
    The signature is generated using HMAC-SHA512 with a timestamp to prevent replay attacks. The message to sign varies based on the HTTP method:
    GET requests: HMAC-SHA512(secret, timestamp)
    POST/PUT/PATCH requests: HMAC-SHA512(secret, timestamp + body)
    Required Headers:
    Signature: The HMAC-SHA512 hex digest
    X-Timestamp: Unix timestamp in seconds
    Timestamp Validation:
    The timestamp must be within 30 seconds of the server time to prevent replay attacks.

    Signature Generation Example (Python)#

    Here is a simple Python function demonstrating how to generate the required signature:

    Signature Generation Example (Node/JS)#

    Making Requests#

    Required Headers#

    All API requests must include the following headers:
    HeaderValueDescription
    Content-Typeapplication/jsonIndicates the request body format is JSON.
    Signature[HMAC SHA512 HASH]The signature generated from the request body.
    X-Timestamp1766825847Current timestamp used in the signature generation.

    Example Request (curl)#

    Here is a full example of how to make a request to a sample endpoint.

    First, generate the signature for your request body#

    Let's assume the generated signature is: 1a2b3c...
    curl -X POST \
 https://pruebas.elmomento.io/api/1xbet/orders/ \
 -H 'Content-Type: application/json' \
 -H 'Signature: 1a2b3c...' \
 -d '{  
 "amount": 500,  
 "orderID": "Somerandomstring",  
 "currency": "DOP",  
 "callback_url": "https://google.com",  
 "request": {  
    "email": "ceterasddsare@hotmail.com",  
    "id_number": "00100000001"  
  }  
 }'

    Endpoints Overview#

    Below is an overview of the available endpoints.

    Deposit#

    Handles deposit orders for clients who want to increase their balance.
    POST /1xbet/orders/
    Create Order: Creates a new deposit order.
    GET /1xbet/orders/
    Get Orders: Returns a list of existing deposit orders.

    Withdrawal#

    Handles withdrawal orders for clients who want to withdraw their balance.
    POST /1xbet/withdrawalorders/
    Create Withdrawal Order: Creates a new withdrawal order.
    GET /1xbet/withdrawalorders/
    Get Withdrawal Orders: Returns a list of existing withdrawal orders.

    Rate Limiting#

    To ensure API stability for all our clients, we enforce a rate limit of 1000 requests per hour. If you exceed this limit, you will receive an HTTP 429 Too Many Requests response.

    Error Handling#

    Our API uses standard HTTP status codes to indicate the success or failure of a request.
    2xx codes indicate success.
    4xx codes indicate a client-side error (e.g., bad request, authentication failure).
    5xx codes indicate a server-side error.
    In the case of an error (4xx or 5xx), the response body will contain a JSON object with more details:

    Support#

    If you encounter any issues or have questions during your integration, please contact our technical support team at ceterre@ourord.com.
    Modified at 2026-02-11 02:29:17
    Next
    Get Orders
    Built with