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. API keys

                                API keys

                                Team API keys for shared automation: scoped when you create them, always expiring, and revocable by admins.

                                An API key is the right credential for automation the whole team relies on, like a CI job that uploads every night. To create one, open Settings, then API keys under team settings, and choose Create API key. Describe what the key is for, pick an expiration date, choose its permissions and which projects it can reach, then generate it. Copy the key straight away: it's shown only once.

                                A few things are worth knowing about how keys behave:

                                • A key belongs to the team member who created it, and it's stored only as a hash.
                                • Its permissions are fixed at creation. What a key can actually do is the overlap between those permissions and what its owner may do, so a key never exceeds its owner.
                                • Every key has an expiration date.
                                • Team admins with apikey:manage can see and revoke every key in the team. Revoking takes effect immediately.
                                curl -H "Authorization: Bearer $EMBODIFLOW_KEY" https://api.embodiflow.io/v1/projects
                                Previous

                                Authentication overview

                                Next

                                Personal access tokens