Skip to main content
Thygon exposes a unified HTTP REST API that powers the CLI, the Console UI, and the SDK. If you are building integrations in languages other than TypeScript, you can communicate with these endpoints directly.

​
Base paths

By default, the API gateway maps base paths to their respective microservices:
ServiceBase pathExample endpoint
IAM/authGET https://api.thygon.com/auth/me
Event/eventsPOST https://api.thygon.com/events
Entity/entitiesGET https://api.thygon.com/entities/:id
Integration/integrationsPOST https://api.thygon.com/integrations/:id/trigger
Workflow/workflowsPOST https://api.thygon.com/workflows
Runtime/runsGET https://api.thygon.com/runs/:id

​
Authentication

Authorize all requests using an API Key passed in the Authorization header. 
Authorization: Bearer your-api-key
Content-Type: application/json

​
Error handling

The API returns standard HTTP status codes to indicate the success or failure of an request:
  • 200 / 201: The request succeeded.
  • 400: Invalid payload or query parameters.
  • 401: Missing or invalid API key.
  • 403: Insufficient permissions to access the resource.
  • 404: The requested resource or endpoint does not exist.
  • 500: An internal server error occurred.