Skip to main content
This directory provides the complete HTTP REST API specification for all public and internal endpoints exposed across the Hoox edge microservices stack.

🔒 Security & Authorization Headers

All internal calls between workers (via V8 Service Bindings) must provide the standard internal authentication header:
Public webhook and dashboard endpoints use cookie authorization or custom API keys:
  • Webhook Ingestion: Authenticated using the apiKey property inside the JSON payload.
  • Telegram webhook: Authenticated via the secure token path: /telegram/<TELEGRAM_WEBHOOK_SECRET>.

🚀 Ingress Webhook Endpoints (workers/hoox)

The public gateway acts as the primary firewall and entry entryway for all external trade signals.

A. Ingest Signal Webhook

Receives TradingView alerts or automated cURL signals.
  • Path: /webhook
  • Method: POST
  • JSON Payload:
  • Success Response (200 OK):

B. Proactive Health Diagnostics

  • Path: /health
  • Method: GET
  • Success Response (200 OK):

🗄️ Database Service Endpoints (workers/d1-worker)

The d1-worker serves as a private, internal SQL proxy database.

A. Execute Single SQL Statement

  • Path: /query
  • Method: POST
  • JSON Payload:
  • Success Response (200 OK):

B. Execute Transactional Batch Statements

  • Path: /batch
  • Method: POST
  • JSON Payload:
  • Success Response (200 OK):

🧠 AI Risk & Chat Endpoints (workers/agent-worker)

Bridges background risk audits and multi-provider AI chat streams.

A. Conversational Chat Stream (Server-Sent Events)

  • Path: /agent/chat
  • Method: POST
  • Headers: Accept: text/event-stream
  • JSON Payload:
  • Success Response: Emits standard text/event-stream updates, terminating with data: [DONE].

B. Multimodal AI Vision Audit

  • Path: /agent/vision
  • Method: POST
  • JSON Payload:
  • Success Response (200 OK):

🔗 Next Steps

Last modified on June 17, 2026