Changes API.

See the Weblate's Web API documentation for detailed description of the API.

GET /api/changes/316095/?format=api
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "unit": "https://weblate.foundryvtt-hub.com/api/units/212094/?format=api",
    "component": "https://weblate.foundryvtt-hub.com/api/components/variant-encumbrance/main/?format=api",
    "translation": "https://weblate.foundryvtt-hub.com/api/translations/variant-encumbrance/main/pl/?format=api",
    "user": null,
    "author": null,
    "timestamp": "2023-05-05T19:45:01.166178Z",
    "action": 59,
    "target": "",
    "old": "",
    "details": {
        "state": 0,
        "source": "I DON'T RECOMMENDED it, but does anyone seem to use this strange rule? If true the add/remove of the AE is launched only when there is a change on the value level of the tier so the refresh is ignored when add/remove/update item",
        "old_state": -1
    },
    "id": 316095,
    "action_name": "String updated in the repository",
    "url": "https://weblate.foundryvtt-hub.com/api/changes/316095/?format=api"
}