Units API.

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

GET /api/units/883071/?format=api
HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "translation": "https://translate.fedoraproject.org/api/translations/fedora-docs-l10n-fedora-system-administrat/f29pagesserversconfiguring_ntp_using_ntpd/en/?format=api",
    "source": [
        "The _Network Time Protocol_ (*NTP*) enables the accurate dissemination of time and date information in order to keep the time clocks on networked computer systems synchronized to a common reference over the network or the Internet. Many standards bodies around the world have atomic clocks which may be made available as a reference. The satellites that make up the Global Position System contain more than one atomic clock, making their time signals potentially very accurate. Their signals can be deliberately degraded for military reasons. An ideal situation would be where each site has a server, with its own reference clock attached, to act as a site-wide time server. Many devices which obtain the time and date via low frequency radio transmissions or the Global Position System (GPS) exist. However for most situations, a range of publicly accessible time servers connected to the Internet at geographically dispersed locations can be used. These `NTP` servers provide \"pass:attributes[{blank}]_Coordinated Universal Time_pass:attributes[{blank}]\" (*UTC*). Information about these time servers can found at [citetitle]_www.pool.ntp.org_."
    ],
    "previous_source": "",
    "target": [
        "The _Network Time Protocol_ (*NTP*) enables the accurate dissemination of time and date information in order to keep the time clocks on networked computer systems synchronized to a common reference over the network or the Internet. Many standards bodies around the world have atomic clocks which may be made available as a reference. The satellites that make up the Global Position System contain more than one atomic clock, making their time signals potentially very accurate. Their signals can be deliberately degraded for military reasons. An ideal situation would be where each site has a server, with its own reference clock attached, to act as a site-wide time server. Many devices which obtain the time and date via low frequency radio transmissions or the Global Position System (GPS) exist. However for most situations, a range of publicly accessible time servers connected to the Internet at geographically dispersed locations can be used. These `NTP` servers provide \"pass:attributes[{blank}]_Coordinated Universal Time_pass:attributes[{blank}]\" (*UTC*). Information about these time servers can found at [citetitle]_www.pool.ntp.org_."
    ],
    "id_hash": 3657097139281585317,
    "content_hash": 3657097139281585317,
    "location": "./pages/servers/Configuring_NTP_Using_ntpd.adoc:12",
    "context": "",
    "note": "type: Plain text",
    "flags": "",
    "labels": [],
    "state": 100,
    "fuzzy": false,
    "translated": true,
    "approved": false,
    "position": 3,
    "has_suggestion": false,
    "has_comment": false,
    "has_failing_check": false,
    "num_words": 167,
    "source_unit": "https://translate.fedoraproject.org/api/units/883071/?format=api",
    "priority": 100,
    "id": 883071,
    "web_url": "https://translate.fedoraproject.org/translate/fedora-docs-l10n-fedora-system-administrat/f29pagesserversconfiguring_ntp_using_ntpd/en/?checksum=b2c09e78d7f9e4a5",
    "url": "https://translate.fedoraproject.org/api/units/883071/?format=api",
    "explanation": "",
    "extra_flags": "",
    "pending": false,
    "timestamp": "2020-02-24T22:19:15.849193Z"
}