How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Magic Moment Playbook Office Suite Integration API

Swagger 2.0 contract for the Playbook office-suite integration service: calendar event create/list/update/delete across connected Google Workspace and Microsoft 365 accounts, mail sync (OAuth results queue, IMAP/SMTP credentials, attachments), Microsoft 365 webhook subscription handling, Zoom Phone call-log and recording capture, and OAuth 2.0 authorize/callback/deauthorization. Authenticated with an x-access-token or x-api-key header.

This API exposes 26 operations across 23 paths, organized into 7 resource areas, and defines 15 schemas. It is described by OpenAPI 2.0, at version 1.0.0.

Requests are made against the base URL https://suite.magicmoment.co.jp/.

26 operations 23 paths 15 schemas 2 DELETE12 GET5 PATCH6 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
1.0.0
Base URL
https://suite.magicmoment.co.jp/
Authentication
API Key, API Key
Resource Areas
7

Authentication & Security 2

Magic Moment Playbook Office Suite Integration API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-access-token (accessToken). An API key is passed in the header as x-api-key (apiToken).

Paths & Operations 26

Across 23 paths, the API surfaces 26 operations — 2 DELETE, 12 GET, 5 PATCH, 6 POST, 1 PUT. They span 7 resource areas: calendars, utils, mail, microsoft365, oauth2, profiles, zoom. Each is listed below with its method, path, parameters, and response codes.

calendars 6
POST
/calendars
カレンダーイベントを作成
createCalendarEvent 1 param → 200
GET
/calendars/events
カレンダーイベント一覧を取得
listCalendarEvents 2 params → 200
GET
/calendars/{calendarId}/{eventId}
Show calendar event
showCalendarEvents 3 params → 200
PUT
/calendars/{calendarId}/{eventId}
カレンダーイベントを更新
updateCalendarEvent 3 params → 200
DELETE
/calendars/{calendarId}/{eventId}
カレンダーイベントを削除
deleteCalendarEvent 3 params → 200
GET
/calendars/{userId}/events
List calendar events for selected user
listUserCalendarEvents 4 params → 200
utils 1
GET
/healthcheck
ヘルスチェック
healthCheck → 200
mail 5
GET
/mail/attachment/{mailAttachmentId}
添付メールダウンロード
getMailAttachment 1 param → 200
PATCH
/mail/oauth-results/enqueue
メール取り込み対象の oauthresults をエンキューする
enqueueOauthResultsForSyncMail → 204
PATCH
/mail/oauth-results/{oauthResultId}/sync
指定された oauthresultid に紐づくユーザーのメールを取り込む
syncMailByOauthResultId 1 param → 204
PATCH
/mail/smtp-imap-credentials/sync
smtp-imap-credentials に紐づくユーザーのメールを取り込む
syncMailByImap → 204
PATCH
/mail/syncdeprecated
Clientからのポーリングによるメール同期を廃止するため、本APIも合わせて廃止予定です。API自体が 404 を返さないようにするため、処理は行わず 204 を返します
syncMails → 204
microsoft365 2
PATCH
/microsoft365/subscription-expiration
Microsoft 365 サブスクリプションの有効期限を延長
updateMicrosoft365SubscriptionExpiration → 200500
POST
/microsoft365/webhook/subscription
Microsoft 365 Webhook サブスクリプションの受け取り
microsoft365WebhookSubscription 2 params → 200202
oauth2 5
GET
/oauth2/authorize
認証
startAuth 2 params → 200
DELETE
/oauth2/authorize
Unlink service
deleteAuth 1 param → 200
GET
/oauth2/callback
認証コールバック
callbackAuth 3 params → 200401
POST
/oauth2/deauthorization
サービスの認可取消し
deauthorization 3 params → 200401
GET
/oauth2/results
認証結果一覧
listOauthResults → 200
profiles 1
GET
/profiles/{userId}
プロフィールを取得
getProfile 1 param → 200
zoom 6
POST
/zoom-phone/call-logs
Zoom Phone の通話ログの永続化
createZoomPhoneCallLog 1 param → 200401
POST
/zoom-phone/call-logs/recording
ZoomPhone通話録音の取得と保存
saveUserRecording 1 param → 200401
GET
/zoom-phone/call-logs/recordings/{recodingId}/stream
recodingIdを元に録音データのstreamを取得する
getZoomPhoneRecodingDataStream 1 param → 200
GET
/zoom-phone/call-logs/{callLogId}
callLogIdを元にcallLogを取得する
getZoomPhoneCallLogById 1 param → 200
POST
/zoom-phone/webhook
zoomPhoneWebhook 4 params → 200
GET
/zoom-phone/{userId}/status
ユーザーのZoomPhone連携が有効になっているか確認する
verifyZoomPhoneActive 1 param → 200401

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are event (14 properties), createCalendarEventRequestBody (11 properties), mail (10 properties), entryPoint (5 properties). Each schema is shown below with its type and property counts.

createCalendarEventRequestBody
object
11 properties 2 required
createdAt
string
作成日
deauthorization
object
2 properties
entryPoint
object
5 properties
error
object
2 properties 1 required
event
object
14 properties
mail
object
10 properties
mailDestination
object
3 properties
meeting
object
2 properties
oauthResult
object
5 properties
operator
object
2 properties
principal
object
2 properties
profile
object
1 property
services
string
success
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

magic-moment-office-suite-integration-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of Magic Moment Playbook Office Suite Integration API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.