Gilito AIHelp

Webhooks & Integrations

Webhooks let you receive real-time notifications from Gilito at your own HTTP endpoints. When specific events occur — such as a signal change, an agent trigger, or a portfolio update — Gilito sends an HTTP POST request to the URL you configure, allowing you to build custom automations and integrations.

Setting Up Webhook Endpoints

Step 1: Navigate to Webhook Settings

Go to Settings > API & Webhooks > Webhooks.

Step 2: Add a New Endpoint

Click Add Webhook and enter:

  • URL — the HTTPS endpoint that will receive webhook payloads
  • Description — an optional label for your reference (e.g., "Slack notifications" or "Trading bot")
  • Events — select which events should trigger this webhook

Step 3: Save and Copy the Secret

After saving, Gilito generates a webhook secret — a unique key used to verify that incoming requests are genuinely from Gilito. Copy this secret and store it securely in your application. It is shown only once.

Supported Events

You can subscribe to the following webhook events:

signal.changed
Fired when a signal changes for any asset in your watchlist or portfolio. The payload includes the asset ticker, previous signal, new signal, and the strategy backing the new signal.
agent.triggered
Fired when one of your agents' conditions are met and the agent triggers. The payload includes the agent name, which conditions matched, the affected assets, and the action taken.
portfolio.updated
Fired when your portfolio positions change — either through manual trades, auto-synced trades, or broker position syncing. The payload includes the portfolio name, the changed positions, and the action type (buy, sell, sync).
alert.fired
Fired when a configured alert condition is met. The payload includes the alert name, the condition that triggered, the asset or value involved, and the timestamp.
Note: You can subscribe a single endpoint to multiple events, or create separate endpoints for different event types. Each webhook request includes an event_type field so your handler can distinguish between them.

HMAC Signature Verification

Every webhook request includes an X-Gilito-Signature header containing an HMAC-SHA256 signature of the request body, signed with your webhook secret. You should verify this signature on every incoming request to confirm it originated from Gilito:

  1. Read the raw request body (before parsing JSON)
  2. Compute HMAC-SHA256 of the body using your webhook secret as the key
  3. Compare the computed signature with the value in the X-Gilito-Signature header
  4. If they match, the request is authentic. If not, reject it
Security: Always verify webhook signatures in production. Without verification, anyone who discovers your endpoint URL could send fake events to your application.

Testing Webhooks

Before relying on webhooks in production, test them to ensure your endpoint handles payloads correctly:

  • Send test event — from the webhook settings page, click Send Test next to any webhook to send a sample payload with mock data
  • View delivery log — Gilito logs the last 30 days of webhook deliveries, including the payload, response status code, and any errors. Use this to debug failed deliveries
  • Retry failed deliveries — if your endpoint was temporarily down, you can manually retry failed webhook deliveries from the log

Gilito automatically retries failed deliveries (non-2xx responses) up to 3 times with exponential backoff. If all retries fail, the delivery is marked as failed in the log.

Zapier & Make Integration

If you use automation platforms like Zapier or Make (formerly Integromat), you can connect Gilito webhooks to hundreds of other apps without writing any code:

  • Zapier: Create a Zap with a "Webhooks by Zapier" trigger, use the "Catch Hook" option, and paste the generated URL as your Gilito webhook endpoint
  • Make: Create a scenario with a "Webhooks" module as the trigger, select "Custom webhook," and paste the URL into your Gilito webhook settings

Common automation examples:

  • Send a Slack message when a signal changes to Buy
  • Log agent triggers to a Google Sheet for record-keeping
  • Send a Telegram notification when a portfolio position changes
  • Create a Notion database entry for each fired alert
Tip: Start with a simple integration (e.g., Slack notifications for signal changes) to verify the connection works, then build more complex automations as needed. Use the test event feature to verify your Zapier/Make setup before going live.

Was this article helpful?

Still need help?

Browse these resources or use the chat widget in the bottom-right corner.

FAQTroubleshootingAPI Docs
← Feature AvailabilityCommon Issues →