Bulk jobs CSV format
How the CSV upload differs from the JSON domain endpoints.
The upload endpoint (POST /v3/aftermarket/customers/{customerId}/jobs/{jobId}/upload) accepts the same CSV
format as the Sample upload file on the
Add domains page.
The header row is required. A file without it is rejected.
CSV vs JSON endpoints
The bulk CSV and the JSON domain endpoints do not share value formats:
| Field | Bulk jobs CSV | Domain JSON endpoints |
|---|---|---|
| Prices | Standard USD (50) | Microunit USD (50000000) |
| Sale lander | Buy It Now / Request Price / Custom Lander | intakeStyle: BUYNOW / PRICE_FORM / CUSTOM_LANDER |
| Booleans | Y / N | true / false |
The CSV's Sale Lander column has a fourth value, Cashparking, with no JSON intakeStyle equivalent: it maps to
landingPage: PARKING_TYPE instead (a parking page, not a sale lander). The other three values map to
landingPage: SALES_TYPE plus the matching intakeStyle above.
The CSV's Hidden column is the same setting as the JSON endpoints' hidden field (Y → true, N → false),
despite the sample upload file describing it in terms of the domain reseller network rather than general listing
visibility.
Upload flow
Create a job
Call Create job. It returns 201 with the job ID.
Upload the CSV
Send the file to Upload data to job.
Check the results
Poll Get job, then read Get job results.