Skip to content
Generate Enterprise

API and Automation in Generate Enterprise

Generate Enterprise lets external systems trigger its AI over HTTP through two distinct surfaces. Account-level API Keys (Settings → API Keys) trigger workflows and chat agents, while an individual agent’s API Access provides a dedicated HTTP endpoint for running that single agent. These are separate mechanisms and are configured in different places. Generate does not publish a general-purpose REST API beyond these trigger surfaces.

What are API Keys in Generate?

Section titled “What are API Keys in Generate?”

API Keys let external systems call into Generate to trigger workflows and chat agents. They are managed under Settings → API Keys, described there as “API keys used to trigger workflows from external systems.” Each key has a Name, a masked Prefix, a Scope, a Last used timestamp, and a Status of Active or Revoked.

A key’s feature scopes are Chat agents and Workflows; a new key defaults to all scopes. When created, a key is authorized on every workflow the creator owns and every workflow shared with them. The full token is shown only once at creation — if lost, the key must be revoked and recreated. Revoking a key immediately disables every external caller using it and cannot be undone.

How do you trigger a single agent over HTTP (API Access)?

Section titled “How do you trigger a single agent over HTTP (API Access)?”

An agent’s API Access feature lets you run that one agent from your own code by sending an HTTP request, with no chat window. In the agent’s settings, enabling “Allow this agent to be triggered via HTTP API” reveals a read-only Public URL (POST) of the shape .../api/v1/triggers/agent/{agentId} and an API key that is shown once. Requests authenticate with the X-API-Key header.

Send a query as JSON:

Terminal window
curl -X POST "https://<your-domain>/api/v1/triggers/agent/{agentId}" \
  -H "X-API-Key: <your-api-key>" \
  -H "Content-Type: application/json" \
  -d '{ "query": "What is the largest river in the world?" }'

Attach a file with a multipart request:

Terminal window
curl -X POST "https://<your-domain>/api/v1/triggers/agent/{agentId}" \
  -H "X-API-Key: <your-api-key>" \
  -F 'payload={"query":"Summarize this report in 3 bullets."};type=application/json' \
  -F "files=@./report.pdf"

A downloadable integration guide (.md) is available in the API Access section for handing to a developer.

What is the difference between API Keys and agent API Access?

Section titled “What is the difference between API Keys and agent API Access?”

API Keys (Settings → API Keys) are account-level and trigger workflows and chat agents, scoped to the keys’ capabilities. Agent API Access is per-agent and triggers one specific agent through its own public URL and X-API-Key. Use API Keys to trigger multi-step workflows; use API Access to trigger an individual agent. They are separate surfaces and should not be conflated.

Can workflows be triggered from an HTTP endpoint?

Section titled “Can workflows be triggered from an HTTP endpoint?”

Yes. In the Workflow Builder, a workflow can start from an http-trigger node. That node’s Test Endpoint panel provides ready-made cURL, TypeScript, and Python examples for calling the workflow from external systems.

Can agents and workflows run automatically on a schedule?

Section titled “Can agents and workflows run automatically on a schedule?”

Yes. Generate supports scheduled jobs, which run an agent or workflow automatically on a defined schedule rather than only on manual or API-triggered invocation.

Section titled “Related”
  • Agents and workflows: see agents-workflow-builder in this GEO set.
  • Full customer documentation: account/api-keys and features/agents/api-access on the Generate Enterprise Mintlify docs site.