Skip to main content
Use ConnectionConfig to configure authentication and endpoints for all SDK clients.

PersonalToken

  • Use for backend-only or administrative operations where a human- or service-owned token is appropriate (e.g., CI/CD, provisioning, migrations).
  • Best when you need elevated privileges across projects or organization-level APIs.
  • Never embed in client-side code. Store securely (vault/secret manager) and rotate regularly.
    Authorization
    string
    Personal token for administrative APIs.
    AuthId
    string
    Rapida Auth ID performing the action.
    ProjectId
    string
    Rapida project ID for scoping requests.

WithSDK

  • Use for typical application integrations (server-side web apps, backend services) using a project-scoped API key.
  • Safer to use in application servers than personal tokens; permissions are limited to the project.
  • Do not ship in public client apps without a proxy; prefer server-to-server.
    ApiKey
    string
    Project API key used for typical app integrations.
    UserId
    string
    Optional user identifier to propagate in requests.