FlowRelay FlowRelay Docs Shopify Flow Search /
All docs pages

START

USE CASES

SET UP

OPERATE

RECOVER

AGENT ACCESS

REFERENCE

Reference

OpenAPI

Generated OpenAPI schema discovery and public contract placement for Agent Operations.

On this page

Schema location #

Use the OpenAPI document for exact field names, types, and shapes. Use these prose docs for product meaning, delivery semantics, and safe guidance. The two are complementary; neither replaces the other.

ArtifactURL
OpenAPI JSONhttps://docs.flowrelay.app/reference/openapi/agent-operations.openapi.json
Trigger mapping referencehttps://docs.flowrelay.app/setup/trigger-variants-and-event-mapping/
Choose an agent missionhttps://docs.flowrelay.app/agent-access/agent-mission-playbooks/
Availability and refusalshttps://docs.flowrelay.app/agent-access/availability-and-refusals/
Agent orientationhttps://docs.flowrelay.app/agent-access/agent-orientation/
Docs indexhttps://docs.flowrelay.app/llms.txt

Versioning #

The current generated Agent Operations schema version is 2026-06-17. Generated schema versions move with the canonical operation registry; agents re-read the manifest and OpenAPI document before relying on cached operation names or schemas.

Operation names #

Use generated operation IDs for clients. The public manifest operation is getAgentOperationsManifest. Keep examples synthetic and redacted, and do not include real tokens, authentication headers, event bodies, or customer records.

Examples #

The generated OpenAPI document includes synthetic request examples for endpoint creation, replay preview and execution, diagnostics sharing, support preview and submit, expansion requests, and feature requests. Use those schema-bound examples instead of copying production requests.

Inspect the generated examples Lists operation IDs that include request-body examples.
curl -s https://docs.flowrelay.app/reference/openapi/agent-operations.openapi.json \
  | jq -r '.paths[][] | select(.operationId) | .operationId'

Generated clients #

If you generate a client from the schema, preserve refusal handling, idempotency keys, docs URLs in refusals, and the action-preview lifecycle. These behaviors are part of the Agent Operations contract and must remain visible in your client.

Local docs search