Child Item

Webhook integration -- Challenge is inserted at the start of the URL parameters

Hi All,

I'm working on a Dropbox integration, but am running into a problem.

The URL I wish to receive the request on has parameters already within the URL. When I try send the verification I find that the challenge is inserted as the first parameter, which breaks the request on the receiving end.

eg. URL is: https://<WEBSITE>/portal.cgi?http_service=webhook&whitepaper=dropbox_app, but the verification is sent to GET https://<WEBSITE>/portal.cgi?challenge=<CHALLENGE_CODE>&http_service=webhook&whitepaper=dropbox_app

I'm trying to work within a prebuilt framework, where the location I wish to receive the webhook calls is determined by the parameters, and the current functionality breaks the request.

This is more of a feature request I guess, but if anyone has an idea, I'd love to hear!

Find more posts tagged with

API

Abuse

Accepted answers

Здравко

@LukeyB wrote:
...
I'm trying to work within a prebuilt framework, where the location I wish to receive the webhook calls is determined by the parameters, and the current functionality breaks the request.
...

Hi @LukeyB,

That sounds very strange! 🤔 Generally order of URL parameters shouldn't have matter. Any HTTP query receiver shouldn't expect particular parameter order! Only existence of mandatory parameters and/or disagreement with unwanted might be expected.

For "a prebuilt framework", that sounds like a bug. Ask environment provider for assistance related to possible settings/preferences, so would be able tune/fix that. 🤷 Or read framework documentation more careful. Alternative can be usage of some of Dropbox SDKs (or your own extension) within your framework if possible; most environments provide way for extensions.

Good luck.

All comments

Здравко

@LukeyB wrote:
...
I'm trying to work within a prebuilt framework, where the location I wish to receive the webhook calls is determined by the parameters, and the current functionality breaks the request.
...

Hi @LukeyB,

Good luck.

Greg-DB

@LukeyB Здравко is correct; the URL parameter order is not supposed to matter, and so the Dropbox webhook system does not guarantee any particular URL parameter order. You'll need to troubleshoot this with the framework itself.

LukeyB

Thanks for the help guys, appreciated! I'll see what I can do on the other end.