Endpoints
Attach mapping file to configuration
PATCH/api/v1/configurations/{config_id}/mapping-file
Sets the activeMappingFile field on the configuration and writes UseMapping and MappingFileName into every application with trafficType ‘chakra’, as a new configuration version. Requires at least one Chakra application, an attached traceset, and a mapping file whose rank count equals the traceset’s rank count.
Parameters
Request Body
Responses
200 - Mapping file attached successfully; returns the new configuration versionDetach mapping file from configuration
DELETE/api/v1/configurations/{config_id}/mapping-file
Removes the activeMappingFile field and writes UseMapping false and an empty MappingFileName into every Chakra application, restoring default placement, as a new configuration version. The mapping file itself is untouched and stays attachable to other configurations.
Parameters
Responses
200 - Mapping file detached successfully; returns the new configuration versionList 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. PUT each part with its size bytes (or fewer, since sizeBytes is an upper bound) before partUrlsExpireAt (one hour by default); expiresAt is the 24-hour session lifetime, not the URLs’. 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 part.., sizeBytes is outside 1..64000000, workspaceId is absent, blank, or padded with whitespace, or description exceeds 2048 characters
Complete 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.