> ## Documentation Index > Fetch the complete documentation index at: https://spreecommerce.org/docs/llms.txt > Use this file to discover all available pages before exploring further. # Update your account > Edits the signed-in person's own account — the name and photo their team sees, and the language their panel displays. This is the person, not the business: the seller they act for is `PATCH /profile`. Like `GET /me` it answers without `X-Spree-Seller-Id`, because the account is the same whichever seller they are acting for. `avatar` takes an ActiveStorage direct-upload signed id to set the photo, or `null` to remove it; omit it to leave the current one alone. `email` is identity-bound and cannot be changed here. ## OpenAPI ````yaml /api-reference/seller.yaml patch /api/v3/seller/me openapi: 3.0.3 info: title: Seller API contact: name: Spree Commerce url: https://spreecommerce.org email: hello@spreecommerce.org description: | Spree Seller API v3 - the marketplace seller panel, where a seller runs their own shop inside someone else's marketplace. This is a branch of its own, not a narrowing of the Admin API. Every endpoint is scoped server-side to the seller the request acts as, which is what makes cross-seller access impossible by construction rather than by rule. Sellers never call the Admin API. ## Authentication Sign in at `POST /api/v3/seller/auth/login` and send the returned JWT as `Authorization: Bearer `. The token carries a `seller_api` audience — a token minted for the storefront or the back office is not accepted here, and vice versa. There is deliberately **no secret API key** for this branch: a credential that could act as a seller without a seller signing in is exactly what the separate audience exists to prevent. ### Choosing a seller A user may run more than one seller. Login returns the list; send the chosen seller's ID in the `X-Spree-Seller-Id` header on every authenticated request. The store is derived from the seller — never sent — so no header can widen what a seller reaches. A request that names no seller the caller belongs to is rejected with `403`. ## Response Format All responses are JSON. List endpoints return paginated responses with `data` and `meta` keys. ## Error Handling Errors return a consistent format: ```json { "error": { "code": "validation_error", "message": "Validation failed", "details": { "name": ["can't be blank"] } } } ``` version: v3 servers: - url: http://{defaultHost} variables: defaultHost: default: localhost:3000 security: [] tags: - name: Authentication description: Seller sign-in, token refresh, logout, and invitation acceptance - name: Account description: The signed-in user, the sellers they may act for, and what they may do - name: Countries description: Country and state reference data for the panel's address forms - name: Delivery Methods description: >- The seller's own ways to ship, and the marketplace methods shared with them - name: Delivery Profiles description: >- The marketplace's delivery vocabulary — what kind of goods a product is, which decides how it ships - name: Delivery Zones description: >- The marketplace's destinations, for narrowing where a seller's own method ships - name: Onboarding description: >- The marketplace checklist a seller completes before admission, and what they submit against it - name: Policies description: The seller's own legal documents, as the marketplace asks them to publish - name: Product Types description: The types a seller may list a product against, and what each adds - name: Products description: The seller's own catalog - name: Profile description: >- The seller's own record — presentation, contact details, addresses, and tax registration - name: Stock Locations description: Where the seller keeps stock, and so where their returns are sent - name: Team description: Who runs this seller, and the invitations nobody has accepted yet - name: Uploads description: Presigned direct uploads for the documents onboarding asks for paths: /api/v3/seller/me: patch: tags: - Account summary: Update your account description: | Edits the signed-in person's own account — the name and photo their team sees, and the language their panel displays. This is the person, not the business: the seller they act for is `PATCH /profile`. Like `GET /me` it answers without `X-Spree-Seller-Id`, because the account is the same whichever seller they are acting for. `avatar` takes an ActiveStorage direct-upload signed id to set the photo, or `null` to remove it; omit it to leave the current one alone. `email` is identity-bound and cannot be changed here. parameters: [] requestBody: content: application/json: schema: type: object properties: first_name: type: string example: Ada last_name: type: string example: Lovelace selected_locale: type: string example: de description: Panel display language, as a code the panel ships. avatar: type: string nullable: true description: Direct-upload signed id, or `null` to remove the photo. responses: '200': description: account updated content: application/json: example: user: id: adm_UkLWZg9DAJ email: kala@rosenbaummoen.info first_name: Ada last_name: Lovelace full_name: Ada Lovelace created_at: '2026-01-15T12:00:00.000Z' avatar_url: null selected_locale: null sellers: - id: sel_UkLWZg9DAJ name: Seller 56 slug: seller-56 status: approved permissions: [] permission_keys: [] schema: $ref: '#/components/schemas/SellerMeResponse' '401': description: missing or invalid token content: application/json: example: error: code: authentication_required message: Authentication required schema: $ref: '#/components/schemas/ErrorResponse' '422': description: the photo is not a web image content: application/json: example: error: code: validation_error message: >- Avatar has an invalid content type (authorized content types are PNG, JPG, GIF, WEBP) details: avatar: - >- has an invalid content type (authorized content types are PNG, JPG, GIF, WEBP) schema: $ref: '#/components/schemas/ErrorResponse' security: - bearer_auth: [] components: schemas: SellerMeResponse: type: object description: >- The signed-in user, the sellers they may act for, and what they may do on the selected one properties: user: $ref: '#/components/schemas/Account' sellers: type: array items: $ref: '#/components/schemas/SellerMeSummary' permissions: type: array items: $ref: '#/components/schemas/PermissionRule' permission_keys: type: array items: type: string description: >- Permission keys on the selected seller. Empty until `X-Spree-Seller-Id` names one — capability is per seller. example: - read_products - write_products required: - user - sellers - permissions - permission_keys ErrorResponse: type: object properties: error: type: object properties: code: type: string example: record_not_found message: type: string example: Record not found details: type: object description: Field-specific validation errors nullable: true example: name: - is too short - is required email: - is invalid required: - code - message required: - error example: error: code: validation_error message: Validation failed details: name: - is too short email: - is invalid Account: type: object properties: id: type: string email: type: string first_name: type: string nullable: true last_name: type: string nullable: true full_name: type: string nullable: true created_at: type: string avatar_url: type: string nullable: true selected_locale: type: string nullable: true required: - id - email - first_name - last_name - full_name - created_at - avatar_url - selected_locale x-typelizer: true SellerMeSummary: type: object description: >- A seller the signed-in user may act for, as `/me` reports it — the login response carries the same fields without `slug`. properties: id: type: string description: Prefixed seller ID — send as `X-Spree-Seller-Id` example: sel_abc123 name: type: string example: Acme Supplies slug: type: string example: acme-supplies status: type: string example: approved description: Seller lifecycle status required: - id - name - slug - status PermissionRule: type: object description: >- A single permission rule (CanCanCan rule). Rules are applied in order, last-matching-wins. properties: allow: type: boolean description: true for `can`, false for `cannot` actions: type: array items: type: string description: Action names, e.g. ["read", "update"] or ["manage"] subjects: type: array items: type: string description: Subject class names, e.g. ["Spree::Product"] or ["all"] has_conditions: type: boolean description: >- True if the server-side rule has per-record conditions. The SPA shows the action optimistically and handles 403 from the API. required: - allow - actions - subjects - has_conditions securitySchemes: bearer_auth: type: http scheme: bearer bearerFormat: JWT description: JWT token for an authenticated seller session (`seller_api` audience) ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.