FlamPix Gateway API
    FlamPix Gateway API
    • 📜 API Overview
    • ⚠️ API Base URL Migration Notice ⚠️
    • Docs
      • 🔑 Authentication & HMAC Signing
      • 🪝 Webhook
      • 🧵 Deposit Status Strings
      • 🚦 API Limits
    • Raiz
      • Create Deposit
        POST
      • Get Deposit Status
        GET
      • Get User Info
        GET
      • Health Check
        GET
      • Transaction Status Update
    • Schemas
      • Customer
      • DepositRequest
      • DepositResponse
      • UserInfoResponse
      • WebhookPayload

    ⚠️ API Base URL Migration Notice ⚠️

    Summary#

    ✅ Two URLs available until 01/02/2026
    ⚠️ After this date, only api.flampix.com will be supported
    🚀 New integrations should use the new URL immediately
    📈 Migration is required to support high-throughput, enterprise-grade traffic
    If you have any questions or need assistance during the transition, our technical team is available to support your migration.

    Coexistence Period#

    Both API base URLs will coexist and remain fully operational until February 1st, 2026:
    https://www.flampix.com/gt/api/v1
    https://api.flampix.com/gt/api/v1
    During this period, no functional differences are expected between the two endpoints.

    Mandatory Migration After 01/02/2026#

    Starting February 1st, 2026, the API will undergo a full and exclusive migration:
    The legacy domain www.flampix.com will be deprecated for API traffic.
    All API requests must be directed to:
    https://api.flampix.com/gt/api/v1
    Requests made to the old URL after this date may fail or be blocked without further notice.

    Recommendation for New Integrations#

    If you do not yet have a production system consuming the FlamPix API, it is strongly recommended that you start directly with the new base URL:
    https://api.flampix.com/gt/api/v1
    This avoids any future migration effort and ensures long-term stability.

    Technical Rationale#

    With sustained growth in transaction volume, FlamPix is migrating its API infrastructure to a dedicated, high-performance environment. This change allows us to:
    Scale horizontally without service degradation
    Isolate API workloads from web traffic
    Improve latency and network routing
    Increase overall reliability and observability
    Target capacity: up to 1,200 transactions per minute, without bottlenecks or performance degradation.
    Modified at 2025-12-25 20:29:31
    Previous
    📜 API Overview
    Next
    🔑 Authentication & HMAC Signing
    Built with