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

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.