Webhook routes

devsleeper

Say I have a webhook below:
<base braincloud webhook url>

Now, I want to call this, but at the same time I want to append a route depending on the state:

/game/join
or
/game/create

How can I manage this in braincloud when the server (Photon) that is attempting to call the webhook can't be modified and is essentially a blackbox to customers?

Does braincloud support this type of "routing" from a single base url?

JasonL

No, dynamic routing is not supported by BrainCloud webhook yet. You will have to use two different URLs.

devsleeper

That clears up some confusion! Thanks.

devsleeper

Unfortunately, I won't be able to use BrainCloud with Photon webhooks at all which is a shame, your end-point names also don't allow '/'s so I can't even create two different URLs.

JasonL

How about passing the slug as a parameter along with the webhook URL? This will allow your script to parse the parameter and perform actions accordingly.

Paul Winterhalder

For what its worth - plenty of apps on brainCloud are using Photon - so I would expect it is possible... (though as you say - our webhooks are a single route each. As @JasonL indicates - you should be able to indicate the different functions via a parameter?)

devsleeper

This post is deleted!

devsleeper

Apparently what I thought was working was actually just photon's default behavior when it doesn't receive the appropriate response from the webhook.

@Paul-Winterhalder
Plenty may use photon but the Quantum 3 sdk is quite new and uses a new webhooks plugin that is restricted to a single base url and some static settings.. the way it works is appending the request type to the base url, ie join/create which I can't just include as a parameter since this happens dynamically within the photon server outside my control.

While I have had success using postman to receive an expected returned result and logs accordingly in BrainCloud, I don't actually see Any of photon's attempts to contact the Same url in the logs, which I'm guessing makes this a no-go?

I would at least expect to see something log in the Unreadable Requests section of logs? The fact it's ignoring photon completely but not postman is really bizarre, or maybe intended as the above comments indicate.. either way I need this functionality so that's unfortunate.

https://docs.braincloudservers.com/api/cc/writingscripts/webhooks
config example

Paul Winterhalder

Hi @devsleeper - if you contact us through the chat widget we can go through your logs with you and see if we can get to the bottom of this. Thanks.