Reading it
endpoint
X-Tylon-Workspace header and refuses none — this is where the ids
for that header come from, so a version of it that demanded one would be a
door whose key is behind the door.
string
The public half of the credential. Safe in a log — it is not what
authenticates.
string
What it was called when it was issued, and what it signs its writes with.
A card it creates says
createdBy: the deploy script.string[]
read, or read and write. Writing with only read is 403.object[]
Every board it reaches, with the role it holds on each. This is the listing:
workspaceId is exactly what the X-Tylon-Workspace header accepts, and
nothing else is.string | null
Which board served the call. Always
null here, because this route answers
with the list rather than out of it.What to do with it
Choosing a board
How the ids above go into the header, what happens when you leave it out,
and why a name is refused where an id belongs.
Writing
What the
write scope and the role in boards let this credential do.