Monolo API Docs
  • Introduction
  • Authorization
    • API Keys Management
    • Signature
    • Code snippets
  • Environments
  • Errors
  • Expired Payment
  • Changelog
  • References
    • Crypto payments
      • πŸ”’Request crypto payment
      • πŸ”’Add payment details
      • πŸ”’Get payment data
      • Fetch deposit amounts metadata
    • Crypto withdrawals
      • Request withdrawal metadata
      • πŸ”’Request crypto withdrawal
      • πŸ”’Request crypto withdrawal approval status
    • Wallet Addresses
      • Validate address
    • Businesses
      • πŸ”’Get business by ID
      • πŸ”’Get business deposits
      • πŸ”’Get business withdrawals
      • πŸ”’Get business balance
    • Callbacks
      • Deposit received notification
      • Withdrawal broadcast notification
      • Withdrawal approved/rejected notification
    • Currencies & Fees
      • Get all currencies
      • Get exchange rates [crypto to fiat]
      • Get exchange rates [fiat to fiat]
      • Get exchange rates [any currency to any currency]
Powered by GitBook
On this page

Authorization

The Monolo API's authorization scheme

PreviousIntroductionNextAPI Keys Management

Last updated 6 months ago

When authorizing against the Monolo REST API, one must provide a standard HTTP Authorization header in the following format:

'Authorization: FRX-API api-key=<your_api_key>,
                        signature=<signature>,
                        timestamp=<unix_timestamp>'

consist of an API key and an API secret, forming a pair together. The key must be passed with each request in the Authorization header’s API-Key component and the API secret is used for the generation of the component. The Timestamp component must be an integer value representing the current in milliseconds.

All requests that require authorization are labelled with this icon πŸ”’

API credentials
Signature
UNIX epoch time