DebitLlama
  • DebitLlama Documentation
  • What is wallet abstraction?
  • Account Creation and Checkout flow
  • How DebitLlama compares to others?
  • Process payments via Solvers
  • Payment Intents
    • ZKP Implementation details
    • Smart Contract Implementation details
    • Client Side Implementation
    • Security first. A little game theory.
  • Creating Accounts
  • Comparing Account types
  • Accepting Payments
    • Checkout Redirect
    • Managing your items
    • Checkout page
  • Fees
  • Passkeys
  • Rest Api v1
    • Creating Access Tokens
      • What is Bearer Authentication?
    • Schema
    • Networks and Currencies
    • /api/v1
    • /api/v1/accounts
    • /api/v1/accounts/[commitment]
    • /api/v1/payment_intents
    • /api/v1/payment_intents/[slug]
    • /api/v1/items
    • /api/v1/items/[slug]
    • Configuring Webhooks
      • Request Schema
    • Zapier Integration
  • Try it out on Testnet
  • Slack
Powered by GitBook
On this page
  1. Rest Api v1
  2. Creating Access Tokens

What is Bearer Authentication?

Learn how to use the access tokens you created

The Access Tokens created on the front-end are Bearer Tokens, they grant access to the API for the bearer and will be used to identify their accounts.

DebitLlama access tokens are generated using the following schema:

debitllama.APIv1_<random>

The access token names always start with the name of the application and the API version so they are easy to tell apart from other tokens you might be using.

To write data using the API you need to use the Authorization header for your requests like the following example:

Authorization: Bearer <accesstoken>

Here is a simple Fetch function written in javascript to get you started posting to the API:

await fetch(`https://debitllama.com/api/v1/payment_intents/${paymentIntent}`, {
    method: "POST",
    headers: {
      "Authorization": `Bearer ${accesstoken}`,
      "Content-Type": "application/json"
    },
    body,
})

PreviousCreating Access TokensNextSchema

Last updated 1 year ago