Upload Asset
Upload one file (multipart form field file, at most 25 MiB). The
part’s content type is stored and served back from bytes_path.
Dark launch: requires the hosted_apis_access entitlement (402 hosted_apis_not_in_plan otherwise).
Authentication
AuthorizationBearer
Enter your API key with the Bearer prefix, e.g. ‘Bearer sk_…’.
Path parameters
store_id
Store id (prefixed external id, store_...).
Headers
Speechify-Version
Request
This endpoint expects a multipart form containing a file.
file
The file to store (at most 25 MiB).
Response headers
Speechify-Request-Id
Unique identifier for this request, present on every response (2xx and
non-2xx alike). If the caller sends a `Speechify-Request-Id` request
header the server echoes it back (sanitized and length-capped) so one
logical request can be traced end-to-end; otherwise the server generates
a fresh value. Log it on every response and quote it in support requests
- it is the stable handle that ties your observation to Speechify's
server-side logs, and it matches the `request_id` field in the error
envelope.
The legacy alias `X-Request-ID` carries the same value and is still
accepted on requests, until 2027-07-24. Prefer the un-prefixed name
(RFC 6648).
Response
The stored asset.
id
filename
content_type
size_bytes
created_at
bytes_path
The API path the bytes stream from (prepend the API host).
source
The durable run (and its journal step) that wrote this version. Absent for a direct API write.
Errors
400
Bad Request Error
401
Unauthorized Error
402
Payment Required Error
404
Not Found Error
413
Content Too Large Error
503
Service Unavailable Error