Post Active Storage Presign
Same as POST /api/v2/active_storage/direct_uploads but takes the file details at the top level. Same 1 GB limit. Prefer direct_uploads.
Authentication
OAuth 2.0 Client Credentials Flow. To obtain an access token:
-
Request API credentials from HINDSITE support to receive your
client_idandclient_secret -
Make a POST request to obtain an access token:
POST https://app.hindsiteind.com/oauth/token
Content-Type: application/x-www-form-urlencoded
grant_type=client_credentials&client_id=YOUR_CLIENT_ID&client_secret=YOUR_CLIENT_SECRET
- The response will contain your access token:
{
"access_token": "your_access_token_here",
"token_type": "Bearer",
"expires_in": 7200,
"created_at": 1234567890
}
- Include the token in subsequent API requests:
Authorization: Bearer your_access_token_here
Request
Base64-encoded MD5 digest of the file contents
MIME type, e.g. image/jpeg
Response
Blob created. PUT the file bytes to direct_upload.url with direct_upload.headers, then pass signed_id to the endpoint that attaches the file.
Poster image URL. Present only for previewable blobs (e.g. video).
Storage key of the file in Hindsite’s file store. Opaque; download the file with blob_url.
Only present on the POST /api/v2/active_storage/presign and POST /api/v2/active_storage/direct_uploads responses, which omit preview_url. PUT the file bytes to url with headers, then reference the blob by signed_id.
