server_error

What the API answers

Something went wrong on our side.

The message stays in English, like every API response: branch your script on error.code, which never changes.

What to do

Something unexpected went wrong on our side. Try again; if it comes back, give support the X-Request-Id header of the response.

Processing. Encoding the file failed, or something else went wrong on the platform side. Fixed by the platform operator.

For a media upload, retry with the same Idempotency-Key: if the first attempt had gone through, you get the same media back instead of a duplicate.

Full response

JSON

{
    "status": "error",
    "error": {
        "code": "server_error",
        "message": "Something went wrong on our side.",
        "docs": "https://aperture-app.preview.moncompanion.cloud/docs/errors/server_error"
    },
    "meta": {
        "request_id": "01K2R7M8QF3V9XZ4B6NCDT0YAH",
        "api_version": "v1",
        "duration_ms": 12,
        "timestamp": "2026-10-27T14:32:08+00:00"
    }
}

The meta values are a sample. meta also carries app_version and commit, and a refusal may add error.details with the value at fault.

Codes of the same family

HTTP	Code	What to do	Retry
500	transcode_failedTranscode failed	The file could not be re-encoded. Check that it plays correctly on your machine, then send it again.	No
503	encoder_unavailableEncoder unavailable	The encoder is not answering on this instance. The problem is on the platform's side: try again later.	Yes
500	server_errorServer error	Something unexpected went wrong on our side. Try again; if it comes back, give support the X-Request-Id header of the response.	Yes
503	maintenanceMaintenance in progress	The platform is under maintenance, and nothing needs changing on your side. Wait the number of seconds given by the Retry-After header, which every route sends, then send the same request again. The native API also gives error.details.retry_after_seconds (the same wait), error.details.expected_end_at (the announced end, or null) and error.details.media_served: when it is true, files already uploaded keep being served and read requests keep working, only uploads and changes wait. GET /api/v1/status keeps answering throughout.	Yes

Every error code