FlowManner
Chat
Sign InGet Started
Flowmanner
Menu
  • Chat
  • Agents
  • Pricing
  • Docs
  • About
Products
  • Workflows
  • Templates
  • Changelog
  • Missions
Resources
  • Blog
  • API Reference
More
  • Careers
  • Contact
  • Security
  • Start
    • Quickstart
    • Your First Mission
    • Your First Eval
  • How-to
    • Connect Your Own Keys (BYOK)
    • Switch Models Per Task
    • Publish a Template
    • Run Evaluations
    • Chat with Artifacts & Previews
    • Automate via the API
    • Webhooks & Triggers
  • Concepts
    • Glossary
    • Execution Model
    • Models & Routing
    • Sandboxes & Previews
    • Memory & Privacy
    • Trust Model
  • Reference
    • Reference · API
      • Authentication
      • Missions & Runs
      • Chat & Sandboxes
      • Blueprints, Graphs & Templates
      • Evaluations & Feedback
      • Marketplace & Community
      • Files & Exports
      • Integrations & Webhooks
      • Agents & Orchestration
      • Auth, Workspaces & Billing
      • Memory & Knowledge
      • Notifications
      • Platform Services
    • Errors
    • Models
    • Limits

Automate via the API

Log in, hold a bearer token, page through results, handle errors.

  1. Get a token 
    POST /api/auth/login
{ "username_or_email": "…", "password": "…" }
    Access tokens live ~15 minutes; refresh tokens renew them (Authentication).
  2. Call v2 endpoints with Authorization: Bearer <token>. Prefer the v2 surface — every response uses the standard envelope (Errors): { data, meta: { request_id, timestamp }, error }.
  3. Page deterministically: list responses wrap items with total/page/per_page/pages; pass per_page explicitly rather than relying on defaults (20).
  4. Retry correctly: back off on 429/5xx, never blind-retry 4xx; log meta.request_id for support.
  5. Webhooks instead of polling? See Webhooks & Triggers — HMAC signatures let you verify Flowmanner's calls.

Last updated 2026-08-25 (git-derived)