Jump to content
View in the app

A better way to browse. Learn more.

Learn more

Feature Request / API Limitation: Image Attachments & Uploads in Calendar Events REST API

Featured Replies

Feature Request / API Limitation: Image Attachments & Uploads in Calendar Events REST API (POST /calendar/events)

(Regarding V5.X hosted solution)

When creating or editing calendar events via the frontend web UI, users can seamlessly upload an event Cover photo. The web form handles this via a multipart file uploader that generates a temporary attachment reference (attach_id) linked to the event record.

However, when utilizing the REST API endpoint (POST /calendar/events), the JSON payload schema does not expose a mechanism to pass binary image files, reference a remote image URL, or map an existing attachment ID. Consequently, programmatically created events are generated completely stripped of images.

Question:

  1. Is there an undocumented parameter, secondary endpoint, or ID mapping workflow within the current REST API to attach an image to a calendar event upon creation?

  2. If not, can the calendar events REST API schema be updated to support image attachments (either via multipart/form-data or an attachment ID reference) to achieve parity with the web UI?

AD_4nXcC-aI5tgdr6WeO4kDQ4-ZnKmVbss3IxzaB

Second this. I'm using Zapier to create events along with DB Records.

I assume this would allow Zapier to grab the image from the DB and use it in the Event.

JM

Agree with the OP.

Also, adding another related calendar REST API gap to this thread.

POST /calendar/events and POST /calendar/events/{id} have no venue parameter, so there’s seemingly no way to link an event to a venue through the API. The API clearly knows about venues: the event response already includes a venue object, and venues can be created and edited through /calendar/venues. Only setting the link from an event is missing.

This matters for SEO. Events linked to a venue output location.name in their Event structured data. Events created through the API can only send location, so they don’t, and Google Search Console flags every one with “Missing field ‘name’ (in ‘location’)”.

We import local events automatically, so linking hundreds of them by hand in the edit form isn’t practical. Could a venue(int, venue ID) parameter be added to both endpoints, please? It would be a small addition and would sit alongside the image upload support requested above.

You cannot use venues when posting events on the API currently. What exactly is showing in google search console?

Recently Browsing 0

  • No registered users viewing this page.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.