Content Licensing API (1.1.1)

Download OpenAPI specification:

The Content Licensing integration API

Partner login

login

Request Body schema: application/json
clientId
required
string

The client's unique identifier

clientSecret
required
string

Secret token held by the partner

Responses

Request samples

Content type
application/json
{
  • "clientId": "string",
  • "clientSecret": "string"
}

Response samples

Content type
application/json
{
  • "token": "a_jwt_valid_token"
}

ContentLicensing catalog

catalog

Request Body schema: application/json
required
clientId
required
string

The client's unique identifier

Responses

Request samples

Content type
application/json
{
  • "clientId": "string"
}

Response samples

Content type
application/json
{
  • "idChannel": "string",
  • "authors": [
    ],
  • "background": "string",
  • "cover": "string",
  • "trailer": "string",
  • "title": "string",
  • "subtitle": "string",
  • "htmlDescription": "string",
  • "price": 0,
  • "video": [
    ]
}

ContentLicensing contentAccessAuthorization

contentAccessAuthorization

Request Body schema: application/json
clientId
required
string

The client's unique identifier

userId
required
string

The client's unique identifier. This field id is provided by the partner. It represent the unique indentifier for the user. The partner can choose it depending on how he thinks it is more manageable for him handle this field. The identifier must not have a specific formatting for osteocom. The most important thing is that must be unique for identify the custemer. Osteocom manages this fiels only for content authorization access and for user token creation.

email
string

This field becomes mandatory if partner gave permission to osteocom about marketing consent. The email must be a valid formatted email i.e. test@domain.com, otherwise the field is considerated optional

marketingConsent
boolean

This field is about marketing consent if the customer decide to give the permission for receiving marketing contents i.e. newsletters. It is set to false value by default.

name
string

User's first name

surname
string

User's last name

required
Array of objects (contentLicensing_contentAuthorization_products)

Responses

Request samples

Content type
application/json
{
  • "clientId": "string",
  • "userId": "string",
  • "email": "string",
  • "marketingConsent": false,
  • "name": "string",
  • "surname": "string",
  • "products": [
    ]
}

Response samples

Content type
application/json
{
  • "token": "userAccessKey"
}

ContentLicensing video access

videoAccess

Request Body schema: application/json
clientId
required
string
userId
required
string

The client's unique identifier. This field id is provided by the partner. It represent the unique indentifier for the user. The partner can choose it depending on how he thinks it is more manageable for him handle this field. The identifier must not have a specific formatting for osteocom. The most important thing is that must be unique for identify the custemer. Osteocom manages this fiels only for content authorization access and for user token creation.

videoId
required
string

Unique identifier for the video

userAccessKey
required
string

Access key that authenticates the user

Responses

Request samples

Content type
application/json
{
  • "clientId": "string",
  • "userId": "string",
  • "videoId": "string",
  • "userAccessKey": "string"
}

Response samples

Content type
application/json
{
  • "tokenAuthVideo": "a_token_video"
}

ContentLicensing revocate activation

revocateActivation

Request Body schema: application/json
clientId
required
string

The client's unique identifier

userId
required
string

User Id provided by partner.

channelId
required
string

Unique identifier for the channel

Responses

Request samples

Content type
application/json
{
  • "clientId": "string",
  • "userId": "string",
  • "channelId": "string"
}

Response samples

Content type
application/json
{
  • "userId": "email_user",
  • "cancelationDate": "024-00-00T00:00:00.000Z"
}