RECORD SERVICE Client integration reference / revision 1.4 Maintainer: Workshop Data Services Overview -------- The record service supports browser links and small command-line clients. It returns UTF-8 JSON. Object-key order is not significant; clients should read fields by name and retain the HTTP status alongside the response body. This installation uses synthetic training records. Request format -------------- Endpoint: /api/hard/action Method: GET Parameter Meaning record Record identifier from the issued ticket; preserve its spelling action Requested operation from the table below; names are lowercase sig Hexadecimal signature from the ticket issuer Include all three parameters. Encode query values when constructing a link; an ampersand separates parameters and is not part of the preceding value. Tickets are issued through the portal. Keep an original copy when diagnosing a rejected request so that transcription errors can be distinguished from service behavior. Operations ---------- Name Result view Return the record summary for an on-screen preview export Return the complete acceptance record for the audit workflow Both operations are read-only. Export does not delete the stored record or advance a background job. A successful response identifies the operation in its action field; the remaining fields depend on the selected operation. Response handling ----------------- 200 Operation completed 400 Unknown action 403 Invalid signature 404 Record not found Error bodies contain an error field. Preserve its text in support notes, but do not substitute an error body for a successful record. Submit requests one at a time and allow the current response to finish before sending another. Release notes ------------- Revision 1.4 clarifies response handling for clients that previously discarded non-200 bodies. Parameter names and operation names are unchanged. The service does not provide bulk exports or write operations in this deployment.