Edit a row of a store clone batch

Replaces the values of one row and validates it again with the rules of the upload: required columns, CNPJ, platform lookups, manager email and managerUserExists. Only that row is looked up on the platform. Then it recomputes the collisions of the whole file: DUPLICATE_IN_FILE for retailerName and hostName and REPEATED_IN_FILE for taxDocumentId, so fixing one row can change the status of others. The other rows keep their own errors.

version is the version of the row the client read. When the row changed since then, it answers 409 with the current row in details.row. The edited row gets version + 1; the other rows keep their version even when their status changes.

Only the values of the batch columns are kept. An empty value clears the column.

The answer carries the edited row and every row whose status or errors changed, the new totals and rowSummaries. A batch that is EXECUTING or COMPLETED answers 409. When other edits keep changing the batch at the same time, it retries by itself and answers 409 asking to try again only after a few attempts.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
integer
required
≥ 1
Body Params
values
object
required

Values of the batch columns, as strings. Other keys are dropped.

integer
required
≥ 0
Responses

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json