Describe a device approval request without revealing unauthenticated organization data

GET/api/mcp/device
No API key
Veyra Docs TeamUpdated Version 3 · History

Describe a device approval request without revealing unauthenticated organization data.

Authorization

No API key is needed: the token or id in the path, or the request's own signature, authenticates the call. How keys work.

Responses

200SuccessThe request worked; the body holds the result.
400Bad requestThe request is malformed or failed validation. details names each field that failed.
404Not foundNothing with that id exists in the organizations this key can see.

Errors return {"error": "..."}, often with a code and details. See errors and limits.

MCP gateway