Forum Discussion
Hi Aidon,
You don't need Authentication, User Name and password in Pipeline Webhook request. You may want to add content type to headers. That should work.
Please don't share your user token here.
Thank you
------------------------------
Razi D.
WEP Forms
http://www.destatechs.com
------------------------------
Hi Razi,
I made your recommended changes, but still getting the following error message. I've also deleted the old user token and replaced with a new one. Thanks for the heads up on that.
------------------------------
Aidon Olligschlager |
Flight Operations Technical Support
Pentastar Aviation
Waterford MI
[email protected] | 248-202-9587
------------------------------
- AidonOlligschla2 years agoQrew Cadet
This worked! Thank you all for your assistance. Much appreciated!
------------------------------
Aidon Olligschlager |
Flight Operations Technical Support
Pentastar Aviation
Waterford MI
[email protected] | 248-202-9587
------------------------------ - ChayceDuncan2 years agoQrew Captain
When I did this long ago I ended up getting and actual auth ticket using api_authenticate, but by looking at that start of this thread you need to put QB-USER-TOKEN before your actual token in the body. So:
BODY:
QB-USER-TOKEN xxxxxxxx
------------------------------
Chayce Duncan
------------------------------ - ChayceDuncan2 years agoQrew Captain
Sorry not the body - I meant the Headers. Try putting QB-USER-TOKEN before your actual token in header. Mistype on my part.
------------------------------
Chayce Duncan
------------------------------ - RaziD_2 years agoQrew Cadet
Please see both attached images, This is how I just set up the webhook(in Pipeline) and it works. I am not sure if you are missing anything.
Thank you
------------------------------
Razi D.
WEP Forms
http://www.destatechs.com
------------------------------ - ChayceDuncan2 years agoQrew Captain
Yes, looks like QB-USER-TOKEN is the primary missing element.
------------------------------
Chayce Duncan
------------------------------