01.software Docs

Replace an event schedule through the protected action

Use the SDK for application integration. This read-only reference covers Commerce, Customer Auth, Membership and Events.

All HTTP operations
POST
/api/events/{id}/schedule

Operator-only shaped mutation for timed/all-day conversion and canonical all-day date or timezone edits. It serializes the event row and participant fence, rechecks every overlapping occurrence and durable participation source, and derives all-day shadows only after canonical dates are fixed.

Authorization

bearerAuth
headerAuthorizationBearer <token>

Public integration credentials: verified opaque sk01_ secret key or pat01_ personal access token; operation policy and read/write scopes still apply. These credentials are not Customer JWTs.

Path Parameters

id*string

Document ID

Request Body

application/json
  1. body
timezone?string

Optional IANA timezone.

schedule*|

Response Body

Authoritative schedule and compatibility shadows

application/json
  1. response
event*

Examples may be generated from schemas; they are illustrative, not recorded successful API calls. Example snippets may omit required authentication headers.

Example Request
curl -X POST 'https://api.01.software/api/events/string/schedule' \  -H 'Content-Type: application/json' \  -d '{  "schedule": {    "kind": "timed",    "startsAt": "2019-08-24T14:15:22Z",    "endsAt": "2019-08-24T14:15:22Z"  }}'
Example Response
{  "event": {    "id": "string",    "isAllDay": true,    "timezone": "string",    "startsAt": "2019-08-24T14:15:22Z",    "endsAt": "2019-08-24T14:15:22Z",    "allDayStartDate": "2019-08-24",    "allDayEndDateExclusive": "2019-08-24"  }}