Get current user
Returns the authenticated DigitalStack user, current account, active membership, and authentication context.
GET
/api/v1/mePurpose
Resolve who a credential represents and which DigitalStack account currently bounds the request.
Security
Identity and account coordinates are always derived from the authenticated principal. Query parameters, request bodies, and custom identity headers cannot select another user or account.
Recommended uses
- Confirm an API key or OAuth token before starting a workflow.
- Display the signed-in user and active account in an integration UI.
- Troubleshoot account selection and granted scopes without exposing secret credential data.
Not intended for
- Listing users, memberships, or accounts.
- Changing a profile, membership, role, or active account.
- Inspecting API key material, OAuth token claims, or internal authorization policy.
Authorization
profile:readapi key scoperequiredRequired scope when calling with an API key.
Request
curl -X GET "https://www.digitalstack360.com/api/v1/me" \
-H "Authorization: Bearer $DS_API_KEY"Examples use a placeholder key from your environment. Store your key in $DS_API_KEY — never commit it.
Response
200 OK
{
"data": {
"user": {
"id": "7f33c8b3-3fa0-4a0d-8cd7-cad51b19487f",
"email": "[email protected]",
"displayName": "Alex Morgan",
"avatarUrl": null,
"status": "active"
},
"account": {
"id": "d1762e70-7745-4cc3-80db-841da4a3504d",
"name": "Example Workspace"
},
"membership": {
"role": "admin",
"status": "active"
},
"authentication": {
"method": "api_key",
"scopes": [
"profile:read"
]
}
},
"meta": {
"requestId": "9a28983d-689b-4d97-913f-0d44911c5d20"
}
}Errors
401
missing_authNo credentials provided
401
invalid_api_keyAPI key is invalid or revoked
403
scope_insufficientCredential lacks profile:read scope
500
internal_errorCurrent identity context could not be loaded