Endpoints
List mapping files
GET/api/v1/mapping-files
Lists the Chakra mapping files in a workspace, newest first, with cursor pagination. Deleted files are omitted.
Parameters
Responses
200 - Paginated list of mapping filesGet mapping file
GET/api/v1/mapping-files/{mapping_file_id}
Returns a mapping file’s metadata, including the stored CRC64NVME checksum of its bytes.
Parameters
Responses
200 - Mapping file detailsDelete mapping file
DELETE/api/v1/mapping-files/{mapping_file_id}
Soft-deletes a mapping file. The delete succeeds whether or not a configuration refers to the file; a configuration that refers to it then reports it as deleted, and creating a simulation from that configuration is refused until the file is detached or another is attached. Simulations already created are unaffected.
Parameters
Responses
204 - Mapping file deleted 404 - Mapping file not found, or already deletedGet mapping file download URL
GET/api/v1/mapping-files/{mapping_file_id}/download
Returns a presigned URL for the mapping file’s stored bytes. The served bytes are byte-for-byte the uploaded bytes.
Parameters
Responses
200 - Presigned download URLInitiate mapping-file upload
POST/api/v1/mapping-files/upload-url
Creates an upload session and returns presigned S3 multipart upload URLs for one Chakra mapping file. After PUTting every part, call POST /api/v1/mapping-files/upload-url/complete to validate and store it. Nothing is stored until that call succeeds.
Request Body
Responses
200 - Presigned upload URLs for each partComplete mapping-file upload
POST/api/v1/mapping-files/upload-url/complete
Finalises the multipart upload, validates the file against the simulator’s grammar, stores it once under its content checksum, and creates the mapping file. A file whose bytes already exist as a live mapping file in the workspace returns that file with duplicateOfExisting set and creates nothing. A file that fails validation is refused with the offending line number and nothing is stored.