Create or replace the Business Event Definition
This endpoint is an idempotent upsert of your single Business Event Definition. It is a full replace: attributes and validations omitted from the body are removed.
To create the Business Event Definition, send no If-Match, or send If-None-Match: * to make the request fail if a Business Event Definition already exists. To replace it, If-Match is required and must carry the ETag from your last read - omitting it is rejected with 428, and a stale value with 412.
Validations can be created only for attributes defined in the Business Event Definition. A change is refused with 409 if accounting rules still use on an attribute that the change removes in their configuration, or if the attribute’s type or role it changes.
The change takes effect immediately and does not go through an approval workflow, so the response is always 201 or 200. Your user also needs permission to view and edit data structures.
If part of the setup could not be completed straight away, the response lists it in warnings. The Business Event Definition is saved and the setup finishes by itself, so you do not need to resend the request.
Authentication
OAuth authentication of the form <token>.
Headers
The ETag from your last read of the resource. Required when replacing an existing resource, and omitted when creating one.
Send * for create-only semantics - the request then fails if the resource already exists.
Request
Response headers
Current entity tag of the resource. Supply it as If-Match on a subsequent update or deactivation.