Skip to main content
POST
Export a CWR registration file for one publisher
This endpoint requires authentication. Include your Bearer token in the Authorization header.

Description

POST /publisher/publishers/export/cwr Generates a CWR file (text/plain) for the tenant’s exportable works (works missing required fields are excluded — see the X-CWR-Excluded-Count response header) using the given publisher’s territories and agreement block. Exactly one publisherIds entry is accepted per call; a CWR file carries a single sender/publisher chain, so multi-publisher requests are rejected rather than silently dropping publishers. Authorization: admin role + publisher capability enabled.

Code Examples

Authorizations

Authorization
string
header
required

JWT Authorization header using the Bearer scheme. Format: "Bearer {token}"

Body

application/json
publisherIds
string<uuid>[]
required

Exactly one publisher id — a CWR file carries a single sender/publisher chain. Requests with more than one id return 400.

Required array length: 1 element
version
enum<string>
default:2.1

CWR file-format version to render. Only the 2.x family is emittable — CWR 3.0/3.1 are a different specification and are rejected with 400.

Available options:
2.1,
2.2
Example:

"2.1"

Response

CWR file generated.

The response is of type file.