Skip to content
AiKYNETIX

Upload an organization logo (owner-only)

POST
/api/me/branding/logo/
curl --request POST \
  --url http://localhost:8000/api/me/branding/logo/ \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: multipart/form-data' \
  --form file=@file

Multipart upload of an org logo for the active team. Owner-only (403 for members). Accepts PNG / JPG / SVG up to 2 MB; wrong type or oversize → 400. Stores the object in the media bucket under teams/<id>/branding/ and returns its public logo_url. The URL is NOT persisted by this call — PATCH it into /api/me/branding/ as logo_url to save it (mirrors the Client.avatar_url two-step).

Authorizations

Section titled “Authorizations”

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typemultipart/form-data

Multipart body for POST /api/me/branding/logo/.

object
file
required

Logo image — PNG / JPG / SVG, ≤ 2 MB. Validated server-side.

string format: binary

Responses

Section titled “Responses”

200

Section titled “200”
Media typeapplication/json
object
logo_url
required

Public URL of the stored logo. PATCH it into /api/me/branding/ as logo_url to persist.

string format: uri
Examples
ExampleUploadedLogoURL

Uploaded logo URL

{
  "logo_url": "https://media.example/aikynetix-media/teams/2648a781/branding/logo-9f3ab2c1.svg"
}

400

Section titled “400”
Media typeapplication/json
object
detail
required

Human-readable message, or a stable machine code for the cases a client branches on. The standard envelope for 400 (validation — a field-keyed object may appear instead), 401 (missing / invalid credentials), 403 (authenticated but not permitted), and 404 (absent — cross-team records are collapsed to 404 so the API never leaks the existence of another team’s data).

string
Examplegenerated
{
  "detail": "example"
}

401

Section titled “401”
Media typeapplication/json
object
detail
required

Human-readable message, or a stable machine code for the cases a client branches on. The standard envelope for 400 (validation — a field-keyed object may appear instead), 401 (missing / invalid credentials), 403 (authenticated but not permitted), and 404 (absent — cross-team records are collapsed to 404 so the API never leaks the existence of another team’s data).

string
Examplegenerated
{
  "detail": "example"
}

403

Section titled “403”
Media typeapplication/json
object
detail
required

Human-readable message, or a stable machine code for the cases a client branches on. The standard envelope for 400 (validation — a field-keyed object may appear instead), 401 (missing / invalid credentials), 403 (authenticated but not permitted), and 404 (absent — cross-team records are collapsed to 404 so the API never leaks the existence of another team’s data).

string
Examplegenerated
{
  "detail": "example"
}