The Traffic Inspector has been discontinued.

Existing accounts will have access until June 19th, 2018.

Read the full announcement for more details →


Request Captures (Request Bins)

Captured requests are useful for inspecting the request data your HTTP client or webhook provider are generating without forwarding the data on to a destination URL.

Each of your buckets has a capture URL that consists of a bucket key and the Runscope hostname. Here's an example capture URL (replace bucket_key with the bucket key you'll receive after signing up for an account):

All requests made to the URL are captured and stored in the associated bucket and available for inspection. For free accounts, view captured requests in your "All Traffic" stream. Paid accounts have an additional Captures stream view that will display only requests made to capture URLs.

Note: If you're looking to capture and inspect an API or webhook service call that is relayed to a destination endpoint, check out Gateway URLs.

Webhook Debugging

Capturing requests is particularly useful when building a webhook or HTTP push notification integration.

Here's how:

  • Register the capture URL for your desired bucket with the webhook event publisher.
  • Generate some test alerts sent to the capture URL to inspect the data being sent by the remote service.
  • Once you're ready to receive the hooks on your own server, create a Gateway URL with your server's domain and update the webhook settings with your provider.
  • All of the webhook events sent to your server will be logged in Runscope, along with the response generated by your server.