Bring Your Own Guardrails
Portkey supports bringing your own Guardrail using a custom webhook:
Add Webhook
as a Guardrail Check and setup any Guardrail Actions along with it. This is useful when you have an existing custom guardrail pipeline in your app and you are sending your LLM inputs or outputs to it for sync or async evaluation. Bring that onto Portkey’s Gateway, make it production-grade, and enforce LLM behavior in real-time, easily.
How Custom Webhook Works
In the Guardrail check, Portkey expects your Webhook URL
and any headers
(including Authorization
) you need to send.
Headers
Headers here should be a JSON object, like below:
Portkey makes a POST
request to your webhook URL and expects two objects in the response: verdict
and data
.
Custom Metadata
You can send any Metadata to your Webhook URL with Portkey’s Metadata header.
When you make the request, Portkey will automatically forward all your metadata info to your Webhook URL. More about Metadata here
Webhook Response
Portkey expects two objects: verdict
and data
Object | Type | Required? |
---|---|---|
verdict | boolean | Yes |
data | any | No |
Here’s a sample webhook response:
Check out the Webhook implementation here:
Based on the verdict value, the Guardrail Check will PASS
or FAIL
, and will have subsequent impact on the Guardrail Actions you’ve set.
The webhook request automatically time out after 3 seconds -this can not be changed. So, if a webhook request times out, the Guardrail verdict will return PASS
for that request.
Head over to the Portkey Discord community if you are building out custom webhooks and need any help!
Was this page helpful?