API Reference

curl -X POST 'https://api.example.com/api/triggers/webhook/flow_123' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"event":"order.created","data":{"orderId":"12345"}}'

{ "status": "accepted", "triggerId": "trig_abc" }

Phinite APIs let external systems start Agent Graph runs—typically via triggers—using workspace API keys or OAuth tokens your admin provisions.

Authentication

string

required

Bearer token for API authentication. Format: Bearer YOUR_API_KEY

Never expose API keys in client-side code or public repos. Store keys in env variables or your secret manager.

Example: Trigger a webhook

curl -X POST 'https://api.example.com/api/triggers/webhook/flow_123' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"event":"order.created","data":{"orderId":"12345"}}'

{ "status": "accepted", "triggerId": "trig_abc" }

Create and deploy an Agent Graph with a trigger.
Issue an API key under workspace API keys (role permitting).
Call the trigger endpoint from your system; monitor runs in observability.

Trigger APIs execute deployed graph builds—not draft Studio saves. Build and assign an environment before testing production traffic.

1. Getting Started

2. Agent Graphs

3. Graph Studio (Workflow Builder)

4. Tools & Dev Studio

5. Configure

6. Ship

7. Observability & Billing

8. User Management

9. Reference

10. Troubleshooting & Support

Authentication

Example: Trigger a webhook

​Authentication

​Example: Trigger a webhook

​Related flows

​Related

Authentication

Example: Trigger a webhook

Related flows

Related