Download a connection-scoped records export artifact
Redeems a `READY` records export as a short-lived signed URL for the materialized FHIR NDJSON artifact. The export must have been created by the same SDK connection. Returns `409` if the export exists but is not yet `READY` (still `QUEUED`/`RUNNING`) or is no longer downloadable (`EXPIRED`/`FAILED`), and `404` if it does not belong to the connection.
/api/sdk/v1/records/exports/{exportId}/downloadRedeems a READY records export as a short-lived signed URL for the materialized FHIR NDJSON artifact. The export must have been created by the same SDK connection. Returns 409 if the export exists but is not yet READY (still QUEUED/RUNNING) or is no longer downloadable (EXPIRED/FAILED), and 404 if it does not belong to the connection.
Authorization
platformApiKey CuraeAI Platform API key using the format Bearer . Keys are opaque credentials such as cae_live_..., not JWTs.
In: header
Path Parameters
Response Body
application/json
application/problem+json
curl -X GET "https://example.com/api/sdk/v1/records/exports/497f6eca-6276-4993-bfeb-53cbbbba6f08/download"{ "download": { "url": "http://example.com", "expiresInSeconds": 60, "expiresAt": "2019-08-24T14:15:22Z" }, "export": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "connectionId": "84b500d7-71c8-4b1f-adf4-f1eb0000973d", "status": "QUEUED", "resourceTypes": [ "Observation" ], "format": "fhir_ndjson", "includeRawFhir": true, "artifact": { "sha256": "string", "byteSize": "string" }, "errorCode": "string", "queuedAt": "2019-08-24T14:15:22Z", "startedAt": "2019-08-24T14:15:22Z", "completedAt": "2019-08-24T14:15:22Z", "expiresAt": "2019-08-24T14:15:22Z", "failedAt": "2019-08-24T14:15:22Z", "createdAt": "2019-08-24T14:15:22Z", "updatedAt": "2019-08-24T14:15:22Z" }}{ "type": "string", "title": "string", "status": 0, "detail": "string", "instance": "string", "code": "string", "details": {}, "retryable": true}Get a connection-scoped records export GET
Returns status and metadata for a durable records export job created by the same SDK connection.
Create an SDK patient connection POST
Starts a connection-oriented Curae Connect flow for the SDK app's authenticated user coordinate. The response returns a durable `connection.id` used as `connectionId` in subsequent SDK gateway request bodies. If user action is required, `nextAction` contains a Curae-hosted webview URL to open.