Overview
User requests are responsible for handling any actions on the current user, and you must be signed in as that User. A reference to a Client object needs to be sent with each request, through a Clerk-issued JWT. This step is handled automatically if you're using one Clerk's Session Management.
GET
/v1/me
PATCH
/v1/me
GET
/v1/me/email_addresses
POST
/v1/me/email_addresses
GET
/v1/me/email_addresses/:id
POST
/v1/me/email_addresses/:id/send_verification_email
POST
/v1/me/email_addresses/:id/verify
DEL
/v1/me/email_addresses/:id
GET
/v1/me/phone_numbers
POST
/v1/me/phone_numbers
GET
/v1/me/phone_numbers/:id
PATCH
/v1/me/phone_numbers/:id
POST
/v1/me/phone_numbers/:id/send_verification_sms
POST
/v1/me/phone_numbers/:id/verify
DEL
/v1/me/sessions/:id
POST
/v1/me/profile_image
GET
/v1/me/sessions
GET
/v1/me/sessions/active
POST
/v1/me/sessions/:id/revoke
POST
/v1/me/tokens
GET
/v1/me/organizations
POST
/v1/me/totp
POST
/v1/me/totp/attempt_verification
DEL
/v1/me/totp
POST
/v1/me/backup_codes
Last modified 11mo ago