Link relation aa:create-asset

Overview

Create an asset.

HTTP method

POST

URI template variables

-

Query parameters

queueId

Only for MediaCentral Newsroom Management

A mandatory query parameter that specifies the Queue where the asset will be created.

unlock

Only for MediaCentral Newsroom Management

Put false to preserve asset lock, default value is true.

qkey

Only for MediaCentral Newsroom Management

Password for key-locked queue.

Request body

An aa:asset resource.

The format of the request body depends on the system. The type property of the link contains the supported format.

HTTP response

201 Created

The asset was created successfully.

Response body

-

The link rel doesn’t return a response body but sets the HTTP header Location to a URL that returns the created asset.

Available in

Description

MediaCentral Asset Management

The body is expected in the same format that is returned when getting the information about an asset.

  • Writable status properties are created (see Status).

  • Common attributes that are given in the request are set.

Example:
 
{
  "base": {
    "id": "934902-324-324-32-2342839",
    "type": "asset.VIDEO",
    "systemType": "interplay-mam",
    "systemID": "a80eaff4-a086-47b1-8775-9e22d3b2f8cb"
  },
  "common": {
    "name": "Parliament session"
  }
}
 

You can embed an aa:attributes resource to set custom attributes. The same restrictions apply as in aa:update-attributes.

Example:
 
{
  "base": {
    "id": "934902-324-324-32-2342839",
    "type": "asset.VIDEO",
    "systemType": "interplay-mam",
    "systemID": "a80eaff4-a086-47b1-8775-9e22d3b2f8cb"
  },
  "common": {
    "name": "Parliament session"
  },
  "_embedded": {
    "aa:attributes": {
      "attributes": [
        {
          "name": "REGISTRATION_DATETIME",
          "value": "2017-02-10 23:10:12"
        },
        {
          "name": "CONTRIBUTIONS",
          "type": "multi-value compound",
          "value": [
            {
              "index": 0,
              "attributes": [
                {
                  "name": "ROLE",
                  "value": "288"
                },
                {
                  "name": "REAL_NAME",
                  "value": "John Doe"
                }
              ]
            },
            {
              "index": 1,
              "attributes": [
                {
                  "name": "ROLE",
                  "value": "221"
                },
                {
                  "name": "REAL_NAME",
                  "value": "John Smith"
                }
              ]
            }
          ]
        },
        {
          "name": "KEYWORDS",
          "type": "multi-value string",
          "value": [
            {
              "index": 0,
              "value": "Germany"
            },
            {
              "index": 1,
              "value": "Berlin"
            },
            {
               "value": "Politics"
            }
          ]
        }
      ]
    }
  }
}
 

MediaCentral Newsroom Management

The body is expected in NSML format. Content-Type must be set to application/vnd.com.avid.inews.nsml+xml.

Example request body:
 
<nsml version="4.1">
<head>
    <meta words="4" rate="180" wordlength="6" version="2"/>
    <formname>DEFAULT-FORM</formname>
    <storyid>0ba0af50:0000a8b9:56bc92a9</storyid>
</head>
<fields>
    <string id="title">Weather forecast</string>
    <date id="create-date">1453717480</date>
    <date id="modify-date">1455198889</date>
    <string id="modify-by">avstar</string>
</fields>
<body>
    <p>The weather is fine.</p>
</body>
</nsml>
 

You can also use ia:create-asset-with-position and ia:create-asset-with-position-and-lock to create an asset with NSML as body.

Wolftech Newsroom

The body is expected in the same format that is returned when getting the information about an asset. You must include an embedded aa:attributes resource to set custom attributes with mandatory attributes for each Wolftech News entity.

Stories and Pitches

For stories, and pitches, you must send an embedded aa:attributes resource with the attribute MainOrganization.

Example for creating a story
 
{
  "base": {
    "type": "wtn-story"
  },
  "common": {
    "name": "Test story",
    "description": "My <b>bold</b> description."
  },
  "_embedded": {
    "aa:attributes": {
      "attributes": [
        {
          "name": "MainOrganization",
          "value": "1"
        },
        {
          "name": "Offices",
          "value": [
            {
              "index": 0,
              "value": "2"
            },
            {
              "index": 1,
              "value": "3"
            }
          ]
        },
        {
          "name": "Custom_1",
          "value": "A good value"
        }
      ]
    }
  }
}
 

Publishing Outputs

For publishing outputs, you must send an embedded aa:attributes resource with the attributes StoryId, which identifies the story for which the publishing output is created, and PublishingFolders with at least one row with the sub attribute Folder.

Example for creating a publishing output
 
{
  "base": {
    "type": "wtn-pubpoint"
  },
  "common": {
    "name": "Example publishing output"
  },
  "_embedded": {
    "aa:attributes": {
      "attributes": [
        {
          "name": "StoryId",
          "value": "S3"
        },
        {
          "name": "PublishingFolders",
          "value": [
            {
              "index": 0,
              "attributes": [
                {
                  "name": "Folder",
                  "value": "15"
                },
                {
                  "name": "PublishingDate",
                  "value": "2025-06-26T15:01:24Z"
                }
              ]
            }
          ]
        }
      ]
    }
  }
}
 

Events

For events, you must send an embedded aa:attributes resource with the attributes Calendar, StartDateTime, and EndDateTime.

Example for creating an event
 
{
  "base": {
    "type": "wtn-event"
  },
  "common": {
    "name": "My new event #4"
  },
  "_embedded": {
    "aa:attributes": {
      "attributes": [
        {
          "name": "Calendar",
          "value": "3"
        },
        {
          "name": "Offices",
          "value": [
            {
              "index": 0,
              "value": "2"
            },
            {
              "index": 1,
              "value": "3"
            }
          ]
        },
        {
          "name": "StartDateTime",
          "value": "2025-05-26T17:29:49+01:00"
        },
        {
          "name": "EndDateTime",
          "value": "2025-05-26T19:29:49+01:00"
        },
        {
          "name": "TimeZoneKey2",
          "value": "Europe/Berlin"
        }
      ]
    }
  }
}