Accept event with the Outlook Calendar API

Accepts a meeting invitation and, unless sendResponse is false, emails the response to the organizer. The response is 202 with no body.

Identifier
outlook_calendar_accept_event

The request

POST https://connect.reportei.com/api/tools/outlook_calendar_accept_event/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "event_id": "<event_id>"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
event_idstringYesEvent id from List events.
commentstringNoText sent with the response.
sendResponsebooleanNofalse answers without emailing the organizer. The default is true.

Supported connections

Your customer connects their Outlook Calendar account once, with one of the modes below. The same connection serves every tool of the toolkit.

OAuth with your product's app

You register your product's OAuth app once, with POST /api/merchants/credentials/outlook_calendar, and your customer authorizes the account on a consent screen. Connect renews the token when it is about to expire.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/outlook_calendar_accept_event. It becomes your agent's tool definition with no conversion.

Other Outlook Calendar tools

See all 10 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.