ec696334ff35
Replace Complete
Beta. Catalog replace is a Beta feature and can change. Send the Batch-Beta: catalog-replace header on each call. <br/><br/>Applies the pending revision in one atomic operation. When this call is successful, the catalog serves the new revision and Batch removes the previous contents. Readers see the complete old catalog, then the complete new catalog. They never see a state between the two. <br/><br/>Batch must index every item in the pending revision before you can apply it. If indexing is not complete, the call returns 409 CATALOG_REPLACE_NOT_READY. Retry the call after a short delay. To follow the progress, read the pending_replace block of /catalogs/view.
Headers
The unique project key, identifying a project on the Batch platform
Value of the Batch-Beta header. It is a comma-separated list of Beta contract flags. Thus one request can opt into more than one Beta contract at the same time (first-flag, second-flag). Flags are lowercase and case-sensitive, and the order does not matter. Batch rejects an unknown flag with a 400 on any endpoint. When a contract becomes generally available, Batch continues to accept its flag but the flag has no more effect. Thus you never need to remove it.
Beta opt-in. This endpoint is in Beta. It accepts only requests that carry the catalog-replace flag. Batch rejects a request without the flag with a 400.
Request body
Response
Empty success response