API docs by Redocly

DBC Metadata Enrich API (1.0.0-dev)

Download OpenAPI specification:

License: Propietary

The DBC Metadata Enrich API lets DBC push per-receiver metadata enrichments (e.g. cataloguing flags) for a content. Publizon merges the pushed data into the ONIX it serves to the target receiver channel.

Authentication

An API key and a set of credentials (email and password) must be used to authenticate. Use the auth api to get the short-lived token needed to call the endpoints.

companyId header

The companyId header is only relevant when your user belongs to more than one company. In that case it must be set on every request to indicate which company the call is being made on behalf of. If this applies to you, contact Publizon to obtain your company id.

Put content flags for a receiver

Store the calling source's cataloguing flags for a content on a receiver channel.

Error codes:

  • UNAUTHORIZED: Authentication failed or the caller is not allowed to access this endpoint.
  • FORBIDDEN: The caller is authenticated but does not have permission to push content flags.
  • CONTENT_NOT_FOUND: The provided content identifier does not exist.
  • RECEIVER_NOT_FOUND: The content is not distributed to the provided receiver.
  • UNPROCESSABLE_ENTITY: The request payload is invalid.
Authorizations:
(api_keybearer_auth)
path Parameters
identifier
required
string
receiverId
required
string
Request Body schema: application/json
required
required
object

Responses

Request samples

Content type
application/json
{
  • "flags": {
    }
}

Response samples

Content type
application/json
{
  • "errorCode": "UNAUTHORIZED",
  • "message": "string",
  • "traceId": "string"
}