Test Okta Webhooks Locally (Receive Okta Webhooks on localhost)

You are building a Okta integration and you need to watch your handler react to a real event. The problem hits immediately: Okta will only POST to a public URL, and your handler is running on localhost:8080. Okta has no way to reach it.

The usual workarounds are slow. Deploying to a staging environment for every code change kills your iteration speed. Copying a sample payload out of the docs into curl gives you a guess at the real request, not the exact headers and body Okta actually sends. What you really want is to test Okta webhooks locally — real events, hitting your local handler, on a URL that does not change every time you restart.

This guide shows how to do exactly that.

Why testing Okta webhooks locally is tricky

A webhook is just an HTTP request that Okta sends to a URL when something changes. Okta lives on the public internet; your dev machine usually does not. It sits behind a router, a corporate firewall, or both, with no public IP and no inbound ports open.

So you need something in the middle: a public endpoint Okta can hit that relays each request down to your laptop without you opening a single firewall port. That is what Webhook Relay does — and unlike a random tunnel URL, the endpoint is stable, so you configure Okta once and never touch it again.

Step 1: Inspect the real payload with Webhook Bin

Before you write any handler code, find out what Okta actually sends. Open the free Webhook Bin — no signup — and you get an instant public URL.

1. Copy the Webhook Bin URL.
2. In the Okta Admin Console, go to Workflow → Event Hooks → Create Event Hook, set the URL, choose the events, and add an authentication header secret. Okta then sends a one-time verification request.
3. Trigger a real event and inspect the captured request.

You will see the full body and every header. Okta first sends a one-time verification GET with an X-Okta-Verification-Challenge header — respond with { "verification": "<that value>" }. Event deliveries are JSON with an eventType and a data.events array of System Log events.

Now you know the exact shape of the data before writing a line of code. For more on this approach, see How to test webhooks and What is a webhook.

Step 2: Forward the events to localhost with the relay agent

Once you know the payload, route those same events into your local handler. Sign up for Webhook Relay, install the relay agent (CLI or Docker), and create a bucket — say okta. The bucket gives you a stable public input endpoint.

Start forwarding to your local server:

relay forward --bucket okta http://localhost:8080/webhook

The agent opens an outbound connection to Webhook Relay and streams every incoming request down to http://localhost:8080/webhook. Because the connection is outbound, there are no firewall ports to open and no public IP needed — this works from your laptop, behind a corporate proxy, or inside a Kubernetes cluster. Running in Docker? The same command works in the official webhookrelay/webhookrelayd image. Full details are in the localhost forwarding docs.

Now point the Okta webhook at your Webhook Relay endpoint (or create it there from the start), trigger an event, and watch it arrive on localhost.

Okta-specific configuration and quirks

A few Okta details worth knowing:

• Verification GET: echo the X-Okta-Verification-Challenge as {"verification": "..."} or the hook won't verify.
• No HMAC: secure it with the custom authentication header secret you configure.
• Payload: eventType + a data.events array of System Log events.

Step 3: Verify the Okta webhook signature

Okta Event Hooks don't sign the body with an HMAC. Security is two-part: (1) a one-time verification GET carrying an X-Okta-Verification-Challenge header, which you answer by returning { "verification": "<value>" }; and (2) a custom authentication header (for example Authorization: <secret>) that you set when creating the hook and Okta sends on every event — check it matches before trusting the payload.

To sanity-check an HMAC implementation, paste a captured body, your secret, and the received signature into the free HMAC signature verifier. For language-specific code and the common pitfalls (reading the body after a JSON parser has already consumed it, timing-safe comparison), read Verify a webhook signature.

Replay and iterate

This is where local development gets fast:

• Replay from Webhook Relay — past requests are stored on your bucket, so you can resend a captured event against your handler without touching Okta at all.
• Iterate on your handler by editing code and replaying the same delivery until it behaves correctly. No commits, no pushes, no deploys just to test a single code path.
• Keep relay forward running while you work — events stream straight to localhost as you trigger them in Okta.

Because the Webhook Relay endpoint is stable, you can stop and restart the agent, reboot your machine, or come back next week — the Okta configuration never needs to change.

Get started

1. Inspect the real payload in the free Webhook Bin — no signup needed.
2. Create a Webhook Relay account, install the agent, and run relay forward --bucket okta http://localhost:8080/webhook.
3. Point your Okta webhook at the stable endpoint, trigger an event, and watch it hit localhost.

You will be testing real Okta events against your local handler in a few minutes — no deploys, no open firewall ports, and a URL you configure exactly once.