Webhook APIs allow third-party platforms to automatically push data into Quixy applications—without any manual intervention from end users. Once configured, any event or data capture in an external system can instantly trigger a POST request into a designated Quixy app, streamlining information flow and eliminating redundancy.
To consume a Quixy Webhook API, the external system must authenticate using a Bearer Token.
Note
Only Quixy users with Integration Access can generate and view the required token. Organizational Admin must assign this permission when creating a user or by editing an existing user profile.
Follow the steps below to enable secure data reception from a third-party system. Before generating a Webhook:
1. Create an application with all the fields that will receive data from the external platform.
2. Complete the app design and move to the Publish step.
3. Enable Webhook by toggling the switch.
Tip
The app must be published with Webhook enabled for the API details to be generated.
4. Go to Admin Menu → Apps → Manage Apps.
5. Locate and open the app you just published.
6. Ensure the Webhook toggle is still enabled.
7. Click the “Click Here” link to open the Webhook API configuration popup.
8. Retrieve Webhook Details, the popup displays all integration details required by the third-party system:
| # | Field | Description |
|---|---|---|
| 1 | API URL | Endpoint used by external platforms to send POST requests into Quixy. |
| 2 | JSON Structure | A ready-to-use payload schema generated from the app fields. |
| 3 | Bearer Token | Authentication token that must be sent in the request header. |
| 4 | Secret Key (Optional) | Additional credential for validating signatures or supporting header-based authentication. |
Important
All credentials must be securely stored and referenced by the external system for every API call.
Once the third-party platform is configured with:
Webhook automatically push data into the Quixy app using an HTTP POST request.
Integration
Request Header
POST /webhook/app/incoming-data HTTP/1.1
Host: quixy.com
Authorization: Bearer <Your_Bearer_Token>
Content-Type: application/jsonExample Payload
{
"email_subject": "System Alert",
"email_body": "Threshold exceeded on Node 12",
"received_date": "2025-07-22T10:35:00Z" }