Structured Content Upload Issues

38 views
Skip to first unread message

Emmanuelle Sohn

unread,
Nov 16, 2023, 5:38:08 PM11/16/23
to Eventbrite Developers
Hi there, 

I'm trying to use the /structured content endpoint to create a description for my event, and although I am getting a 200 response, there is no structured content created or published. You can see this is the response, and I've verified with the get structured content endpoint. Has anyone encountered this issue/know how to resolve it?

Thanks!
Emmy

Request:

POST /v3/events/751776974167/structured_content/1 HTTP/1.1
Host: www.eventbriteapi.com
Authorization: Bearer [access_token]
Content-Type: application/json
Cookie: [cookie]
Content-Length: 215

{
  "modules": [
    {
      "type": "text",
      "data": {
        "body": {
          "type": "text",
          "text": "<h2>Hello World</h2>"
        }
      }
    }],
  "purpose": "listing",
  "publish": true
}

Response:
200
{
"resource_uris": {
},
"access_type": "not-apply",
"has_autogenerated_content": false,
"hide_virtual_venue_content": false,
"page_version_number": "1",
"purpose": "listing",
"modules": [],
"widgets": [],
"pagination": {
"object_count": 100,
"page_number": 1,
"page_size": 100,
"page_count": 1
}
}

Malcolm Taylor

unread,
Jun 13, 2024, 10:11:47 PM (9 days ago) Jun 13
to Eventbrite Developers
Not sure if you're still working on this, but have you tried incrementing the structured content page version number in the post call. 

You can get the "page_version_number" from the response in the structured content api call. More information can be found in the docs about structured content --  https://www.eventbrite.com/platform/api#/reference/structured-content 

So instead of  -- POST /v3/events/751776974167/structured_content/1
POST /v3/events/751776974167/structured_content/2

Hope that helps! let me know if you need code references. 

Best, 
Malcolm 

Emmanuelle Sohn

unread,
Jun 17, 2024, 3:32:38 PM (5 days ago) Jun 17
to Eventbrite Developers
Hi Malcom! Thanks so much for all that info! I did find the issue! It was that my POST needed a '/' after the page_version_number! 
Appreciate the help on this one!! : ) 

Emmy

Reply all
Reply to author
Forward
0 new messages