Creates a new bulk job. The job type can be one of Import, Delete, Update, or Cancel. The response includes the job ID and information needed to upload your data file to S3.
After creating a bulk job, you must upload the data file to Amazon S3 using the information
returned in the uploadFileInfo
object. This includes:
uploadUrl
: The S3 endpoint to which the file must be uploaded.formFields
: Key-value pairs to include in a multipart/form-data POST request.jobId
: The ID of the job, used for later submission.You can use the following cURL command to upload the file:
curl --request POST \
--url '<uploadUrl>' \
--header 'Content-Type: multipart/form-data' \
--form 'key=<formFields.key>' \
--form 'bucket=<formFields.bucket>' \
--form 'x-amz-algorithm=<formFields["x-amz-algorithm"]>' \
--form 'x-amz-credential=<formFields["x-amz-credential"]>' \
--form 'x-amz-date=<formFields["x-amz-date"]>' \
--form 'Policy=<formFields.Policy>' \
--form 'x-amz-signature=<formFields["x-amz-signature"]>' \
--form 'x-amz-security-token=<formFields["x-amz-security-token"]>' \
--form 'file=@/path/to/your/file.csv'
Note: Always use the exact form field keys returned in the formFields
object of the API response.
This is a presigned Amazon S3 POST operation and not a Zuora endpoint.
After uploading the file, you must call the "Submit a bulk job for processing" operation endpoint to start processing the job.
Accept-Encoding | string Include the If specified, Zuora automatically compresses responses that contain over 1000 bytes of data, and the response contains a |
Content-Encoding | string Include the |
Zuora-Entity-Ids | string An entity ID. If you have Zuora Multi-entity enabled and the OAuth token is valid for more than one entity, you must use this header to specify which entity to perform the operation in. If the OAuth token is only valid for a single entity, or you do not have Zuora Multi-entity enabled, you should not set this header. |
Zuora-Org-Ids | string Comma separated IDs. If you have Zuora Multi-Org enabled, you can use this header to specify which orgs to perform the operation in. If you do not have Zuora Multi-Org enabled, you should not set this header. The IDs must be a sub-set of the user's accessible orgs. If you specify an org that the user does not have access to, the operation fails. This header is important in Multi-Org (MO) setups because it defines the organization context under which the API should operate—mainly used for read access or data visibility filtering. If the header is not set, the operation is performed in scope of the user's accessible orgs. |
Zuora-Track-Id | string <= 64 characters A custom identifier for tracing the API call. If you set a value for this header, Zuora returns the same value in the response headers. This header enables you to associate your system process identifiers with Zuora API calls, to assist with troubleshooting in the event of an issue. The value of this field must use the US-ASCII character set and must not include any of the following characters: colon ( |
Job creation successful
{- "name": "string",
- "objectType": "string",
- "description": "string",
- "mappings": [
- {
- "source": "string",
- "target": "string",
- "type": "array",
- "arrayType": "string"
}
], - "headers": [
- "string"
], - "rowIdHeader": "string",
- "delimiter": "string",
- "hasHeaders": true,
- "fileType": "csv",
- "jobType": "Import",
- "isCustomObject": true,
- "customObjectNamespace": "string"
}
{- "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
- "uploadUrl": "string",
- "uploadRequest": {
- "fields": {
- "property1": "string",
- "property2": "string"
}
}, - "status": "Created",
- "jobType": "Import"
}