Overview
Webhooks let you push event notifications from Ekso to external systems in real time. When something happens in your tenant — an item is created, a user is deleted, a board is added — Ekso sends an HTTP POST request to the URL you configure for that event.
You manage webhooks under Settings > Hooks.
Event types
Ekso supports nine webhook events across four resource types:
Item events
| Event | Fires when |
|---|
item-add | A new item is created |
item-update | An existing item is modified |
item-delete | An item is deleted |
User events
| Event | Fires when |
|---|
user-add | A new user is added to the tenant |
user-delete | A user is removed from the tenant |
Container events
| Event | Fires when |
|---|
container-add | A new container is created |
container-delete | A container is deleted |
Board events
| Event | Fires when |
|---|
board-add | A new board is created |
board-delete | A board is deleted |
Configuration
Each event type maps to a single HTTP endpoint URL. To receive notifications for an event, set the URL where Ekso should send the POST request.
You can configure different URLs for different events, or point multiple events at the same endpoint and use the event type in the payload to distinguish them.
If you only need a subset of events, leave the others unconfigured. Ekso only sends requests for events that have a URL assigned.
Webhook configuration requires admin permissions. Only users with the Manage role can view or update webhook settings.
Webhooks are event-driven and fire immediately when a resource changes. For scheduled, condition-based alerts (e.g., “notify me when items are overdue”), see Notifications. Use cases
Common integrations built with webhooks include:
- Slack or Teams notifications — post a message when a high-priority item is created
- External ticketing sync — mirror item changes to a third-party system
- Audit logging — forward all events to a centralized log or SIEM
- CI/CD triggers — kick off a build when an item moves to a specific status
