Branta
  • Branta API
    • Start Here
  • Guardrail
    • Authentication
    • Environments
    • Name, Image and Block Height
    • V1
      • Adding Payments
      • Displaying Payments
      • Getting Payments
      • Indexing Payments
    • Guardrail+
  • More
    • API Status
    • Key Rotation
  • BTCPayServer Plugin
Powered by GitBook
On this page
  1. Guardrail

Authentication

Branta endpoints require an API key to authenticate. Two API Keys are issued - staging and production.

Include API_KEY in the HTTP Header to authenticate.

Your API keys carry sensitive privileges so they should be kept secure at all times. Do not commit them to code or share them publicly.

(NOTE - DO NOT USE PRODUCTION API KEYS ON THESE PAGES. ONLY ENTER STAGING API KEYS ON THIS WEBSITE FOR TESTING PURPOSES.)

curl -X POST -H "Content-Type: application/json" \
-H "API_KEY: mykey" \
 -d '{
 "payment": {
 "ttl": "86400",
 "payment": "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa"}
 }' \
 https://staging.branta.pro/v1/payments

IP Whitelisting

To enhance security and prevent unauthorized access, Branta allows you to whitelist specific IP addresses when making POST requests to our servers.

Why Use IP Whitelisting?

  • Enhanced Security – Restrict API access to trusted sources, reducing the risk of unauthorized requests.

  • Compliance & Data Protection – Ensure only approved servers can interact with sensitive data, helping meet security and regulatory requirements.

How It Works

  1. Provide a list of IP addresses that are authorized to send POST requests.

  2. Requests from non-whitelisted IPs will be automatically rejected.

  3. You can update your IP whitelist at any time.

PreviousGuardrailNextEnvironments

Last updated 27 days ago