Kickoff Request:
A client MAY also provide a second prefer header value of separate-export-status, so the combined prefer header for the kickoff request is Prefer: respond-async, seperate-export-status (alternatively, the header may be repeated twice, once with each value). If this header value is included by a client and is supported by a server, the server SHALL return the header Preference-Applied: respond-async, seperate-export-status in its response.
When a prefer header value of separate-export-status is provided in the kickoff request and supported by the server, the HTTP status code in the response to an bulk data status request SHALL reflect the status request itself, and not the export job. When the HTTP status code of the bulk data status request is 200 OK, the response SHALL also include an X-Export-Status header with an HTTP status code that reflects the status of the export job.
Examples:
Scenario
Headers
Body