Get mandate history

Accepted cases (Aktenzeichen).

Main-case-centric: the list returns main cases only. Sub-cases are reachable through the main case detail representation and direct detail/subresource URLs, not a flat list expansion. Tenant-scoped by the authenticated company.

Sub-resources of one mandate:

• payments — the reported, non-ignored payments
• documents — claim-document metadata and a proxy-stream download
• history — published client activity, related resources, and attachments. A main case includes its subcases; a subcase includes only itself.

The sub-resource operations resolve the mandate including sub-cases — unlike the list, which hides sub-cases — so an individually-addressable sub-case’s own track stays reachable. These public mandate operations are reads.

GET /v2/mandates/{id}/history/

Get mandate history

Python

import requests

url = "https://api.paywise.de/v2/mandates/{id}/history/"

headers = {"Authorization": "Bearer <token>"}

response = requests.get(url, headers=headers)

print(response.text)

200

{
  "count": 1,
  "next": null,
  "previous": null,
  "results": [
    {
      "advance_type": null,
      "attachments": [],
      "description": "Please confirm the outstanding amount.",
      "id": "b0000000-0000-4000-8000-000000000001",
      "is_advance_request": false,
      "occurred_at": "2026-07-18T11:05:00Z",
      "related_resources": [
        {
          "body": {
            "allowed_answer_types": "yes-no-freetext-on-no",
            "answer": null,
            "answered": false,
            "answered_at": null,
            "created_at": "2026-07-18T11:05:00Z",
            "description": "We need your confirmation before continuing.",
            "href": "https://api.paywise.de/v2/mandates/50000000-0000-4000-8000-000000000001/requests-to-client/80000000-0000-4000-8000-000000000001/",
            "id": "80000000-0000-4000-8000-000000000001",
            "mandate": {
              "href": "https://api.paywise.de/v2/mandates/50000000-0000-4000-8000-000000000001/",
              "id": "50000000-0000-4000-8000-000000000001",
              "reference_number": "PW-2026-000123"
            },
            "question_attachments": [],
            "title": "Please confirm the outstanding amount",
            "updated_at": "2026-07-18T11:05:00Z"
          },
          "id": "80000000-0000-4000-8000-000000000001",
          "type": "request_to_client",
          "url": "https://api.paywise.de/v2/mandates/50000000-0000-4000-8000-000000000001/requests-to-client/80000000-0000-4000-8000-000000000001/"
        }
      ],
      "source_mandate": {
        "id": "50000000-0000-4000-8000-000000000001",
        "reference_number": "PW-2026-000123",
        "relation": "main_case"
      },
      "state": {
        "legal_stage": {
          "code": "extrajudicial",
          "label": "Außergerichtlich",
          "label_key": "mandate.state.legal_stage.extrajudicial"
        },
        "payment": {
          "code": "unpaid",
          "label": "Unbezahlt",
          "label_key": "mandate.state.payment.unpaid"
        },
        "processing": {
          "code": "in_progress",
          "label": "Laufend",
          "label_key": "mandate.state.processing.in_progress"
        }
      },
      "text": "Please confirm the outstanding amount.",
      "title": "Additional information required",
      "type": "status_update",
      "updated_at": "2026-07-18T11:05:00Z"
    }
  ]
}

Authorizations

caseBearerAuthpartnerBearerAuth

Authorization · string · header · required

Company-bound Case Management API key — the standard credential for this API.

Headers

X-On-Behalf-Of-Company · string<uuid>

Required when a Partner key calls the Case Management API; rejected for direct Case keys. Contains the entitled paywise company UUID.

Path Parameters

id · string<uuid> · required

UUID of the accepted case in this request.

Query Parameters

cursor · string

Opaque continuation cursor for incremental synchronization, taken from the next URL of a previous page. Only valid together with updated_since: with updated_since set the list is ordered by change time and then id and pages by this cursor instead of offset, so a row that changes while you page is returned again later instead of pushing another row out of the result. Rows changed less than 60 seconds ago are held back until they are settled; use the largest updated_at you received as the next updated_since.

expand · enum<string>

Embed the typed related resource body.

Available options: history.related_resources

limit · integer · default: 10

Number of results to return (maximum 100).

Required range: 1 <= x <= 100

offset · integer · default: 0

Zero-based result offset.

Required range: x >= 0

updated_since · string<date-time>

Return entries changed at or after this timezone-aware RFC 3339 timestamp (inclusive). With it set, results are ordered by change time and then id instead of newest first, page by cursor instead of offset, and entries changed less than a minute ago are held back.

Response

200

application/json

Limit/offset page of results.

count · integer · required · read-only

Total number of matching resources.

next · string<uri> | null · required · read-only

URL for the next page, or null when this is the last page. With updated_since it carries an opaque cursor.

previous · string<uri> | null · required · read-only

URL for the previous page, or null when this is the first page. Always null with updated_since.

results · object[] · required · read-only

History entries returned for the requested page.

Show child attributes