← Back to Documentation
API & Automation
Webhook Notes
Plan webhook-style automation around documented portal and billing events.
Key Steps
- Use documented portal and billing webhooks only where they are part of the deployment path.
- Validate signatures before trusting any webhook payload.
- Keep future automation idempotent because retries can happen.
Article Scope
This guide focuses on the operational steps needed to run Orchestris with team access, provider control, and predictable usage.
Handler design
- Validate the signature and timestamp.
- Reject payloads that do not match expected schema.
- Return quickly after persisting the event or enqueueing work.
Retry safety
- Use event IDs to deduplicate retries.
- Do not assume event delivery order across unrelated resources.
- Make side effects safe to run more than once.
Operations
- Monitor delivery failures.
- Rotate webhook secrets through a documented process.
- Keep endpoint logs long enough to investigate missed automation.
Related Topics
API & Automation
Agent API Gateway
Connect OpenAI-compatible agent tools to Orchestris Server while keeping model access, quota, and usage controls in one place.
API & Automation
REST API
Use REST endpoints for authentication, licensing, deployments, billing, and operational automation.
API & Automation
Client Streaming Notes
Understand the native streaming path used by connected clients and private deployments.