Application Calendars

If you're building an application that requires scheduling for venues, properties, or any resource not tied to a specific person's calendar, Cronofy’s Application Calendars offer a flexible solution. They function as dedicated calendars within the Cronofy ecosystem, allowing you to leverage Cronofy's scheduling tools without the need for a "real" mailbox as a data store.

By using

POST /v1/application_calendars HTTP/1.1

Content-Type: application/json; charset=utf-8



{

  "client_id": {CLIENT_ID},

  "client_secret": {CLIENT_SECRET},

  "application_calendar_id": "my-unique-string"

}

You can then retrieve the calendar’s details as needed by using the same application_calendar_id for subsequent calls to the application_calendars endpoint. The response will include important information, such as the calendar’s access_token which is necessary for utilising Cronofy’s scheduling functionality with that calendar.

The application_calendar_id can be linked back to the meeting venue on the integrator’s side. This way, you can easily tie the Application Calendar to what it is managing availability for.

💡 The Application Calendar’s ID can be defined by the integrator and can be any string - for example, a GUID (globally unique identifier) or a numeric value.

Adding Events to Application Calendars

The process of creating events in an Application Calendar is the same as with user accounts. First, you retrieve the calendar_id via the

GET /v1/calendarsHTTP/1.1

Host: {data_center_url}

Authorization: Bearer {ACCESS_TOKEN}

Using the calendar_id and the access_token, you can then proceed with a call to create the event:

POST /v1/calendars/{calendar_id}/events HTTP/1.1

Host: {data_center_url}

Authorization: Bearer {ACCESS_TOKEN}

Content-Type: application/json; charset=utf-8



{

  "event_id": "qTtZdczOccgaPncGJaCiLg",

  "summary": "Board meeting",

  "description": "Discuss plans for the next quarter.",

  "start": "2024-10-26T15:30:00Z",

  "end": "2024-10-26T17:00:00Z",

  "location": {

    "description": "Board room"

  }

}

Using Application Calendars with scheduling functions

You can check an Application Calendar’s availability the same way you would with standard Cronofy accounts:

{

  "participants": [

    {

      "members": [

        { "sub": "apc_64b17fbb8090ea21640c9152" },

        { "sub": "acc_5ba21743f408617d1269ea1e" }

      ],

      "required": "all"

    }

  ],

  "required_duration": { "minutes": 60 },

  "available_periods": [

    {

      "start": "2024-10-25T09:00:00Z",

      "end": "2024-10-25T18:00:00Z"

    },

    {

      "start": "2024-10-26T09:00:00Z",

      "end": "2024-10-26T18:00:00Z"

    }

  ]

}

Other Cronofy functionalities that are supported by Application Calendars include:

• Assigning .


• Using the .


• Combining Cronofy’s calendar synchronisation and scheduling API with companion to any attendees, so that once accepted, the event is also created in the attendee’s calendar.
  Vollständiger Original-Bericht

  Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.

  ↗ Original-Artikel auf dev.to lesen