I'll tell you, these days I prefer to parse out API calls in a script. There's often some sort of transformation or other operation I need to do rather than just pull out a variable, and I want my step to be visible rather than part of the API call. It's a personal preference -- you'll see others say to just manipulate output within the connector.
But in your case you just want a simple variable! It should work! I don't' see any sort of array in the response that would call for a change of your value format either.
If I were standing over your shoulder and we were working through this, I'm sure we'd figure it out by trial and error. It's much harder trying to suggest things from this far away!
Here's what I'd do if I needed to do more complex things against that API call: I'd set the API call connector to "return raw data" in the transformation screen. I'd use DEBUG to get the actual full response from the API. I'd plug that response into ChatGPT and tell it that I need to extract the token variable. Then I'd plug chatGPT's script into Orchestrator's scripting template, with 1 input - responseJSON, and 1 output - tokenVar. Then hook up all the plumbing there and move along, since the scripting method removes any guesswork.