Get multimodal upload URLs
Storage
Get multimodal upload URLs
POST
Get multimodal upload URLs
Authorizations
API key issued by EverOS, sent as Authorization: Bearer <api_key>.
Body
application/json
Objects to sign for upload. At most 50 per request
(status: 1007 if exceeded). Each fileId must be unique within
the request (status: 1009 on duplicates).
Required array length:
1 - 50 elementsResponse
Envelope response (MMS returns HTTP 200 for every business outcome;
only unmatched routes return 404). status: 0 means success and
result.data is a SignResponse. Non-zero status values seen on
this endpoint:
20003— request body bind failure (malformed JSON).2018— parameter validation failed (e.g. missingobjectList,fileId,fileName, orfileType);result.datais the validator error string.1012—mms-tokenmissing, invalid, expired, or revoked (emitted by the auth middleware before the handler runs).1013— token lacks the requiredobject:signscope.1007—objectListexceeds the per-request limit of 50.1002—fileTypenot one of image/video/file.1009— duplicatefileIdwithin the request.1004— S3 operation failed (bucket unavailable).1005— presigned POST generation failed.2015— object metadata persistence failed.20001— unhandled internal server error.
Response envelope for the sign endpoint. The result.data shape
depends on status:
status: 0(success) —result.datais aSignResponse, as modelled below.status: 2018(validation failed) —result.datais a plain string carrying the validator error message, not aSignResponse.- all other non-zero statuses —
result.dataisnull.
Generated clients should treat result.data as populated only when
status is 0.

