Unit Instance

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

{
    "translation": "https://weblate.osgeo.org/api/translations/postgis-workshop/history_tracking/en/?format=api",
    "source": [
        "A common requirement for production databases is the ability to track history: how has the data changed between two dates, who made the changes, and where did they occur? Some GIS systems track changes by including change management in the client interface, but that adds a lot of **complexity** to editing tools."
    ],
    "previous_source": "",
    "target": [
        "A common requirement for production databases is the ability to track history: how has the data changed between two dates, who made the changes, and where did they occur? Some GIS systems track changes by including change management in the client interface, but that adds a lot of **complexity** to editing tools."
    ],
    "id_hash": 67817232071333675,
    "content_hash": 67817232071333675,
    "location": "../../en/history_tracking.rst:6",
    "context": "",
    "note": "",
    "flags": "",
    "labels": [],
    "state": 100,
    "fuzzy": false,
    "translated": true,
    "approved": false,
    "position": 2,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": false,
    "num_words": 52,
    "source_unit": "https://weblate.osgeo.org/api/units/99441/?format=api",
    "priority": 100,
    "id": 99441,
    "web_url": "https://weblate.osgeo.org/translate/postgis-workshop/history_tracking/en/?checksum=80f0ef69cb43172b",
    "url": "https://weblate.osgeo.org/api/units/99441/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2021-11-14T01:14:42.325928Z"
}