> ## Documentation Index > Fetch the complete documentation index at: https://docs.shoply.gg/llms.txt > Use this file to discover all available pages before exploring further. # Update an expense > Changes an expense. A field left out stays as it is. Refused with `business_details_required` until the store has its business details. Needs the `expenses.write` permission (Change Expenses). ## OpenAPI ````yaml /api-reference/openapi.json put /stores/{storeId}/expenses/{expenseId} openapi: 3.1.0 info: title: Shoply API version: '1' description: >- Everything a store's own server can do with a secret API key: its catalogue, orders, customers, marketing, finance and the rest of what the dashboard does. And the Customer API, which a buyer's own device asks with a token of theirs. servers: - url: https://api.shoply.gg/v1 security: - apiKey: [] tags: - name: API key - name: Store - name: Domain - name: Payment methods - name: Analytics - name: Storefronts - name: Storefront code - name: Payment Routing - name: Custom payment methods - name: Products - name: Product pictures - name: Stock - name: Categories - name: Upsells - name: Subscriptions - name: Orders - name: Invoices - name: Reviews - name: Coupons - name: Coupon categories - name: Coupon pop-up - name: Sales - name: Blog - name: Search settings - name: Redirects - name: Sitemap - name: Cart Recovery - name: Email Marketing - name: Email Templates - name: Customers - name: Affiliates - name: Support Tickets - name: Blacklist - name: Fraud protection - name: Disputes - name: Finance - name: Tax - name: Expenses - name: Expense setup - name: API requests - name: Webhook endpoints - name: Webhook deliveries - name: Customer API paths: /stores/{storeId}/expenses/{expenseId}: put: tags: - Expenses summary: Update an expense description: >- Changes an expense. A field left out stays as it is. Refused with `business_details_required` until the store has its business details. Needs the `expenses.write` permission (Change Expenses). operationId: expenses.update parameters: - name: storeId in: path required: true description: >- The store's ID. A key reaches the store it was made in: `GET /key` answers which. schema: type: string - name: expenseId in: path required: true description: The expense. schema: type: string - $ref: '#/components/parameters/IdempotencyKey' requestBody: required: true content: application/json: schema: type: object properties: spentOn: type: string description: >- The day it was paid, as `YYYY-MM-DD`. Not in the future: a bill still to come is a recurring expense. example: '2026-10-01' payee: type: string description: Who was paid, up to 120 characters. example: Hetzner amount: type: number description: How much, above zero, with at most 2 decimals. example: 12.5 currency: type: string description: >- The currency `amount` is in, when it is not the store's own. It is converted at today's rate and kept in the store's currency. example: EUR method: type: string description: How it was paid. enum: - card - bank - crypto - paypal - cash - other categoryId: type: string description: The expense category it is filed in, by ID. category: type: string description: >- The same, by the category's name, for a script that has no reason to know an ID. With neither, the store's rules file it. example: Hosting note: type: string description: A note, up to 255 characters. reference: type: string description: An invoice number or the like, up to 160 characters. productId: type: string description: A product this expense is a cost of. required: - spentOn - payee - amount responses: '200': description: It worked. content: application/json: schema: type: object properties: success: type: boolean message: nullable: true code: nullable: true data: type: object properties: id: type: string spentOn: type: string payee: type: string note: type: string category: type: object properties: id: type: string name: type: string icon: type: string method: type: string reference: type: string amount: type: number entered: nullable: true productId: nullable: true recurring: type: boolean source: type: string receipt: nullable: true createdAt: type: string updatedAt: type: string example: success: true message: null code: null data: id: 9843f9b7-5d03-480f-9ed8-0cf8aba0e7f9 spentOn: '2026-10-22' payee: Hetzner note: Two servers category: id: 2022abcc-ad2e-45ba-8e73-9e1652d701b7 name: Hosting and domains icon: server method: card reference: R0012345678 amount: 12.5 entered: null productId: null recurring: false source: api receipt: null createdAt: '2026-10-22T16:20:20Z' updatedAt: '2026-10-22T16:20:20.053Z' '401': $ref: '#/components/responses/NoKey' '403': $ref: '#/components/responses/NotAllowed' '404': $ref: '#/components/responses/NotFound' '422': $ref: '#/components/responses/Refused' '429': $ref: '#/components/responses/TooMany' x-codeSamples: - lang: javascript label: Node.js source: | import Shoply from "@shoplygg/node"; const shoply = new Shoply({ apiKey: process.env.SHOPLY_API_KEY }); const result = await shoply.expenses.update("EXPENSE_ID", { spentOn: "2026-10-01", payee: "Hetzner", amount: 12.5, }); - lang: php label: PHP source: | getenv('SHOPLY_API_KEY')]); $result = $shoply->expenses->update('EXPENSE_ID', [ 'spentOn' => '2026-10-01', 'payee' => 'Hetzner', 'amount' => 12.5, ]); - lang: python label: Python source: > import shoply client = shoply.Client() # reads SHOPLY_API_KEY result = client.expenses.update("EXPENSE_ID", spentOn="2026-10-01", payee="Hetzner", amount=12.5) components: parameters: IdempotencyKey: name: Idempotency-Key in: header required: false description: >- A word of your own for this one change, up to 180 letters, digits, dots, dashes, underscores and colons. Sent again with the same key, the request is not carried out twice: the first answer comes back, with `Idempotent-Replay: true`. schema: type: string responses: NoKey: description: >- No API key was sent, or the one sent is not a live key: `api_key_required`, `invalid_api_key`. content: application/json: schema: $ref: '#/components/schemas/Refusal' NotAllowed: description: >- The key is real and may not do this: `missing_scope` (with `requiredScope`), `ip_not_allowed`, `account_unavailable`, or `dashboard_only` for something only a person in the dashboard may do. content: application/json: schema: $ref: '#/components/schemas/Refusal' NotFound: description: >- There is no such thing in this store: `not_found`. A store that is not the key's own is answered the same way. content: application/json: schema: $ref: '#/components/schemas/Refusal' Refused: description: >- The request was understood and not carried out. `validation_failed` says what is wrong with each field under `errors`; other codes are the route's own. content: application/json: schema: $ref: '#/components/schemas/Refusal' TooMany: description: >- The key has used up its budget for now: `rate_limited`. `Retry-After` says how many seconds to wait. content: application/json: schema: $ref: '#/components/schemas/Refusal' schemas: Refusal: type: object properties: success: type: boolean example: false message: type: string description: What is wrong, in words for a person. code: type: string description: What is wrong, as a word that does not change. data: nullable: true errors: type: object description: >- For `validation_failed`: what is wrong with each field, by the field's name. additionalProperties: type: string required: - success - message - code securitySchemes: apiKey: type: http scheme: bearer description: >- A secret API key, made under Developers in the dashboard: `Authorization: Bearer shoply_sk_...` ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.