AddEvent Events API

The Events API from AddEvent — 2 operation(s) for events.

Operations 5

POST /events Create an event #
GET /events Search events #
GET /events/{event_id} Retrieve an event #
PATCH /events/{event_id} Update an event #
DELETE /events/{event_id} Delete an event #

Specifications

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/addevent:addevent-events-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

OpenAPI Specification

addevent-events-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  version: v2.14.0
  title: Calendar and Event Events API
  contact:
    name: AddEvent Inc
    email: support@addevent.com
servers:
- url: https://api.addevent.com/calevent/v2
security:
- bearerAuth: []
tags:
- name: Events
paths:
  /events:
    post:
      operationId: create-event
      summary: Create an event
      tags:
      - Events
      description: Creates a new event on an existing calendar.
      requestBody:
        $ref: '#/components/requestBodies/event-create'
      responses:
        '201':
          $ref: '#/components/responses/20x-event'
        '400':
          $ref: '#/components/responses/400-invalid-request-body'
    get:
      operationId: search-events
      summary: Search events
      tags:
      - Events
      description: Search for events you've previously created. Returns a search result object that contains an `events` property that contains an array of up to `page_size` events. If no events match the query, the resulting array will be empty.
      parameters:
      - $ref: '#/components/parameters/calendar-ids'
      - $ref: '#/components/parameters/event-ids'
      - $ref: '#/components/parameters/datetime-min'
      - $ref: '#/components/parameters/datetime-max'
      - $ref: '#/components/parameters/search'
      - $ref: '#/components/parameters/custom-data-key'
      - $ref: '#/components/parameters/custom-data-value'
      - $ref: '#/components/parameters/page'
      - $ref: '#/components/parameters/page-size'
      - $ref: '#/components/parameters/event-sort'
      - $ref: '#/components/parameters/sort-order'
      responses:
        '200':
          $ref: '#/components/responses/200-event-search'
        '400':
          $ref: '#/components/responses/400-invalid-query-parameters'
  /events/{event_id}:
    get:
      operationId: retrieve-event
      summary: Retrieve an event
      tags:
      - Events
      description: Retrieves an event object.
      parameters:
      - $ref: '#/components/parameters/event-id'
      responses:
        '200':
          $ref: '#/components/responses/20x-event'
        '404':
          $ref: '#/components/responses/404-not-found'
    patch:
      operationId: update-event
      summary: Update an event
      tags:
      - Events
      description: Updates an event by setting the values of the parameters passed. Any parameters not provided will be left unchanged. This request accepts mostly the same properties as the event creation call.
      parameters:
      - $ref: '#/components/parameters/event-id'
      requestBody:
        $ref: '#/components/requestBodies/event-update'
      responses:
        '200':
          $ref: '#/components/responses/20x-event'
        '400':
          $ref: '#/components/responses/400-invalid-request-body'
        '404':
          $ref: '#/components/responses/404-not-found'
    delete:
      operationId: delete-event
      summary: Delete an event
      tags:
      - Events
      description: Permenantly deletes an event. It cannot be undone.
      parameters:
      - $ref: '#/components/parameters/event-id'
      responses:
        '204':
          $ref: '#/components/responses/204-deleted'
        '404':
          $ref: '#/components/responses/404-not-found'
components:
  examples:
    event-search:
      value:
        pagination:
          current_page: 1
          next_page: 1
          previous_page: 1
          total_items: 2
          total_pages: 1
          page_size: 10
        links:
          next_page_url: https://api.addevent.com/calevent/v2/events&page=1
          previous_page_url: https://api.addevent.com/calevent/v2/events&page=1
        events:
        - $ref: '#/components/examples/event-min/value'
        - $ref: '#/components/examples/event-all/value'
    event-min:
      value:
        id: evt-0f571af553d8437eb6a9ce22384fdcba
        calendar_id: 1687480957492930
        unique_key: de16434237
        title: Event name
        internal_name: ''
        datetime_start: '2023-07-02 15:00:00'
        datetime_end: '2023-07-02 16:00:00'
        recurring_rule: ''
        all_day_event: false
        timezone: America/Los_Angeles
        description: ''
        location: ''
        location_id: 0
        organizer_name: ''
        organizer_email: ''
        reminder: 30
        free_busy: default
        color: 1
        landing_page_template_id: default
        rsvp_enabled: false
        rsvp:
          settings:
            rsvp_form_id: default
            seats_limited: false
            seats_limit: 50
            inactive: false
            notify_emails: ''
            notify_frequency: none
          stats:
            seats_left: 50
            count_total: 0
            count_going: 0
            count_maybe: 0
            count_cantgo: 0
        custom_data: {}
        link_long: https://www.addevent.com/event/de16434237
        link_short: https://evt.to/aougueghw
        created: '2023-07-19 23:46:13'
        modified: '2023-07-19 23:46:37'
    invalid-query-parameters:
      value:
        error_message: Attribute Validation Error
        invalid_param_responses:
        - name: sort_by
          reason: Invalid sorting field provided
        error_id: 1-655f6e3c-2597d3171a91c593213d3e40
    event-all:
      value:
        id: evt-0f571af553d8437eb6a9ce22384fdcba
        calendar_id: 1687480957492930
        unique_key: de16434237
        title: Event Title
        internal_name: Internal Event Name
        datetime_start: '2023-07-02 15:00:00'
        datetime_end: '2023-07-02 16:00:00'
        recurring_rule: FREQ=DAILY;COUNT=2
        all_day_event: false
        timezone: America/Los_Angeles
        description: This is a description of what the event is about.
        location: https://www.zoom.com/join/123456
        location_id: 0
        organizer_name: Firstname Lastname
        organizer_email: emailaddress@addevent.com
        reminder: 30
        free_busy: default
        color: 1
        landing_page_template_id: QnTHySwB6570
        rsvp_enabled: true
        rsvp:
          settings:
            rsvp_form_id: 8709VYGmXZOkJh
            seats_limited: false
            seats_limit: 50
            inactive: false
            notify_emails: ''
            notify_frequency: none
          stats:
            seats_left: 50
            count_total: 20
            count_going: 15
            count_maybe: 3
            count_cantgo: 2
        custom_data:
          internal_id: 123456
          bannerimage: https://cdn.example.org/banner1.jpg
        link_long: https://www.addevent.com/event/de16434237
        link_short: https://evt.to/aougueghw
        created: '2023-07-19 23:46:13'
        modified: '2023-07-19 23:46:37'
    event-body:
      value:
        title: Event name
        datetime_start: 2024-06-01 10:00
        datetime_end: 2024-06-01 11:00
        timezone: America/Los_Angeles
        recurring_rule: FREQ=DAILY;COUNT=2
        landing_page_template_id: default
        rsvp_form_id: default
    invalid-request-body:
      value:
        error_message: There are a number of validation errors with the request
        error_id: 00c3317d-ecdc-449d-84f5-8562bc1ff831
        property_validation_errors:
        - name: rrule
          reason: Not a valid RRule value
        - name: title
          reason: Cannot have blank value
  responses:
    400-invalid-request-body:
      description: Bad request
      content:
        application/json:
          schema:
            type: object
            properties:
              error_id:
                type: string
                description: A UUID which can be used to troubleshoot the error.
              error_message:
                type: string
                description: Additional information about the error.
              property_validation_errors:
                type: array
                items:
                  type: object
                  properties:
                    name:
                      type: string
                    reason:
                      type: string
                description: An array of invalid property names, and the associated reason that the property is invalid.
          examples:
            Invalid request body:
              $ref: '#/components/examples/invalid-request-body'
    204-deleted:
      description: Deleted successfully
    400-invalid-query-parameters:
      description: Bad request
      content:
        application/json:
          schema:
            type: object
            properties:
              error_id:
                type: string
                description: A UUID which can be used to troubleshoot the error.
              error_message:
                type: string
                description: Additional information about the error.
              property_validation_errors:
                type: array
                items:
                  type: object
                  properties:
                    name:
                      type: string
                    reason:
                      type: string
                  description: An array of invalid parameter names, and the associated reason that the property is invalid.
          examples:
            Invalid query parameters:
              $ref: '#/components/examples/invalid-query-parameters'
    404-not-found:
      description: Not found
    20x-event:
      description: Ok
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/event'
          examples:
            Event:
              $ref: '#/components/examples/event-min'
            Event 2:
              $ref: '#/components/examples/event-all'
    200-event-search:
      description: Ok
      content:
        application/json:
          schema:
            type: object
            properties:
              pagination:
                $ref: '#/components/schemas/pagination'
              links:
                $ref: '#/components/schemas/links'
              events:
                type: array
                items:
                  $ref: '#/components/schemas/event'
          examples:
            Search results:
              $ref: '#/components/examples/event-search'
  schemas:
    event-input:
      type: object
      properties:
        title:
          type: string
          pattern: ^(?!\s*$).+
          description: The event's title. It must be a non-empty, single-line string.
        calendar_id:
          type: string
          pattern: ^(?!\s*$).+
          description: The ID of the calendar that this event will be associated with. Defaults to the default calendar on the account if not provided.
        datetime_start:
          type: string
          pattern: ^\d{4}-\d{2}-\d{2}(\s\d{2}:\d{2}(:\d{2})?)?$
          description: 'The start date & time of the event. Accepts datetimes in the following formats:


            * `YYYY-MM-DD hh:mm:ss` e.g. 2023-11-28 10:00:00

            * `YYYY-MM-DD hh:mm` e.g. 2023-11-28 10:00

            * `YYYY-MM-DD` e.g. 2023-11-28

            '
        datetime_end:
          type: string
          pattern: ^\d{4}-\d{2}-\d{2}(\s\d{2}:\d{2}(:\d{2})?)?$
          description: 'The end date & time of the event. Accepts datetimes in the following formats:


            * `YYYY-MM-DD hh:mm:ss` e.g. 2023-11-28 10:00:00

            * `YYYY-MM-DD hh:mm` e.g. 2023-11-28 10:00

            * `YYYY-MM-DD` e.g. 2023-11-28


            Defaults to `datetime_start + 1 hour` if not set.

            '
        all_day_event:
          type: boolean
          default: false
          description: Whether the event is an all day event. If `true` then the start and end time of the event are ignored, and only the date is used.
        timezone:
          type: string
          pattern: ^(?!\s*$).+
          description: 'The event''s timezone. This ensures that the event appears at the correct time for users regardless of their timezone.


            The `List timezones` endpoint returns all of the timezone values that are supported, or you can use our <a href="https://www.addevent.com/c/documentation/tools/time-zone-lookup" target="_blank">Timezone Lookup Tool</a> to find a timezone. Defaults to the calendar''s timezone if not provided.


            This property also accepts the value `floating`, which means that the event will appear at the same time in each user''s timezone. For example, the event will be at 2 pm local time for users in Paris and 2 pm for local time for users in San Francisco.

            '
        recurring_rule:
          type: string
          pattern: (?:(\w+)=((?:(?:[^;,=]+,?)*[^;,=])|"(?:[^"]|"")*");?)+
          description: 'The event''s recurring rule which must use the iCalendar Standard''s format. See our <a href="https://www.addevent.com/c/documentation/tools/recurring-rule-generator" target="_blank">Recurring Rule Generator</a> for help with generating valid recurring rules.


            Leave this property empty to create an even that does not repeat.


            **Please note:**

            1. Recurring rules are advanced functionality and need to be tested before using them.

            2. `datetime_start` must match the recurring rule to work in strict calendar systems like Outlook (desktop) and Apple Calendar.

            3. Recurring rules are not supported by Yahoo Calendar.

            '
        description:
          type: string
          description: 'The event''s description. This field accepts plain text or simplified HTML. Use `\n` to create a new line. Simplified HTML is not supported by all calendar clients, in which case, the content will be automatically converted into readable text.


            **Please note:** We recommend keeping your description short and to the point, with a maximum of 500 characters. Some browsers (e.g., Microsoft Edge) limit the number of characters that can be transferred in a URL, so this limit ensures that your event is cross-browser compatible.

            '
        internal_name:
          type: string
          description: An internal name for the event which will not be displayed publicly. This can be used internally to distinguish between events, to add additional information/context to an event, or to store an external ID that relates to another system.
        location:
          type: string
          description: The event's location. This can be an address or a URL, for example, a meeting or webinar link. Only one of `location` and `location_id` can be provided.
        location_id:
          type: integer
          minimum: 0
          description: The ID of the saved location to associate with the event. The value `0` means that a saved location is not being used. Only one of `location` and `location_id` can be provided.
        organizer_name:
          type: string
          description: The event organizer's name. If `organizer_name` is provided, then `organizer_email` must also be provided. The organizer information is displayed on the event landing page, and including an organizer means the event is considered a `meeting` by calendar clients such as Outlook (desktop) rather than an `appointment`.
        organizer_email:
          type: string
          format: email
          pattern: ^$|^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$
          description: The event organizer's email address. If `organizer_email` is provided, then `organizer_name` must also be provided. The organizer information is displayed on the event landing page, and including an organizer means the event is considered a `meeting` by calendar clients such as Outlook (desktop) rather than an `appointment`.
        reminder:
          type: integer
          minimum: 0
          maximum: 10800
          default: 30
          description: 'The number of minutes prior to the start of an event that a reminder notification will be sent to the user via their calendar app. Event reminders are currently only supported by:

            * Apple calendar

            * Outlook desktop

            * Office 365 and Outlook.com (when using the Microsoft Events API)

            '
        color:
          type: integer
          minimum: 1
          maximum: 20
          default: 1
          description: The event's color. This appears in the dashboard and on calendar landing pages or embeddable calendars. Accepts values between `1` and `20` that correspond to the colors on the calendar's palette.
        free_busy:
          type: string
          enum:
          - free
          - busy
          - default
          default: default
          description: 'Indicates whether the event appears as *free* or *busy* when the user adds it to their calendar. Accepts the following values:

            * `free`: the event appears as free and does not block the user''s calendars

            * `busy`: the event appears as busy and blocks the user''s calendar

            * `default`: the event uses the user''s default free/busy setting

            '
        landing_page_template_id:
          type: string
          pattern: ^(?!\s*$).+
          default: default
          description: The ID of the custom event landing page template to associate with the event. Accepts the value `default`, which uses the standard AddEvent template, or the ID of a custom template, which can be retrieved with the `List event templates` endpoint.
        rsvp_enabled:
          type: boolean
          default: false
          description: Whether the event requires a user to respond and enter their information before adding the event to their calendar.
        rsvp_form_id:
          type: string
          pattern: ^(?!\s*$).+
          default: default
          description: The ID of the custom RSVP form to associate with the event. Accepts the value `default`, which uses the standard AddEvent template, or the ID of a custom RSVP form, which can be retrieved with the `List RSVP forms` endpoint.
        custom_data:
          type: object
          description: Arbitary key-value pairs that can be attached to an event. Useful for storing additional structured data on an object, for example, storing external IDs to link an event to another system or linking to custom images for each event. `snake_case` should be used for custom data keys.
    event-rsvp-stats:
      type: object
      properties:
        seats_left:
          type: integer
          description: The number of seats left for the event. Calculated as `seats_limit - count_going`.
        count_total:
          type: integer
          description: The total number of RSVP attendees who have responded to an event, regardless of their response.
        count_going:
          type: integer
          description: The number of RSVP attendees who have responded `going` to an event.
        count_maybe:
          type: integer
          description: The number of RSVP attendees who have responded `maybe` to an event.
        count_cantgo:
          type: integer
          description: The number of RSVP attendees who have responded `not-going` to an event.
      description: The event's RSVP stats.
    event-rsvp-settings:
      type: object
      properties:
        rsvp_form_id:
          type: string
          description: The ID of the custom event landing page template that is associated with the event. The value `default` indicates that the standard AddEvent template is being used.
        seats_limited:
          type: boolean
          description: Whether the number of seats for an event is limited. If `true`, then a limit of `seats_limit` responses applies to the event. If `false` there is no limit to the number of responses that will be accepted.
        seats_limit:
          type: integer
          description: The number of seats that the event is limited to. Once this limit is reached, no additional responses will be accepted for the event.
        inactive:
          type: boolean
          description: Whether the event is still accepting RSVP responses. If `true`, then no additional responses will be accepted for the event.
        notify_emails:
          type: string
          description: A comma-separated list of email addresses that will be sent internal notification emails based on the `notify_frequency` setting.
        notify_frequency:
          type: string
          description: 'Indicates how often internal notification emails should be sent for new RSVP attendees:


            * `none`: don''t send any notification emails

            * `all`: send a notification email for each new RSVP attendee

            * `summary`: send a daily summary email with a list of the new RSVP attendees from that day

            '
      description: The event's RSVP settings. These settings only apply if `rsvp_enabled` is set to `true`.
    event-input-update:
      allOf:
      - $ref: '#/components/schemas/event-input'
      - type: object
        properties:
          datetime_end:
            type: string
            pattern: ^\d{4}-\d{2}-\d{2}(\s\d{2}:\d{2}(:\d{2})?)?$
            description: 'The end date & time of the event. Accepts datetimes in the following formats:


              * `YYYY-MM-DD hh:mm:ss` e.g. 2023-11-28 10:00:00

              * `YYYY-MM-DD hh:mm` e.g. 2023-11-28 10:00

              * `YYYY-MM-DD` e.g. 2023-11-28

              '
          calendar_id:
            type: string
            pattern: ^(?!\s*$).+
            description: The ID of the calendar the event is associated with.
    event:
      type: object
      properties:
        id:
          type: string
          description: Unique identifier for the event.
        unique_key:
          type: string
          description: Public identifier for the event that is used for sharing the event.
        title:
          type: string
          description: The event's title.
        calendar_id:
          type: string
          description: The ID of the calendar that the event is associated with.
        datetime_start:
          type: string
          description: The start date & time of the event. Datetimes are in `YYYY-MM-DD hh:mm:ss` format e.g. 2023-11-28 10:00:00
        datetime_end:
          type: string
          description: The end date & time of the event. Datetimes are in `YYYY-MM-DD hh:mm:ss` format e.g. 2023-11-28 10:00:00
        all_day_event:
          type: boolean
          description: Whether the event is an all day event.
        timezone:
          type: string
          description: The event's timezone. The value `floating` means that the event will appear at the same time in each user's timezone. For example, the event will be at 2 pm local time for users in Paris and 2 pm local time for users in San Francisco.
        recurring_rule:
          type: string
          description: The event's recurring rule in the iCalendar Standard's format. If this value is empty, then the event does not repeat.
        description:
          type: string
          description: The event's description.
        internal_name:
          type: string
          description: An internal name for the event. This will not be displayed publicly.
        location:
          type: string
          description: The location of the event. This can be an address or a URL, for example, a meeting or webinar link.
        location_id:
          type: integer
          description: The ID of a saved location that is associated with the event. The value `0` indicates that a saved location is not being used.
        organizer_name:
          type: string
          description: The event organizer's name.
        organizer_email:
          type: string
          format: email
          description: The event organizer's email.
        reminder:
          type: integer
          description: 'The number of minutes prior to the start of an event that a reminder notification will be sent to the user via their calendar app. Event reminders are currently only supported by:

            * Apple Calendar

            * Outlook desktop

            * Office 365 and Outlook.com (when using the Microsoft Events API)

            '
        color:
          type: integer
          description: The event's color. This appears in the dashboard and on calendar landing pages or embeddable calendars. Values are between `1` and `20` and correspond to the colors on the calendar's palette.
        free_busy:
          type: string
          description: Indicates whether the event appears as *free* or *busy* in the user's calendar. Values are `free`, `busy`, or `default`.
        landing_page_template_id:
          type: string
          description: The ID of the custom event landing page template that is associated with the event. The value `default` indicates that the standard AddEvent template is being used.
        rsvp_enabled:
          type: boolean
          description: Whether the event requires a user to respond and enter their information before adding the event to their calendar.
        rsvp:
          type: object
          properties:
            settings:
              $ref: '#/components/schemas/event-rsvp-settings'
            stats:
              $ref: '#/components/schemas/event-rsvp-stats'
        custom_data:
          type: object
          description: Arbitary key-value pairs that can be attached to an event. Useful for storing additional structured data on an object, for example, storing external IDs to link an event to another system or linking to custom images for each event.
        link_long:
          type: string
          description: The public URL to the event landing page. Used for sharing the event.
        link_short:
          type: string
          description: The public short URL to the event landing page. Used for sharing the event.
        created:
          type: string
          description: Time at which the event was created.
        modified:
          type: string
          description: Time at which the event was last updated.
    links:
      type: object
      properties:
        next_page_url:
          type: string
          description: Link to the next page of search results.
        previous_page_url:
          type: string
          description: Link to the previous page of search results.
      description: Links to additional search results.
    pagination:
      type: object
      properties:
        current_page:
          type: integer
          description: Page number of the current page of search results.
        next_page:
          type: integer
          description: Page number of the next page of search results.
        previous_page:
          type: integer
          description: Page number of the previous page of search results.
        total_items:
          type: integer
          description: The total number of objects in the search results.
        total_pages:
          type: integer
          description: The total number of pages of search results.
        page_size:
          type: integer
          description: The number of search results per page
      description: Meta data about the search results and paging.
  parameters:
    page:
      name: page
      in: query
      schema:
        type: integer
        minimum: 1
        default: 1
      description: Page number of the search results. The first page of results is `page=1`.
    page-size:
      name: page_size
      in: query
      schema:
        type: integer
        minimum: 1
        maximum: 20
        default: 10
      description: A limit on the number of objects to be returned. `page_size` must be between 1 and 20, and the default is 10.
    event-ids:
      name: event_ids
      in: query
      style: form
      explode: false
      schema:
        type: array
        items:
          type: string
          pattern: ^\S+$
      description: Comma-separated list of event IDs. Limits search results to those specific events.
    calendar-ids:
      name: calendar_ids
      in: query
      style: form
      explode: false
      schema:
        type: array
        items:
          type: string
          pattern: ^\S+$
      description: Comma-separated list of calendar IDs. Limits search results to those specific calendars.
    event-sort:
      name: sort_by
      in: query
      schema:
        type: string
        enum:
        - created
        - title
        - calendar_id
        - datetime_start
        default: created
      description: The event property to sort by. Allowed values are `created`, `title`, `calendar_id`, or `datetime_start`. If `sort_order` is provided, then `sort_by` must also be provided. The default sorting is `created, desc` *unless* `datetime_start` or `datetime_end` is provided, in which case the default sorting is `datetime_start, asc`.
    event-id:
      name: event_id
      in: path
      required: true
      schema:
        type: string
        pattern: ^\S+$
      description: Unique identifier for the event.
    sort-order:
      name: sort_order
      in: query
      schema:
        type: string
        enum:
        - asc
        - desc
        default: desc
      description: The order of the returned search results, sorted by the property specified in `sort_by`. Allowed values are `asc` or `desc`. If `sort_order` is provided, then `sort_by` must also be provided.
    datetime-max:
      name: datetime_max
      in: query
      schema:
        type: string
        pattern: ^\d{4}-\d{2}-\d{2}(\s\d{2}:\d{2}(:\d{2})?)?$
      description: 'Limits search results to events that *start before* this time, i.e. `datetime_start =< datetime_max`. Timezones are not considered when doing this comparison, it simply compares the naive datetimes. If `datetime_max` is provided, then the default sorting is changed to `datetime_start, asc`.


        Accepts datetimes in the following formats:


        * `YYYY-MM-DD hh:mm:ss` e.g. 2023-11-28 10:00:00

        * `YYYY-MM-DD hh:mm` e.g. 2023-11-28 10:00

        * `YYYY-MM-DD` e.g. 2023-11-28

        '
    custom-data-key:
      name: custom_data_key
      in: query
      schema:
        type: string
      description: Limits search results to objects with a given key-value pair in the `custom_data` field. If `custom_data_key` is provided, then `custom_data_value` must also be provided.
    datetime-min:
      name: datetime_min
      in: query
      schema:
        type: string
        pattern: ^\d{4}-\d{2}-\d{2}(\s\d{2}:\d{2}(:\d{2})?)?$
      description: 'Limits search results to events that *end after* this time, i.e. `datetime_end >= datetime_min`. Timezones are not considered when doing this comparison, it simply compares the naive datetimes. If `datetime_min` is provided, then the default sorting is changed to `datetime_start, asc`.


        Accepts datetimes in the following formats:


        * `YYYY-MM-DD hh:mm:ss` e.g. 2023-11-28 10:00:00

        * `YYYY-MM-DD hh:mm` e.g. 2023-11-28 10:00

        * `YYYY-MM-DD` e.g. 2023-11-28

        '
    custom-data-value:
      name: custom_data_value
      in: query
      schema:
        type: string
      description: Limits search results to objects with a given key-value pair in the `custom_data` field. If `custom_data_value` is provided, then `custom_data_key` must also be provided.
    search:
      name: search
      in: query
      schema:
        type: string
      description: Search term that searches across an event's `title`, `internal_name`, `description`, and `location`. Searches are case-insensitive.
  requestBodies:
    event-create:
      required: true
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/event-input'
            required:
            - title
            - datetime_start
          examples:
            Request body:
              $ref: '#/components/examples/event-body'
    event-update:
      required: true
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/event-input-update'
          examples:
            Request body:
              $ref: '#/components/examples/event-body'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: APIkey
      description: Your API key can be found on your AddEvent account page - https://dashboard.addevent.com/account/settings
x-provenance:
  method: searched
  source: https://docs.addevent.com/reference
  harvested: '2026-10-27'
  tool: harvest-readme-openapi.py
  note: Assembled verbatim from the OpenAPI definition ReadMe embeds in each operation page of the provider's developer portal; paths and components merged by API title, nothing authored.
  assembled_from:


# --- truncated at 32 KB (33 KB total) ---
# Full source: https://artifacts.apis.io/addevent/openapi/addevent-events-api-openapi.yml