Mapping-Files

Chakra mapping files. The six mapping-file resource operations are served by the trace-service router behind enable_trace_routes; the two configuration attach and detach operations are served by central unconditionally.

Endpoints

Method	Path	Description
PATCH	`/api/v1/configurations/{config_id}/mapping-file`	Attach mapping file to configuration
DELETE	`/api/v1/configurations/{config_id}/mapping-file`	Detach mapping file from configuration
GET	`/api/v1/mapping-files`	List mapping files
GET	`/api/v1/mapping-files/{mapping_file_id}`	Get mapping file
DELETE	`/api/v1/mapping-files/{mapping_file_id}`	Delete mapping file
GET	`/api/v1/mapping-files/{mapping_file_id}/download`	Get mapping file download URL
POST	`/api/v1/mapping-files/upload-url`	Initiate mapping-file upload
POST	`/api/v1/mapping-files/upload-url/complete`	Complete mapping-file upload

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

Name	In	Type	Required	Description
`config_id`	path	string	Yes	-
`If-Match`	header	string	No	ETag for optimistic concurrency control

Request Body

Field	Type	Required	Description
`mappingFileId`	string	Yes	-

{
  "mappingFileId": "string"
}

Responses

200 - Mapping file attached successfully; returns the new configuration version

{
  "id": "config_10045",
  "workspaceId": "string",
  "name": "string",
  "status": "draft",
  "createdAt": "2024-01-15T10:30:00Z",
  "modifiedAt": "2024-01-15T10:30:00Z",
  "version": 1,
  "componentCount": 1,
  "components": [
    {
      "type": "...",
      "trafficType": "...",
      "model": "ScalaSwitch",
      "name": "spine-switch-1",
      "version": "3.2.1",
      "typedParameters": "...",
      "allowedComponents": [
        "..."
      ],
      "components": [
        "..."
      ]
    }
  ],
  "containers": [
    {
      "type": "...",
      "name": "roce-rack",
      "model": "ScalaRack",
      "version": "4.0.0",
      "configuration": null,
      "allowedComponents": [
        "..."
      ],
      "components": [
        "..."
      ]
    }
  ],
  "applications": [
    {
      "type": "...",
      "trafficType": "...",
      "name": "ScalaChakraGenerator",
      "model": "ChakraWorkload",
      "version": "4.0.1",
      "typedParameters": "..."
    }
  ],
  "links": [
    {
      "type": "...",
      "trafficType": "...",
      "model": "ScalaSwitch",
      "name": "spine-switch-1",
      "version": "3.2.1",
      "typedParameters": "...",
      "allowedComponents": [
        "..."
      ],
      "components": [
        "..."
      ]
    }
  ],
  "topology": {
    "name": null,
    "type": "clos",
    "topologyTiers": 1,
    "allowedComponents": [
      "string"
    ],
    "components": [
      "..."
    ],
    "appDistribution": {
      "description": "...",
      "randomApplicationDistribution": "..."
    }
  },
  "globalParameters": {},
  "activeTraceset": {
    "name": "string",
    "id": "string"
  },
  "activeMappingFile": {
    "id": "string",
    "name": "string",
    "deleted": true
  }
}

400 - Malformed configuration ID or mapping file ID, a request body that fails validation, or a configuration in the template workspace (reserved for standard templates) 404 - Configuration not found, or mapping file not found, deleted, or held by another workspace 409 - The configuration has no attached traceset (MAPPING_REQUIRES_TRACESET), or the traceset’s rank count is not yet resolved (CONFLICT, retry-safe). 412 - Precondition failed (ETag mismatch) 422 - The configuration has no Chakra application (MAPPING_REQUIRES_CHAKRA_APP), or the mapping file’s rank count differs from the traceset’s (MAPPING_RANK_COUNT_MISMATCH).

Detach 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

Name	In	Type	Required	Description
`config_id`	path	string	Yes	-
`If-Match`	header	string	No	ETag for optimistic concurrency control

Responses

200 - Mapping file detached successfully; returns the new configuration version

{
  "id": "config_10045",
  "workspaceId": "string",
  "name": "string",
  "status": "draft",
  "createdAt": "2024-01-15T10:30:00Z",
  "modifiedAt": "2024-01-15T10:30:00Z",
  "version": 1,
  "componentCount": 1,
  "components": [
    {
      "type": "...",
      "trafficType": "...",
      "model": "ScalaSwitch",
      "name": "spine-switch-1",
      "version": "3.2.1",
      "typedParameters": "...",
      "allowedComponents": [
        "..."
      ],
      "components": [
        "..."
      ]
    }
  ],
  "containers": [
    {
      "type": "...",
      "name": "roce-rack",
      "model": "ScalaRack",
      "version": "4.0.0",
      "configuration": null,
      "allowedComponents": [
        "..."
      ],
      "components": [
        "..."
      ]
    }
  ],
  "applications": [
    {
      "type": "...",
      "trafficType": "...",
      "name": "ScalaChakraGenerator",
      "model": "ChakraWorkload",
      "version": "4.0.1",
      "typedParameters": "..."
    }
  ],
  "links": [
    {
      "type": "...",
      "trafficType": "...",
      "model": "ScalaSwitch",
      "name": "spine-switch-1",
      "version": "3.2.1",
      "typedParameters": "...",
      "allowedComponents": [
        "..."
      ],
      "components": [
        "..."
      ]
    }
  ],
  "topology": {
    "name": null,
    "type": "clos",
    "topologyTiers": 1,
    "allowedComponents": [
      "string"
    ],
    "components": [
      "..."
    ],
    "appDistribution": {
      "description": "...",
      "randomApplicationDistribution": "..."
    }
  },
  "globalParameters": {},
  "activeTraceset": {
    "name": "string",
    "id": "string"
  },
  "activeMappingFile": {
    "id": "string",
    "name": "string",
    "deleted": true
  }
}

400 - Malformed configuration ID, or a configuration in the template workspace (reserved for standard templates) 404 - Configuration not found, or no mapping file attached 412 - Precondition failed (ETag mismatch)

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

Name	In	Type	Required	Description
`workspaceId`	query	string	Yes	Workspace to list (format: `workspace_xxx`).
`limit`	query	integer	No	Maximum number of items to return; at least 1. A value above the server’s page cap but within the unsigned 32-bit range is clamped to the cap; a value outside that range is refused as not parsing.
`next`	query	string	No	Opaque cursor token from the previous response’s nextCursor field.

Responses

200 - Paginated list of mapping files

{
  "items": [
    {
      "id": "mapfile_2cVQ8f0YyQ3nT1hKpR7mBz4LsXd",
      "name": "gpt-175b-256n.txt",
      "workspaceId": "workspace_def456",
      "sizeBytes": 4096,
      "rankCount": 256,
      "scaleUpGroupCount": 2,
      "hasScaleUp": true,
      "createdAt": "2026-09-16T14:30:00Z"
    }
  ],
  "pagination": {
    "count": 1,
    "hasMore": false
  }
}

400 - Bad Request — workspaceId is absent or blank (there is no tenant-wide fallback), limit is zero or does not parse as a positive unsigned 32-bit integer, or the cursor is invalid or expired

{
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "workspaceId is required"
  }
}

Get 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

Name	In	Type	Required	Description
`mapping_file_id`	path	string	Yes	Mapping file ID (format: `mapfile_xxx`).

Responses

200 - Mapping file details

{
  "id": "mapfile_2cVQ8f0YyQ3nT1hKpR7mBz4LsXd",
  "name": "gpt-175b-256n.txt",
  "workspaceId": "workspace_def456",
  "sizeBytes": 4096,
  "rankCount": 256,
  "scaleUpGroupCount": 2,
  "hasScaleUp": true,
  "createdAt": "2026-09-16T14:30:00Z",
  "description": "Reverse placement for the 256-rank study",
  "hash": "crc64nvme:vK3Jd8Qm1pA",
  "etag": "\"0\"",
  "duplicateOfExisting": false
}

404 - Mapping file not found

{
  "error": {
    "code": "NOT_FOUND",
    "message": "Mapping file 'mapfile_notfound' not found"
  }
}

410 - Mapping file has been deleted

{
  "error": {
    "code": "MAPPING_FILE_DELETED",
    "message": "Mapping file 'gpt-175b-256n.txt' has been deleted"
  }
}

Delete 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

Name	In	Type	Required	Description
`mapping_file_id`	path	string	Yes	Mapping file ID (format: `mapfile_xxx`).

Responses

204 - Mapping file deleted 404 - Mapping file not found, or already deleted

{
  "error": {
    "code": "NOT_FOUND",
    "message": "Mapping file 'mapfile_notfound' not found"
  }
}

Get 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

Name	In	Type	Required	Description
`mapping_file_id`	path	string	Yes	Mapping file ID (format: `mapfile_xxx`).

Responses

200 - Presigned download URL

{
  "url": "https://scala-traces.s3.amazonaws.com/library/crc64nvme:vK3Jd8Qm1pA/gpt-175b-256n.txt?X-Amz-Algorithm=...",
  "expiresAt": "2026-09-16T15:30:00Z"
}

404 - Mapping file not found

{
  "error": {
    "code": "NOT_FOUND",
    "message": "Mapping file 'mapfile_notfound' not found"
  }
}

410 - Mapping file has been deleted

{
  "error": {
    "code": "MAPPING_FILE_DELETED",
    "message": "Mapping file 'gpt-175b-256n.txt' has been deleted"
  }
}

Initiate 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

Field	Type	Required	Description
`name`	string	No	Optional display name; absent, it is chakra-mapping.txt. Used verbatim as the final segment of the stored object’s key, so it must be a single safe path segment of 1 to 255 bytes of [A-Za-z0-9._-], must not be `.`, and must not contain `..` anywhere (so `placement..v2.txt` is refused), because central’s launch check and the legacy path’s stager refuse `..` inside the path the name is part of. Display metadata only: inside the simulator the file is always named chakra-mapping.txt.
`sizeBytes`	integer	Yes	Upper bound on the file’s byte length. The 64,000,000-byte ceiling is the 64 MB per-file limit. The stored sizeBytes is the completed object’s actual length, which may be smaller.
`workspaceId`	string	Yes	Workspace the file belongs to (format: `workspace_xxx`). Must not be blank or padded with whitespace; it is stored exactly as sent.
`description`	string	No	-

{
  "workspaceId": "workspace_def456",
  "name": "gpt-175b-256n.txt",
  "sizeBytes": 4096,
  "description": "Reverse placement for the 256-rank study"
}

Responses

200 - Presigned upload URLs for each part

{
  "uploadId": "upload_2cVQ8f0YyQ3nT1hKpR7mBz4LsXd",
  "checksumAlgorithm": "crc64nvme",
  "parts": [
    {
      "partNumber": 1,
      "url": "https://scala-traces.s3.amazonaws.com/uploads/upload_2cVQ8f0YyQ3nT1hKpR7mBz4LsXd/gpt-175b-256n.txt?partNumber=1&X-Amz-Algorithm=..."
    }
  ],
  "expiresAt": "2026-09-17T14:30:00Z"
}

400 - Invalid request — name is not a single safe path segment or contains .., sizeBytes is outside 1..64000000, workspaceId is absent, blank, or padded with whitespace, or description exceeds 2048 characters

{
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "sizeBytes must be between 1 and 64000000 bytes (the 64 MB per-file limit); got 64000001"
  }
}

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.

Request Body

Field	Type	Required	Description
`uploadId`	string	Yes	-
`parts`	array[CompletedPart]	Yes	-

{
  "uploadId": "upload_2cVQ8f0YyQ3nT1hKpR7mBz4LsXd",
  "parts": [
    {
      "partNumber": 1,
      "etag": "\"d41d8cd98f00b204e9800998ecf8427e\""
    }
  ]
}

Responses

200 - The uploaded bytes already exist as a live mapping file in this workspace; that file is returned with duplicateOfExisting true and no new mapping file was created

{
  "id": "mapfile_2cVQ8f0YyQ3nT1hKpR7mBz4LsXd",
  "name": "gpt-175b-256n.txt",
  "workspaceId": "workspace_def456",
  "sizeBytes": 4096,
  "rankCount": 256,
  "scaleUpGroupCount": 2,
  "hasScaleUp": true,
  "createdAt": "2026-09-16T14:30:00Z",
  "description": "Reverse placement for the 256-rank study",
  "hash": "crc64nvme:vK3Jd8Qm1pA",
  "etag": "\"0\"",
  "duplicateOfExisting": true
}

201 - Mapping file stored and created

{
  "id": "mapfile_2cVQ8f0YyQ3nT1hKpR7mBz4LsXd",
  "name": "gpt-175b-256n.txt",
  "workspaceId": "workspace_def456",
  "sizeBytes": 4096,
  "rankCount": 256,
  "scaleUpGroupCount": 2,
  "hasScaleUp": true,
  "createdAt": "2026-09-16T14:30:00Z",
  "description": "Reverse placement for the 256-rank study",
  "hash": "crc64nvme:vK3Jd8Qm1pA",
  "etag": "\"0\"",
  "duplicateOfExisting": false
}

400 - Invalid request — the upload session is not a mapping-file upload, or the parts do not match the session

{
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "Expected 1 part(s), got 2"
  }
}

404 - Upload session not found

{
  "error": {
    "code": "NOT_FOUND",
    "message": "Upload session not found"
  }
}

409 - The upload session named by uploadId is already being completed or was already completed or aborted (CONFLICT), or a different mapping file with this display name is already stored under this content checksum (MAPPING_FILE_HASH_COLLISION)

{
  "error": {
    "code": "MAPPING_FILE_HASH_COLLISION",
    "message": "A different mapping file is already stored under this content checksum. Re-upload under a different display name."
  }
}

410 - Upload session expired

{
  "error": {
    "code": "GONE",
    "message": "Upload session has expired"
  }
}

413 - The staged object is larger than the declared sizeBytes, or above the 64 MB limit; staging is deleted and nothing is stored

{
  "error": {
    "code": "PAYLOAD_TOO_LARGE",
    "message": "Staged object is 70000000 bytes, above the declared 4096 bytes and/or the 64 MB per-file limit of 64000000 bytes"
  }
}

422 - The file does not parse as a Chakra mapping file; the message names the offending line

{
  "error": {
    "code": "MAPPING_FILE_INVALID",
    "message": "line 3: expected an integer server id, found 'x'"
  }
}

503 - Another upload of the same content held the content lock for too long. This upload session is closed and its staged object deleted, so the request is not safe to retry: open a new upload session and upload the file again. Because another upload of the same content was in progress, the new upload is most often answered 200 with duplicateOfExisting set.

{
  "error": {
    "code": "SERVICE_UNAVAILABLE",
    "message": "Internal server error"
  }
}

Getting Started

API Reference

Reference

Examples

Endpoints

Attach mapping file to configuration

Parameters

Request Body

Responses

Detach mapping file from configuration

Parameters

Responses

List mapping files

Parameters

Responses

Get mapping file

Parameters

Responses

Delete mapping file

Parameters

Responses

Get mapping file download URL

Parameters

Responses

Initiate mapping-file upload

Request Body

Responses

Complete mapping-file upload

Request Body

Responses

​Endpoints

​Attach mapping file to configuration

​Parameters

​Request Body

​Responses

​Detach mapping file from configuration

​Parameters

​Responses

​List mapping files

​Parameters

​Responses

​Get mapping file

​Parameters

​Responses

​Delete mapping file

​Parameters

​Responses

​Get mapping file download URL

​Parameters

​Responses

​Initiate mapping-file upload

​Request Body

​Responses

​Complete mapping-file upload

​Request Body

​Responses

Endpoints

Attach mapping file to configuration

Parameters

Request Body

Responses

Detach mapping file from configuration

Parameters

Responses

List mapping files

Parameters

Responses

Get mapping file

Parameters

Responses

Delete mapping file

Parameters

Responses

Get mapping file download URL

Parameters

Responses

Initiate mapping-file upload

Request Body

Responses

Complete mapping-file upload

Request Body

Responses