Create new entry failing

When creating an new entry as per guidelines https://contentful.github.io/contentful-management.js/contentful-management/3.3.4/typedef/index.html#static-typedef-Entry I get the following error: (getting the space works correctly - this error happens when invoking space.createEntry({}).

{ BadRequest: {
  "status": 400,
  "statusText": "Bad Request",
  "message": "Missing object",
  "details": {},
  "request": {
    "url": "https://api.contentful.com:443/spaces/myspace/entries",
    "headers": {
      "Accept": "application/json, text/plain, */*",
      "Content-Type": "application/vnd.contentful.management.v1+json",
      "X-Contentful-User-Agent": "contentful-management.js/3.3.4",
      "Authorization": "Bearer ACCESS_TOKEN",
      "user-agent": "node.js/v6.10.0",
      "Accept-Encoding": "gzip",
      "X-Contentful-Content-Type": {}
    },
    "method": "post"
  },
  "requestId": "removedforissue"
}

If I put content into body

space.createEntry({
      fields: {
        title: {'en-AU': slugThisMonth},
        body: {
          file: {'en-AU': pdfAssetId},
          effectiveDate: {'en-AU': new Date().toISOString()},
          name: {'en-AU': slugThisMonth}
        }
      },
    })

I get the following error (much the same, just with the extra body)

{ BadRequest: {
  "status": 400,
  "statusText": "Bad Request",
  "message": "Missing object",
  "details": {},
  "request": {
    "url": "https://api.contentful.com:443/spaces/myspace/entries",
    "headers": {
      "Accept": "application/json, text/plain, */*",
      "Content-Type": "application/vnd.contentful.management.v1+json",
      "X-Contentful-User-Agent": "contentful-management.js/3.3.4",
      "Authorization": "Bearer ACCESS_TOKEN",
      "user-agent": "node.js/v6.10.0",
      "Accept-Encoding": "gzip",
      "X-Contentful-Content-Type": {
        "fields": {
          "title": {
            "en-AU": "cf-April-2017"
          },
          "body": {
            "file": {
              "en-AU": "afileid"
            },
            "effectiveDate": {
              "en-AU": "2017-04-05T04:09:55.461Z"
            },
            "name": {
              "en-AU": "cf-April-2017"
            }
          }
        }
      }
    },
    "method": "post"
  },
  "requestId": "removedforissue"
}

Following the documentation at https://www.contentful.com/developers/docs/references/content-management-api/#/reference/entries leads to the same path.

I do have content types setup, in my space, and can’t determine how to create an entry within a content type - maybe this is what i’m missing?

[axe312ger]

Ohh sorry, I overlooked that:

The first parameter of space.createEntry() is the content type as string, the second is your actual entry data.

Also, you need to create an asset first before you can attach it to the entry. (At least if you want to be present in the entry in the moment when the entry is created)

In total, it might later look like this:

space.createAsset({
  fields: {
    file: {
      'en-AU': { 
        contentType: 'image/jpeg',
        fileName: 'test.jpg',
        upload: 'http://www.example.com/test.jpg'
      }
    }
  }
})
.then(asset => asset.processForAllLocales())
.then(asset => asset.publish())
.then(function(asset) {
  return space.createEntry('doc', {
    fields: {
      file: {
        'en-AU': {
          sys: {
            id: asset.sys.id,
            linkType: 'Asset',
            type: 'Link'
          }
        }
      },
      effectiveDate: {'en-AU': new Date().toISOString()},
      name: {'en-AU': slugThisMonth},
      jiraId: {'en-AU': jiraId}
    },
  })
})
.then(function(entry) {
  console.log(entry)
})

Cheers, Benedikt

[bohdan-karapet-vaimo]

Hi, my comment is a bit outdated) I faced with same error and found that we need to pass 2 arguments to createEntry - first one is content type id and second one is entry itself.

I use "contentful-management": "^10.6.3"

Example: space.createEntry('contentTypeId', { fields: { ... } })

In the example above you can see that entry JSON was added to “X-Contentful-Content-Type” header: "X-Contentful-Content-Type": { "fields": { "title": { "en-AU": "cf-April-2017" }, ... } }

But this header is responsible for content type, as per Contentful API examples (saw in Contentful trainig video).