Clara-Backend
  1. Flask Backend Boilerplate
Clara-Backend
  • Clara-Backend
    • Get Started
    • Quickstart (Rest API)
    • Quickstart (MCP Server)
    • Auth
      • Register
      • Google OAuth
      • Login
      • Logout
      • Change Password
      • Send OTP
      • Activate
      • Enable 2FA
      • Disable 2FA
    • User
      • View
      • Update
    • API Key
      • View
      • Reset
    • Transaction
      • View All
      • View
    • Task
      • View All
      • View
    • Agent
      • Supported Attachments
      • Analysis
    • Stripe
      • Rate
      • Portal
      • Buy
    • Misc
      • Health
      • Version
  • Flask Backend Boilerplate
    • Get Started
    • Quickstart
    • Auth
      • Register
      • Google OAuth
      • Login
      • Logout
      • Change Password
      • Send OTP
      • Activate
      • Enable 2FA
      • Disable 2FA
    • User
      • View
      • Update
    • Transaction
      • View All
      • View
    • Stripe
      • Rate
      • Portal
      • Buy
    • Misc
      • Health
      • Version
  1. Flask Backend Boilerplate

Quickstart

2.1 Authorization#

The boilerplate supports several authentication methods. Basic Auth (email and password) is only used to generate a User Token. Once you have the User Token, you should use it as a Bearer token for all user-level requests.
You can authenticate using:
• a Basic Auth
• a User Token (generated via Basic Auth),
• a Public API Key, or
• a Private API Key.
Each endpoint specifies which auth methods it accepts, and you must include the correct one in the Authorization header.
Just paste your API key into the header as:
HeaderValueTypeRole
AuthorizationBasic BASE64(email:password)Basic AuthUser
AuthorizationBearer USER_TOKENBearer TokenUser
AuthorizationPUBLIC_API_KEYAPI KeyPublic
AuthorizationPRIVATE_API_KEYAPI KeyPrivate
Once that’s set, you’re ready to make authenticated requests to any endpoint.

2.2 Rate Limits#

API rate limits apply per API key. The boilerplate allows rate limiting with Flask Limiter.
If your users go over this limit, or exceed their plan’s usage limits, the API will return an HTTP 429 - Too Many Requests response.
Keeping their usage within the limit ensures smooth and reliable performance for everyone.
Modified at 2025-12-10 10:32:59
Previous
Get Started
Next
Auth
Built with