Appearance
Confirm an uploaded avatar
POST /v1/me/avatar/confirm
- Operation ID:
confirmAvatar - Tags: Profile
- Base URL:
http://localhost:8787
Points the profile at the uploaded object and deletes the caller's other avatar objects so only one is stored.
Workflow: Integration guide.
Authentication: Platform user Bearer JWT. Acts only on the caller's own data.
Authentication
- Auth: Platform user Bearer JWT (
Authorization: Bearer <access_token>).
Request body
Required: yes.
Content type: application/json
Schema: object
| Field | Type | Required | Description |
|---|---|---|---|
path | string | yes | Min length: 1. Max length: 200 |
Responses
200
Avatar set.
- Header
x-request-id: Request identifier; quote it when reporting an error. Content type:application/json
Schema: object
| Field | Type | Required | Description |
|---|---|---|---|
avatar_url | string | null | yes | - |
Errors
400
Request validation failed. validation_failed: path is outside the caller's folder or the object was not uploaded.
- Header
x-request-id: Request identifier; quote it when reporting an error. Content type:application/json
Schema: object (ValidationErrorBody) | object (ErrorBody)
| Field | Type | Required | Description |
|---|---|---|---|
(variant 1).success | boolean | yes | One of: false |
(variant 1).error | object | yes | - |
(variant 1).error.name | string | yes | One of: "ZodError" |
(variant 1).error.issues | object[] | yes | - |
(variant 1).error.issues[].code | string | yes | - |
(variant 1).error.issues[].path | (string | number)[] | yes | - |
(variant 1).error.issues[].message | string | yes | - |
(variant 2).error | string | yes | Stable machine-readable error code, e.g. forbidden, not_found. |
(variant 2).details | any | no | Optional structured context. For 403 it is { perm }. |
Request validation
json
{
"success": false,
"error": {
"name": "ZodError",
"issues": [
{
"code": "custom",
"path": [
"field"
],
"message": "Invalid value"
}
]
}
}Application error
json
{
"error": "validation_failed"
}401
Missing, malformed, expired or wrong-audience Bearer token (missing_token, invalid_token, invalid_audience).
- Header
x-request-id: Request identifier; quote it when reporting an error. Content type:application/json
Schema: object (ErrorBody)
| Field | Type | Required | Description |
|---|---|---|---|
error | string | yes | Stable machine-readable error code, e.g. forbidden, not_found. |
details | any | no | Optional structured context. For 403 it is { perm }. |
Error response
json
{
"error": "missing_token"
}500
Unexpected server error (internal). No details are returned.
- Header
x-request-id: Request identifier; quote it when reporting an error. Content type:application/json
Schema: object (ErrorBody), fields as described above.
Error response
json
{
"error": "internal"
}503
Maintenance can refuse this write before authentication (degraded blocks session start and checkout; lockdown blocks other public/user writes).
- Header
x-request-id: Request identifier; quote it when reporting an error. - Header
Retry-After: Maintenance retry delay in seconds; present for panic_mode. Example:30. Content type:application/json
Schema: object (MaintenanceErrorBody)
| Field | Type | Required | Description |
|---|---|---|---|
error | string | yes | One of: "panic_mode" |
level | string | yes | One of: "degraded", "lockdown" |
reason | string | null | yes | - |
Maintenance lockdown
json
{
"error": "panic_mode",
"level": "lockdown",
"reason": "Scheduled maintenance"
}Examples
curl
bash
curl -X POST 'http://localhost:8787/v1/me/avatar/confirm' \
-H "Authorization: Bearer $ACCESS_TOKEN" \
-H 'Content-Type: application/json' \
--data '{"path":"example"}'TypeScript
ts
const accessToken = process.env.ACCESS_TOKEN; // user JWT from your sign-in flow
const response = await fetch("http://localhost:8787/v1/me/avatar/confirm", {
method: "POST",
headers: {
"Authorization": `Bearer ${accessToken}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
"path": "example"
}),
});
if (!response.ok) throw new Error(`HTTP ${response.status}: ${await response.text()}`);
const data = response.status === 204 || response.status === 205
? undefined
: response.headers.get("content-type")?.includes("json")
? await response.json()
: await response.text();