It's normal to just get OK when you hit the URL. Fenix is just responding with "OK - I heard your request". See the YouTube Video.

from fenix.

So... why is the URL for the report builder shown? As a user, why do I need it? I saw it and naturally figured I'd needed to see it. ;)

from fenix.

(Report Builder == Request Browser)

from fenix.

It's more like a Webhook Payload Browser, similar to Request Bin. Perhaps it needs a better name that's more reflective of this. The URL is provided as an endpoint for testing webhooks. In the video, I copy/paste the URL into a Github webhook and trigger the event.

The public address allows you to test payloads coming from remote services. The private one allows you to test your own webhooks. For example, I'm working on a Node.js system that fires a lot of webhooks that pull data from a MongoDB. I like to see the data that's passed in the webhook POST body, and I accomplish that "offline" by pointing my local node script to my local webhook receiver.

from fenix.

Oh - that makes a LOT more sense. :)

On Mon, Jun 9, 2014 at 10:23 PM, Corey Butler [email protected]
wrote:

It's more like a Webhook Payload Browser, similar to Request Bin. Perhaps
it needs a better name that's more reflective of this. The URL is provided
as an endpoint for testing webhooks. In the video, I copy/paste the URL
into a Github webhook and trigger the event.

The public address allows you to test payloads coming from remote
services. The private one allows you to test your own webhooks. For
example, I'm working on a Node.js system that fires a lot of webhooks that
pull data from a MongoDB. I like to see the data that's passed in the
webhook POST body, and I accomplish that "offline" by pointing my local
node script to my local webhook receiver.

—
Reply to this email directly or view it on GitHub
#26 (comment).

Raymond Camden, Web Developer for Adobe

Email : [email protected]
Blog : www.raymondcamden.com
Twitter: raymondcamden

from fenix.