If I'm reading that right, you have the entire "Authentication: Bearer <token>" as a value when it might need to be separated as a key/value. I'm a novice at this kind of stuff for sure, but I have API with similar auth I do in Postman that is set up similar to this.
So, as your key, your would put "Authentication" and as your value "Bearer <token>"

Sorry if that is how you have it and I'm misunderstanding.
------------------------------
Mike DeMarco
Video Production Engineer
Las Vegas United States
------------------------------
Original Message:
Sent: 04-26-2022 18:03
From: Sean Henry
Subject: Xpression Datalinq and Authentication Bearer tokens
Hey all, I'm attempting to pull JSON data from an HTTP API source that requires token authentication. The API docs state that this can be done using an Authentication: Bearer token header, but I'm only receiving "User not signed in" errors in the return JSON object. How would I format the custom header in the Xpression Datalinq Server configuration? The API docs give this example:Authentication: Bearer <token>
And that's how I have it formatted in the Value section of the Custom Header section, but no luck.
I've confirmed that I can fully access the API data with this curl command on the Xpression machine via command line:
curl -H "Authorization: Bearer <token here>" "website here"
Any thoughts on what I might be getting wrong with the Custom Header?
Thanks
------------------------------
Sean Henry
------------------------------