List, create, and manage binary blobs. The content format may be anything, because the blobs are treated as opaque data by the service. Each blob has a status. If a blob is created without content, then its status is created. If the blob is created with content or has been updated to include content then its status is available.
List previously uploaded binary blobs in the user's account. The list can be filtered with mediaType and status query parameters.
Security
sessionToken
- Mock serverhttps://tidepool.redocly.app/_mock/reference/blob.v1/v1/users/{userId}/blobs
- integrationhttps://external.integration.tidepool.org/v1/users/{userId}/blobs
- productionhttps://api.tidepool.org/v1/users/{userId}/blobs
- dev1https://dev1.dev.tidepool.org/v1/users/{userId}/blobs
- qa1https://qa1.development.tidepool.org/v1/users/{userId}/blobs
- qa2https://qa2.development.tidepool.org/v1/users/{userId}/blobs
curl -i -X GET \
'https://tidepool.redocly.app/_mock/reference/blob.v1/v1/users/{userId}/blobs?mediaType=application%2Foctet-stream&status=created' \
-H 'X-Tidepool-Session-Token: YOUR_API_KEY_HERE'List of binary blob metadata
Array []
String representation of a Tidepool User ID. Old style IDs are 10-digit strings consisting of only hexadeximcal digits. New style IDs are 36-digit UUID v4
digestMD5string, = 24 characters(MD5 Digest)^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[...required
Example:"HUXZLQLMuI/KZ5KDcJPcOA=="
Media type as defined in RFC 2045.
Example:"application/octet-stream"
Example:"2017-02-06T02:37:46Z"
Example:"2017-02-06T02:37:46Z"
Example:"2017-02-06T02:37:46Z"
Response
[ { "id": "97a9fae8a19b4da58bb48dc90c9562c9", "userId": "string", "digestMD5": "HUXZLQLMuI/KZ5KDcJPcOA==", "mediaType": "application/octet-stream", "size": 1024, "status": "created", "createdTime": "2017-02-06T02:37:46Z", "modifiedTime": "2017-02-06T02:37:46Z", "deletedTime": "2017-02-06T02:37:46Z", "revision": 42 } ]