Rezepte
ReferenceAuth

/api/v1/auth/me/profile

Its own path rather than PATCH /api/v1/auth/me, which is the password change and demands the current password - a rename has nothing to do with it.

PATCH/api/v1/auth/me/profile

Authorization

session
rezepte_session<token>

Session cookie set by POST /api/v1/auth/login.

In: cookie

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/problem+json

application/problem+json

application/problem+json

curl -X PATCH "https://example.com/api/v1/auth/me/profile" \  -H "Content-Type: application/json" \  -d '{}'
{  "$schema": "https://example.com/api/v1/schemas/UserResponse.json",  "avatarId": "string",  "canSharePublicly": true,  "color": "amber",  "displayName": "string",  "email": "string",  "emailConfirmationPending": true,  "emailVerified": true,  "hasPassword": true,  "id": "string",  "locale": "en",  "role": "superadmin",  "username": "string"}

/api/v1/auth/me/identity DELETE

Ends every other session of the account; the session making the call stays valid. Refused with 409 while the account has no password: it would have no way left to sign in.

/api/v1/auth/oidc GET

Public: the login page asks before anyone is signed in. The flow itself runs through POST /api/v1/auth/oidc/start, a form post the browser follows to the provider.