Upload a CSV file that will be ingested asynchronously

This endpoint will emit a presigned URL to which to upload the file.

The actual upload must start within one minute of the initial call, and terminate within 15 minutes.

The HTTP client used must then replay the request to the provided URL with the same headers as the initial request except for
the Marble API key, and upload the CSV file.

For Marble's hosted platform or when using Google Cloud Storage, adding the header indicated here (x-goog-if-generation-match: 0)
is mandatory. For self-hosted deployment, refer to Marble's documentation to learn more about requirements, depending on the
blob storage in use.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
Query Params
boolean

Whether to put the ingested object under continuous monitoring

uuid

If monitoring the object, which configuration to use. Can be repeated multiple times.

boolean

If monitoring, whether to skip the initial screening of the ingested object.

Headers
string
enum
required
Allowed:
Responses

Language
Credentials
LoadingLoading…
Response
Choose an example:
application/json