> ## Documentation Index > Fetch the complete documentation index at: https://documentation.debbiecollect.com/llms.txt > Use this file to discover all available pages before exploring further. # Patch case > Updates attributes of a case given the cases id ## OpenAPI ````yaml PATCH /v1/{tenantId}/cases/{id} openapi: 3.1.0 info: title: Debbie Platform API Docs description: > The Debbie API is a RESTful interface, allowing you to programmatically update, add and access your data in the platform. It provides predictable URLs for accessing resources, and uses built-in HTTP features to receive commands and return responses. This makes it easy to communicate with third party systems. ## Idempotency The Debbie API supports idempotency for non-idempotent requests through the optional `Idempotency-Key` header. This ensures that retrying the same request multiple times will produce the same result, preventing duplicate operations. ### Using Idempotency Keys - Include an `Idempotency-Key` header with a unique string (we recommend UUIDs) - Maximum key length is 64 characters - Keys are valid for 48 hours - Responses served from the idempotency cache include an `Idempotency-Cached` header ### Example ```http Idempotency-Key: 123e4567-e89b-12d3-a456-426614174000 ``` ### Error Cases - Invalid key format: 400 Bad Request - Reusing a key for a different request: 400 Bad Request ### Best Practices - Use a new key for each unique business transaction - Use the same key when retrying a failed request - Store keys with request details for debugging contact: email: support@debbie.dk version: v0.1.0 x-logo: url: https://debbie-platform.github.io/platform-api-docs/deb-logo.svg servers: - url: https://api.debbiecollect.com security: - bearerAuth: [] tags: - name: Authorization description: Endpoints for interacting with authorization - name: Cases description: Endpoints for interacting with cases - name: Customers description: Endpoints for interacting with customers - name: Creditors description: Endpoints for interacting with creditors - name: Updates description: Endpoints for interacting with updates - name: Users description: Endpoints for interacting with updates - name: Files description: Endpoints for interacting with files - name: Case vouchers description: Endpoints for interacting with case vouchers - name: Billing description: Endpoints for interacting with billing - name: Links description: Endpoints for generating links - name: Webhooks description: >- Debbie provides a range of webhooks. To try them out please visit Debbie Caseworker and navigate to Settings --> Developers --> Webhooks. - name: Voucher Type Ids description: > ### Principals: | Type | id | | --- | --- | | Invoice (Faktura) | eb41e58e-fccf-419d-a771-cd5027fe6e87 | | Credit note (Kreditnota) | ef2cdc50-230f-4046-b1af-0f9c498dddd3 | | Final statement (Opgørelse) | 42385ae0-6846-425c-a793-8d47a3b190b5 | | On account invoice (Acontofaktura) | 2d101b6e-74f9-4a4d-9f8e-c7abe2264da0 | | Loan (Gældsbrev) | bf61f462-6d3c-42e8-a99a-852d4a664926 | ### Costs: | Type | id | | --- | --- | | Collection cost (Inkassoomkostning) | 07960de4-303d-4793-92da-3a8cfd5da1a1 | | Collection fee (Inkassogebyr) | 4c3ccbbf-0651-45b2-b37b-4fe736acfd7e | | Reminder fee (Rykkergebyr) | 3e51bf87-3c8f-4dd5-abd5-69417d113c89 | | Compensation cost (Kompensationsgebyr) | ed3e3d61-e1bc-4ee2-9166-adf2c41a2bbf | ### Interests: | Type | id | | --- | --- | | DK interest (Procesrente) | ca4af363-9925-436c-83d6-23b3db6ed5d2 | | Fixed interest (Fastrente) | 299dc393-1b71-4950-860f-8fb485036722 | | Yearly interest (Årlig rente) | 37db68dd-80be-40c7-8d2d-3619c793107f | ### Transactions: | Type | id | | --- | --- | | Deposit (Indbetaling) | c51f2f6a-8081-45ef-b52d-5e0569fdf12e | externalDocs: description: Find out more about Debbie here url: https://debbie.dk paths: /v1/{tenantId}/cases/{id}: patch: tags: - Cases summary: Update a case description: Updates attributes of a case given the cases id operationId: update-case parameters: - in: path name: tenantId schema: type: string format: uuid required: true description: Id of the tenant the case belongs to - in: path name: id schema: type: string format: uuid required: true description: Id the case to be updated requestBody: description: Update case object content: application/json: schema: $ref: '#/components/schemas/UpdateCase' example: status: ENDED reason: PAID required: true responses: '204': description: Successful operation content: {} '401': $ref: '#/components/responses/UnauthorizedError' '422': $ref: '#/components/responses/UnprocessableContent' components: schemas: UpdateCase: type: object properties: status: type: string enum: - VERIFIED - ENDED description: The updated status of the case reason: type: string enum: - ERROR_US - WITHDRAWN - ERROR_CREDITOR - DEAD - BANKRUPTCY - OBJECTION - PAID - PARTIALLY_PAID - OVERPAYMENT - EXPIRATION - IRRECOVERABLE - TRANSFERRED - UNIDENTIFIED - OFFER_FROM_US - OFFER_FROM_DEBTOR - FORCED_DISSOLVED - NEGATIVE_PAYOFF - DEPARTED - CREDITOR_UNRESPONSIVE - MERGED - FIRE_AND_FORGET - SMALL_CASE_NOT_WANTED - ADDRESS_UNKNOWN - DEBT_RELIEF - CONFLICT_OF_INTEREST - MINOR - NO_DEBT - DELETED description: Used to provide a reason when the status is changed to ended isCompany: type: boolean description: >- Used to indicate whether the entity is a company (true) or private (false) customerId: type: string format: uuid description: Id of the customer which the case belongs to groupId: type: string format: uuid description: Id of case group tags: type: array description: List of tags to set on the case items: type: object required: - tag properties: tag: type: string description: The tag to set on the case from: type: string format: date-time description: Start date for which the tag is active (optional) to: type: string format: date-time description: End date for which the tag is active (optional) migratedId: type: string description: Optinoal migrated id customJournalNumber: nullable: true allOf: - $ref: '#/components/schemas/CustomJournalNumber' description: >- Set to override the journal number with a custom string. Set to null to revert to the default sequential format. CustomJournalNumber: type: object required: - journalNumber - type properties: journalNumber: type: string description: >- The custom journal number string. Replaces the default sequential format ({caseId}-{userId}) on all surfaces in the platform. example: my-reference-123 type: type: string enum: - CUSTOM_STRING description: Must be CUSTOM_STRING. responses: UnauthorizedError: description: Access token missing or invalid UnprocessableContent: description: Unable to process the contained instructions. securitySchemes: bearerAuth: type: http scheme: bearer description: >- Authentication can be done by using a bearer token in the Authorization header. This is done using the following format `Authorization: Bearer {token}`. ````