List available data source types
Get a list of plugin type
Get a list of plugin type
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.
sym-version is required and must be 7.x (for example 7.0).
See SymetryML REST API Security
for the signature algorithm and a complete example.
In: header
Path Parameters
User/Customer identifier
Response Body
application/json
curl -X GET "https://example.com/c1/dss/type"[ "s3", "sftp", "http", "https", "gcs", "azure_blob_storage", "redshift", "jdbc", "localfile", "bigquery", "snowflake", "s3_oci"]Preview data sample POST
Preview data from a data source before creating it. Useful for validating data source configuration and examining data structure, column names, and sample values. The request body has the same encrypted **DSInfo** shape for every data source type (`s3`, `redshift`, `localfile`, etc.) — see [Create new data source](/docs/api-reference/data-sources/dss-create-post) for decrypted-equivalent examples covering all supported types.
Authorize a file upload (step 1 of 3) POST
First step of the file-upload flow: registers a data source definition and authorizes a subsequent upload for it. Only `sftp` and `localfile` destinations are accepted (`localfile` only when the server sets `sml.local_ds.enable=1`); since 7.0 any other type, or a definition missing a required field, is refused here with `400`. The request body is a `DSInfoEncrypted` — the JSON serialization of a `DSInfo` encrypted with the customer's secret key in the 7.0 `v2:` format ([Encrypted Request and Response Bodies](/docs/symetryml-rest-client/rest-documentation/symetryml-rest-api-security#encrypted-request-and-response-bodies)). On success, the response's `statusString` **is** the value the caller sent in its own `Authorization` header — base64-encode that value to use as the `key` query parameter in `upload` (step 3), and compute its RFC 2104 HMAC (with the same secret key) to use as `keyhmac`. The authorization is only valid for 10 minutes.