Changes API.

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

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

{
    "unit": "https://weblate.info.ucl.ac.be/api/units/37741/?format=api",
    "component": "https://weblate.info.ucl.ac.be/api/components/cnp3-ebook/principlestransport/?format=api",
    "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlestransport/en/?format=api",
    "user": null,
    "author": null,
    "timestamp": "2022-09-17T01:14:38.509429+02:00",
    "action": 59,
    "target": "The third phase of a connection is its release. As a connection involves three parties (two users and one service provider), any of them can request the termination of the connection. Usually, connections are terminated upon request of one user once the data transfer is finished. However, sometimes the service provider may be forced to terminate a connection. This can be due to lack of resources inside the service provider or because one of the users is not reachable anymore through the network. In this case, the service provider will issue `Disconnect.indication` primitives to both users. These primitives will contain, as parameter, some information about the reason for the termination of the connection. Unfortunately, as illustrated in the figure below, when a service provider is forced to terminate a connection it cannot guarantee that all SDUs sent by each user have been delivered to the other user. This connection release is said to be abrupt as it can cause losses of data.",
    "id": 14998,
    "action_name": "String updated in the repository",
    "url": "https://weblate.info.ucl.ac.be/api/changes/14998/?format=api"
}