Authentication
API keys created from organization settings receive all developer scopes by
default. Existing keys created before this API shipped need
aops:read /
aops:write added in organization settings.organizationId in the query (GET) or JSON body (writes). Do not send organizationId for API-key requests.
aopId in the path (and aop_id in JSON responses) is the OmniCommerce AOP id from /app/{organizationId}/aops.
Execute an AOP
1
Start the run
The AOP id is in the path. Optional
user_inputs go in the JSON body. The response returns immediately with a thread_id.2
Poll until terminal
running, completed, failed. Terminal responses include conversation messages by default. Pass include_messages=true to force messages while the run is still in progress.Request body
Response
trigger_type is always api for this endpoint. sync_server is the OmniCommerce origin and can be ignored.
Poll status
conversation_asset includes linked_aops, last_message, and metadata.run_status (including awaiting_approval).
Retry a failed run
user_inputs replace the original values; omit them to reuse the failed run’s inputs. Response:
Create an AOP
[[ placeholder ]] in the prompt for execution-time inputs. Omni validates a name of at least 2 characters and a prompt of at least 10 characters.
Response includes
aop_id, title, status: "created", and parent_folder_id.
Read and overwrite config
GET returns prompt, agentId, structured_inputs (computed from placeholders), structured_output, and notification settings.
PUT updates provided fields only. Omitted fields keep their current values. Send user_notification_configs: null to clear notification overrides.