Skip to main content
PATCH
/
user
Update user profile
curl --request PATCH \
  --url https://api.spike.ac/user \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "<string>",
  "notification_preferences": {
    "email_notifications": true,
    "marketing_emails": true
  }
}
'
{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "email": "jsmith@example.com",
  "name": "<string>",
  "created_at": "<string>",
  "updated_at": "<string>",
  "two_factor_enabled": true,
  "org_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "org_name": "<string>",
  "org_slug": "<string>",
  "short_code": "<string>"
}

Documentation Index

Fetch the complete documentation index at: https://doc.spike.ac/docs/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

Authentication using either a Supabase JWT token or an API key (prefixed with sk_). Both token types are passed as Bearer tokens in the Authorization header.

Body

application/json
​
name
string

User display name

Maximum string length: 100
​
notification_preferences
object

Notification preferences

Response

Updated user profile

​
id
string<uuid>
required
​
email
string<email>
required
​
name
string | null
required
​
created_at
string
required
​
updated_at
string
required
​
two_factor_enabled
boolean
required
​
org_id
string<uuid> | null
required
​
org_name
string | null
required
​
org_slug
string | null
required
​
short_code
string | null
required