Prepare prediction result
Registers a short-lived, one-time-use download key for `dsName` in Redis, scoped to the caller's request signature. Only checks that `dsName` is a **registered** data source name — it does not check that the underlying file/object it points to actually exists or is reachable; that's only discovered when `tmp/dss/file/{key}/{filename}` is subsequently called.
Registers a short-lived, one-time-use download key for dsName in
Redis, scoped to the caller's request signature. Only checks that
dsName is a registered data source name — it does not check
that the underlying file/object it points to actually exists or is
reachable; that's only discovered when tmp/dss/file/{key}/{filename}
is subsequently called.
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
Data source name
Response Body
application/json
application/json
curl -X GET "https://example.com/c1/tmp/dss/auth/predict-nbra_ds_sftp_iris"{ "statusCode": 200, "statusString": "OK", "values": {}}{ "statusCode": 400, "statusString": "There is no data source with name <unknownDsName>.", "values": {}}Predict from an inline data frame POST
Synchronous prediction against a small inline `DataFrame` (as opposed to `dss/predict`, which predicts from/to registered data sources via an async job). Each row is predicted individually; the response's `KSVSMap` has one entry per input row, in the same order. If any input attribute name isn't recognized by the model, the request still succeeds — unrecognized attributes are silently ignored; only when **every** attribute name is unrecognized does the call fail with `500 "No known input attributes"`.
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.