Is there an easy way to authenticate more complex ...
# how-do-i
n
Is there an easy way to authenticate more complex API calls? I'm working on some tooling for my developer experience, and it appears that I can pass an auth token in the header (e.g.
{ authorization: "token XXXxxxXXX" }
in some of my calls to
api.graphite.dev
, however more complex requests (e.g.
api.graphite.dev/v1/graphite/mutation/mq-toggle-pause
) appear to follow a more complex flow that tokens might not be useful for
p
(If applicable) To help us more clearly understand what you're trying to do, please provide additional details about: - Screenshots / debug logs / list of commands you've tried to run so far - Your workflow - Current state
hey Nicholas, the auth token is intended to be used with Graphite CLI. I don't think API endpoints like that one are intended for consumption external to Graphite app
n
Hmm, since I can access these both through the API, is there any documented differences between how to authenticate with this separate set of endpoints, such as a different auth endpoint that I would have to make a request to first?
The thought that I am having is that if there's an endpoint such as
check-auth
that I can fetch a different key from to make these requests