Complete robot map (beta)
const url = 'https://api.example.yas/v1/robots/maps/complete';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"partnerId":"partner","schemaVersion":"2026-11","sourceSystem":"partner-export","robotId":"rbt_example","mapId":"map_1"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.example.yas/v1/robots/maps/complete \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "partnerId": "partner", "schemaVersion": "2026-11", "sourceSystem": "partner-export", "robotId": "rbt_example", "mapId": "map_1" }'Beta. Complete makes the map live. Send partnerId, schemaVersion, sourceSystem, robotId, and mapId. PUT the bytes to the minted URL first. An unknown robotId or map is 404. The first complete returns status ready and updatedAt as ISO-8601 UTC. A repeat when the map is already live is 200 with status ready and no updatedAt. Complete within 24 hours of minting. A missing upload is 409 upload_incomplete; a size or type mismatch is 422 invalid_media. A credential may expire before the completion deadline: an already uploaded valid object can still complete. Mint again for invalid content because objects cannot be overwritten.
Authorizations
Section titled “Authorizations”Request Bodyrequired
Section titled “Request Bodyrequired”object
Partner id. It must match the server key.
Schema version of this body. Example: 2026-11.
Name of the system that sent this body. Example: partner-export.
Robot id. The robot must already exist.
Map id from mint. The live map changes when complete succeeds.
Example
{ "partnerId": "partner", "schemaVersion": "2026-11", "sourceSystem": "partner-export", "robotId": "rbt_example", "mapId": "map_1"}Responses
Section titled “Responses”Map is live. status is ready. updatedAt is ISO-8601 UTC on the first complete. A repeat when the map is already live is 200 with status ready and no updatedAt.
object
ready means the map is live.
ISO-8601 UTC on the first complete. A repeat when the map is already live omits this field.
Example
{ "robotId": "rbt_example", "mapId": "map_1", "status": "ready", "updatedAt": "2026-10-15T10:00:00.000Z"}400A required field is missing.
object
Stable error code. No stack trace.
Example
{ "error": "invalid_body"}401The server key is missing or wrong.
object
Stable error code. No stack trace.
Example
{ "error": "invalid_credentials"}403A server key may be limited to vehicles, robots, or both. A call outside that limit is 403 `forbidden` and stores nothing. `identity_mismatch` means `partnerId` does not match the server key.
object
Stable error code. No stack trace.
Example
{ "error": "forbidden"}404Unknown `robotId` or map. Nothing is stored.
object
Stable error code. No stack trace.
Example
{ "error": "not_found"}409No completed object is available yet. Upload before the credential expires and retry complete.
object
Stable error code. No stack trace.
Example
{ "error": "upload_incomplete"}410The 24-hour completion deadline has expired. Mint again; a previous ready map is unchanged.
object
Stable error code. No stack trace.
Example
{ "error": "upload_expired"}422The uploaded object does not match its declared size or type. Mint again and upload valid bytes; the object cannot be overwritten.
object
Stable error code. No stack trace.
Example
{ "error": "invalid_media"}503Storage or its required configuration is unavailable. Retry after the Retry-After interval.
object
Stable error code. No stack trace.
Example
{ "error": "unavailable"}