EmbodiFlowDocs
Get startedDataWorkflows and algorithmsTraining and deploymentDeveloper reference
  • Developer reference

Authentication

  • Authentication overview
  • API keys
  • Personal access tokens
  • Browser sessions

REST API

  • Using the REST API
  • All endpoints
  • Projects
    • Recordings
      • Upload
        • Episodes and versions
          • Annotation
            • Quality and tasks
              • Search
                • Workflows
                  • Algorithms
                    • Models
                      • Artifacts and export
                        • Billing and usage
                          • Team and governance
                            • Account and notifications
                              • Webhook endpoints

                                Events

                                • Outbound events
                                • Signature verification

                                Tools

                                • CLI
                                • SDK
                                • MCP

                                Updates

                                • Changelog

                                © 2026 EmbodiFlow

                                llms.txtOpenAPI JSON
                                1. Developer reference
                                2. Authentication
                                3. Authentication overview

                                Authentication overview

                                Which credential to use where: browser sessions, personal access tokens and API keys.

                                EmbodiFlow has three kinds of credential, each made for one job. Whichever you use, the server works out your team from the credential itself, so you never pass a team in a request.

                                CredentialUse it for
                                Browser sessionThe console. It's an HttpOnly cookie; don't reuse it in scripts.
                                Personal access tokenYour own CLI and integrations.
                                API keyTeam-wide automation, managed by admins.

                                Scripts send the credential as Authorization: Bearer <token>. You choose a credential's permissions when you create it, and they can't be widened later. If a script needs more, create a new credential.

                                Previous

                                Developer reference

                                Next

                                API keys