LogoLogo
  • Introduction
  • Overview
    • What are cryptocurrencies
    • Why accept crypto
    • Our products
      • Payment Gateway
      • Earnings on deposit
      • Manual Invoices
      • Payment & Donation button
      • White Label
      • Affiliate program
      • Demo Shop
  • Getting started
    • Basics
      • What is an Invoice?
      • Accepting Payments
      • Withdrawing Your Funds from OMY Payments
      • Security and Transparency
  • API
    • Overview
    • Authentication
    • API Endpoints
      • Get Merchant Assets
      • Create Invoice
      • Create Invoice by Crypto
      • Get Invoice Data
      • Withdraw Asset
    • Callbacks
    • Common issues
  • No-code Integration
    • Overview
    • Getting Started with No‑Code Integration
  • How to Create Payment Links
  • Advanced Use Cases and Best Practices for No‑Code Integration
  • Legal
    • Terms of Use
Powered by GitBook
On this page
  1. API

Authentication

PreviousOverviewNextAPI Endpoints

Last updated 16 days ago

To use the API, merchants must obtain an API key from their personal account. You can retrieve your API key by logging in at: . Without a valid API key, all requests will be rejected.

Include the API key in the header of each request as follows:

curl -X GET -H "apiKey: yourApiKey" https://api.omypayments.com/

If the API key is missing, the server will respond with:

{
    "success": false,
    "message": "Missing api key",
    "statusCode": 0
}

Invoice Statuses

  • new: Invoice created; awaiting asset selection. (Typically, there is a limited time for asset selection, after which the invoice is canceled.)

  • pending: Asset selected; awaiting payment. (Payment must be made within a set timeframe, otherwise the invoice is canceled.)

  • rejected: Invoice canceled; payment cannot be made.

  • finished: Invoice successfully paid; funds have been credited to the merchant’s account.

https://dashboard.omypayments.com/