Change Instance

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "unit": "https://weblate.info.ucl.ac.be/api/units/37500/?format=api",
    "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/principlesnaming/?format=api",
    "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlesnaming/en/?format=api",
    "user": null,
    "author": null,
    "timestamp": "2022-09-17T01:14:27.180854+02:00",
    "action": 59,
    "target": "In addition to being more human friendly, using names instead of addresses inside applications has several important benefits. To understand them, let us consider a popular application that provides information stored on servers. This application involves clients and servers. The server provides information upon requests from client processes. A first deployment of this application would be to rely only on addresses. In this case, the server process would be installed on one host and the clients would connect to this server to retrieve information. Such a deployment has several drawbacks :",
    "id": 14719,
    "action_name": "String updated in the repository",
    "url": "https://weblate.info.ucl.ac.be/api/changes/14719/?format=api"
}