Circle API: Cannot change event hosts via Admin API V2

Summary

The Circle Admin API (V2) does not support changing or setting event hosts. When creating or updating events via the API, the community_member_id (event creator/host) is always set to the API token owner, and attempts to modify it are silently ignored.

What I Tried

Tested PATCH requests to /api/admin/v2/events/{id} with various field names:

// All of these were accepted (200 OK) but had no effect:
{ host_member_id: memberId }
{ community_member_id: memberId }
{ host: { community_member_id: memberId } }
{ hosts: [memberId] }
{ host_ids: [memberId] }
{ cohost_member_ids: [memberId] }
{ event_setting_attributes: { host_member_id: memberId } }

Also tested on event creation (POST) - same result. The host field in responses is always null, and community_member_id always reflects the API token owner.

Expected Behavior

Should be able to:

1. Set a different community member as the event host when creating events
2. Change the host of existing events via PATCH

Workaround Found

Circle's Headless API with member JWT tokens can create events on behalf of specific members:

1. Create a token named "Headless" in Circle (Developers → Tokens)
2. Use Auth API to get member JWT:

``bash
POST https://app.circle.so/api/v1/headless/auth_token
Authorization: Bearer <HEADLESS_TOKEN>
{"email": "member@example.com"}
``

1. Use returned access_token with Member API to create events as that member

Environment

• Circle Admin API V2 (https://app.circle.so/api/admin/v2)
• Business plan (API access enabled)

References

• Circle Developers Portal
• Headless API Docs
• V2 Events Documentation Issues (Community) - mentions Swagger docs are "inaccurate or misleading"