Get fusion cell status
Checks the reachability/status of each remote fusion cell in the supplied list, by calling each cell's own project-info endpoint. The request body is the customer's secret-key-encrypted (AES) payload; once decrypted it is a `FusionCellInfoList`. The response is likewise an AES-encrypted `FusionCellStatusList`.
Checks the reachability/status of each remote fusion cell in the supplied list, by calling each cell's own project-info endpoint.
The request body is the customer's secret-key-encrypted (AES)
payload; once decrypted it is a FusionCellInfoList. The response
is likewise an AES-encrypted FusionCellStatusList.
Authorization
SymetryMLAuth HMAC-SHA256 signature-based authentication: requests are signed with
your secret key and sent with the Customer-ID, Sym-date,
Authorization, Content-MD5 and sym-version headers.
See SymetryML REST API Security
for the signature algorithm and a complete example.
In: header
Path Parameters
User/Customer identifier
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
AES-encrypted FusionCellInfoList JSON.
Response Body
application/json
curl -X POST "https://example.com/c1/projects/fusion/cellsStatus" \ -H "Content-Type: application/json" \ -d '20nVn/MsTKo6Yf9fmpRMvRfL/AlOrXzAFqe7kP9CSdCaQI4R7I+hm91IIrCtz/v64kWShqXHLzbSVsnGek311b9z6kv+d04KSTh7dLuYlykyWNBuQf1u22hWSyz5QhNit6u38tuquIa2Wc+15McWi1O8Hxo5GmBdfwX/O45kEjWIIQXMY8tcmLaBCCMJwWHshC6oQ2AmKcVxb52yLSOtF2qNpK/Cv22ecTevoWfV+hfCpCsayIUtbPhLiTJ3L38n'values.cellsStatusEncrypted is base64-encoded encrypted content. It is an encrypted FusionCellStatusList object, encrypted with the customer's secret key.
Decrypted equivalent of values.cellsStatusEncrypted:
{ "values": [ { "host": "http://cell1.internal:8080", "cid": "c1", "status": "OK", "pid": "cellProject1" }, { "host": "http://cell2.internal:8080", "cid": "c1", "status": "OK", "pid": "cellProject2" } ]}{ "statusCode": 200, "statusString": "OK", "values": { "cellsStatusEncrypted": "20nVn/MsTKo6Yf9fmpRMvRfL/AlOrXzAFqe7kP9CSdCaQI4R7I+hm91IIrCtz/v6qGEb5L2gPAX2Z4zqvhrXEpVRnL8h+RZXJbhRtoE5uufWGln/12xS3dvTl9oNdkND0D33/mO30OcuYHCgtK0DO/WAMNt/mbwiaB83zHeHTUWeSEUstCtCOvfMoVu2v2K5fRkODb5sD02Oyukns/GdCgS0uqVR4mCCj4tPfpqSG/Pzkzw2Dlr4Sh/Anqpw0QJk" }}Fetch prediction result CSV GET
Streams the file backing the data source registered under `key` (via `tmp/dss/auth/predict-{dsName}` above) — the key is consumed on first use. `{filename}` is a real path segment, not a fixed literal; by convention clients always pass `result.csv`, but the server doesn't require that specific value. On failure (expired/unknown key, or a read error reaching the underlying file/object — unsupported/inaccessible source, missing local file, etc.) the response is a generic Jetty `500` HTML error page, not a JSON `JSONResponse` envelope.
Create a fusion project POST
Creates a new "fusion" project — a project that combines multiple remote projects (fusion cells), each hosted on its own SML REST server, into a single logical project. The project name is given via the `pid` query parameter, not a path segment. The request body is the customer's secret-key-encrypted (AES) payload; once decrypted it is a `FusionCellInfoList` describing the remote cells to fuse.