CalendarEventInput
Fields for creating or (all optional, on PATCH) updating an event. Times are ISO 8601 and need a zone: a trailing Z, an offset, or `timezone`. A bare date makes an all-day event. Stored and returned as UTC instants.
Properties
| Name | Type | Description |
|---|---|---|
| title | string | |
| start | string | "2026-09-15T15:00:00Z", "2026-09-15T15:00:00-04:00", "2026-09-15T15:00:00" plus timezone, or "2026-09-15". |
| end | string | Omit to use duration_minutes (default 30). On PATCH, a moved start keeps the event's length. |
| duration_minutes | integer | |
| timezone | string | IANA zone for a local start/end with no offset, e.g. America/New_York. Also sets X-WR-TIMEZONE on the feed. |
| all_day | boolean | |
| description | string | |
| location | string | |
| status | string | |
| organizer | object | Defaults to the inbox itself. Only events the inbox organizes can be sent with invite; only events it does not can be answered with rsvp. |
| attendees | array | |
| ical_uid | string | Create only. Supply your own iCalendar UID; otherwise one is generated as {hex}@deadsimple.email. |
| sequence | integer | iCalendar SEQUENCE. Managed for you; set it only to take over from a calendar system that already sent this event. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/deadsimple-email/json-schema/deadsimple-email-calendar-event-input-schema.json",
"title": "CalendarEventInput",
"description": "Fields for creating or (all optional, on PATCH) updating an event. Times are ISO 8601 and need a zone: a trailing Z, an offset, or `timezone`. A bare date makes an all-day event. Stored and returned as UTC instants.",
"x-generated": "2026-11-05",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/deadsimple-email-openapi.json#/components/schemas/CalendarEventInput",
"type": "object",
"properties": {
"title": {
"type": "string",
"maxLength": 500
},
"start": {
"type": "string",
"description": "\"2026-09-15T15:00:00Z\", \"2026-09-15T15:00:00-04:00\", \"2026-09-15T15:00:00\" plus timezone, or \"2026-09-15\"."
},
"end": {
"type": "string",
"description": "Omit to use duration_minutes (default 30). On PATCH, a moved start keeps the event's length."
},
"duration_minutes": {
"type": "integer",
"minimum": 1
},
"timezone": {
"type": "string",
"description": "IANA zone for a local start/end with no offset, e.g. America/New_York. Also sets X-WR-TIMEZONE on the feed."
},
"all_day": {
"type": "boolean"
},
"description": {
"type": "string"
},
"location": {
"type": "string"
},
"status": {
"type": "string",
"enum": [
"confirmed",
"tentative",
"cancelled"
],
"default": "confirmed"
},
"organizer": {
"$ref": "#/$defs/CalendarOrganizer",
"description": "Defaults to the inbox itself. Only events the inbox organizes can be sent with invite; only events it does not can be answered with rsvp."
},
"attendees": {
"type": "array",
"maxItems": 100,
"items": {
"oneOf": [
{
"type": "string",
"format": "email"
},
{
"$ref": "#/$defs/CalendarAttendee"
}
]
}
},
"ical_uid": {
"type": "string",
"description": "Create only. Supply your own iCalendar UID; otherwise one is generated as {hex}@deadsimple.email."
},
"sequence": {
"type": "integer",
"description": "iCalendar SEQUENCE. Managed for you; set it only to take over from a calendar system that already sent this event."
}
},
"$defs": {
"CalendarAttendee": {
"type": "object",
"required": [
"email"
],
"properties": {
"email": {
"type": "string",
"format": "email"
},
"name": {
"type": "string"
},
"response": {
"type": "string",
"enum": [
"needs-action",
"accepted",
"declined",
"tentative"
],
"description": "The attendee's answer as last seen (our own rsvp, or their REPLY)."
},
"optional": {
"type": "boolean",
"description": "OPT-PARTICIPANT rather than REQ-PARTICIPANT on the invitation."
}
}
},
"CalendarOrganizer": {
"type": "object",
"properties": {
"email": {
"type": "string",
"format": "email"
},
"name": {
"type": "string"
}
}
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/json-schemas/deadsimple-email-calendar-event-input"
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.