Evyn Ecclesia : Yes Tod…NP.
I’m currently testing my PD Webhook on my PayHere*(PH)* “Sandbox” Account.
Whenever PH sends a request, I’ve setup
a PD Trigger to get it, then run next steps.
So the very next step is an Auth Step for PH, --where I’m getting the error (Ref Screenshot #1).
But based on PH’s Documentation (Ref Screenshots #2 & #3), I may be using the wrong key, or failing to enter some additional required info into this step.
Tod Sacerdoti : Yes, I was able replicate. If you want to make calls to the sandbox API, you need to change https://app.payhere.co/api/v1/user to <https://sandbox.payhere.co/api/v1/user>
Evyn Ecclesia : Ok. Still getting “401 error”
Ref (2) Screenshots of my TestRun @ 11:07am.
Note in 1st Screenshot: Before the run, SandBox is added to Link
Note in 2nd Screenshot: After the run, Sandbox has been removed from
Link, and errors out.
Evyn Ecclesia : I Created a new Auth Link named “SANDBOX REV” -which picks up your newly added changes,
but once the step is run, it looks like it’s reverting back to the old Auth Link named “SANDBOX.”
…And there appears to be a discrepancy btwn
my Connected Accounts vs Auth Step connect.
Shouldn’t the SANDBOX REV be showing up
as “connected” in the Connected Accts Screenshot?
Shouldn’t updates to connections at the step level, be automatically updated and show up
in the Connected Accts Menu Option?
Hopes this sheds more light onto the problem,
as it appears that the Accts Menu Option
is overriding the connection being declared
in the Auth Step at run Time.