GET /api/v0.1/hansard/entries/726187/?format=api
HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "id": 726187,
    "url": "https://info.mzalendo.com/api/v0.1/hansard/entries/726187/?format=api",
    "text_counter": 581,
    "type": "speech",
    "speaker_name": "Hon. (Dr.) Nyikal",
    "speaker_title": "",
    "speaker": {
        "id": 434,
        "legal_name": "James Nyikal",
        "slug": "james-nyikal"
    },
    "content": "Hon. Temporary Deputy Chairlady, this is a monitoring issue. At times, it is necessary to have a certificate back once it is revoked. It may be revoked, but people may still use it. If you have a strict monitoring system, then that is fine. Returning the certificate upon revocation may help. Expiry is different because it carries the date and if anybody sees it, he will know that it is expired. A revoked certificate may be used unless it is surrendered or destroyed. We may need to differentiate revocation from expiry. For revocation, the certificate should be returned to the board as indicated here."
}