Create an export template

Creates a complete export template, including its attributes and analyzer tests, in one call. The operation runs asynchronously and returns 202 Accepted with a Content-Location header pointing to the operation resource. Poll GET /V2/operations/{operationId} for progress and the result. **Field semantics.** Creation writes what the payload carries and leaves everything else at its entity default, so a partial `exportMarketing` object keeps the defaults for the sub-fields it omits. `metadata` is always replaced wholesale, so a sub-field you leave out of it is empty on the new template. `PUT /V2/export-templates/{id}` shares this request schema but replaces both objects wholesale. Server-assigned ids are not accepted anywhere: do not send `id` inside `attributes`, `tags`, `customFormFields` or `analyzerTests`. **Publishing required.** The new export template is a draft. It becomes available in the Productsup platform only after you publish it with `POST /V1/export-templates/{id}/commit`.

curl -X POST "https://export-template-api.productsup.com/V2/export-templates" \  -H "Content-Type: application/json" \  -d '{    "name": "Google Shopping Feed"  }'

{
  "operationId": "01980f10-5b04-7845-b0d5-66861c6cabb0",
  "status": "queued"
}

{
  "message": "Invalid JSON payload"
}

{
  "errors": {
    "message": "Resource access denied."
  }
}