Me
Return the signed-in management-plane user. This route reads only the authenticated principal itself and therefore requires no organization or project permission. Only an OIDC user JWT is admitted on this route; dtno_ organization API keys are not.
user_jwtAuthorizationBearer <token>OIDC access token of a signed-in user (the dashboard/CLI login) used on the management plane: /me, /orgs*, /projects*, /invitations*, /roles, billing, audit, API-key, and service-account routes. Every management operation documents the org/project permission the authenticated member must hold.
Signed-in user
application/json- response
email*stringid*stringuuidname?string|nullcurl -X GET 'https://example.com/me'{ "email": "string", "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "name": "string"}Whether the signed-in user has accepted the privacy-policy version the platform currently requires, with the version and a link to the policy text. Reads only the authenticated principal, so it needs no organization or project permission. Only an OIDC user JWT is admitted on this route; dtno_ organization API keys are not.
user_jwtAuthorizationBearer <token>OIDC access token of a signed-in user (the dashboard/CLI login) used on the management plane: /me, /orgs*, /projects*, /invitations*, /roles, billing, audit, API-key, and service-account routes. Every management operation documents the org/project permission the authenticated member must hold.
Consent status
application/json- response
The signed-in user's standing against the required privacy policy.
accepted*booleanWhether the user has accepted the required version. A client should
prompt for consent only on an explicit false.
accepted_at?|date-timeaccepted_version?|Version the user last accepted, whichever version is required now.
url?|Where the current policy text is published; null when no consent is
required.
version?|Version the platform currently requires; null when it requires no
consent, in which case accepted is always true.
curl -X GET 'https://example.com/me/privacy-policy'{ "accepted": true, "accepted_at": "2019-08-24T14:15:22Z", "accepted_version": "string", "url": "string", "version": "string"}Record that the signed-in user accepts the named privacy-policy version. The version must be the one the platform currently requires (as returned by GET /me/privacy-policy); any other value is refused with 409 so consent is only ever recorded against the text the user was shown. Idempotent: accepting an already-accepted version only refreshes the acceptance time. Only an OIDC user JWT is admitted on this route; dtno_ organization API keys are not.
user_jwtAuthorizationBearer <token>OIDC access token of a signed-in user (the dashboard/CLI login) used on the management plane: /me, /orgs*, /projects*, /invitations*, /roles, billing, audit, API-key, and service-account routes. Every management operation documents the org/project permission the authenticated member must hold.
application/json- body
Body of POST /me/privacy-policy/accept: the version the user was shown
and accepts. It must equal the version the platform requires now, so an
acceptance made against a status read from an older configuration (a
rolling restart that changed the version, or a stale dashboard tab) is
refused instead of being recorded as consent to text the user never saw.
version*stringAcceptance recorded
curl -X POST 'https://example.com/me/privacy-policy/accept' \ -H 'Content-Type: application/json' \ -d '{ "version": "string"}'