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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Magic Moment

Magic Moment Playbook Call Integration API

Swagger 2.0 contract for the Playbook call integration service: call-log capture (including MiiTel), call-provider settings, capability tokens for the softphone client, and conference control (create, hold music, join callback, status changes). Authenticated with an x-access-token header.

Documentation Provider Profile APIs.io OpenAPI GitHub

This API exposes 18 operations across 11 paths, organized into 5 resource areas, and defines 6 schemas. It is described by OpenAPI 2.0, at version 1.0.0.

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

18 operations 11 paths 6 schemas 2 DELETE6 GET8 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
1.0.0
Base URL
https://call.magicmoment.co.jp/
Authentication
API Key
Resource Areas
5

Authentication & Security 1

Magic Moment Playbook Call Integration API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-access-token (accessToken).

Paths & Operations 18

Across 11 paths, the API surfaces 18 operations — 2 DELETE, 6 GET, 8 POST, 2 PUT. They span 5 resource areas: call-log, settings, capability, conference, utils. Each is listed below with its method, path, parameters, and response codes.

call-log 3
GET
/call-log
Get call log
getCallLog 1 param → 200
POST
/call-log
Create Call log
createCallLog 1 param → 200
POST
/call-log/miitel
Create Call log for Miitel
createCallLogForMiitel 1 param → 200
settings 8
GET
/call-providers
Get call provider setting
getCallProviderSetting → 200
POST
/call-providers
Create call provider setting
createCallProviderSetting 1 param → 200
GET
/call-providers/miitel
Get Miitel setting
getMiitelSetting → 200
POST
/call-providers/miitel
Create Miitel setting
createMiitelSetting 1 param → 201
PUT
/call-providers/miitel/{settingId}
Update Miitel setting
updateMiitelSetting 2 params → 204
DELETE
/call-providers/miitel/{settingId}
Delete Miitel setting
deleteMiitelSetting 1 param → 200
PUT
/call-providers/{settingId}
Update call provider setting
updateCallProviderSetting 2 params → 200
DELETE
/call-providers/{settingId}
Delete call provider setting
deleteCallProviderSetting 1 param → 200
capability 2
GET
/call-providers/{settingId}/capability-token
Get token from Call center
GetCapabilityToken 1 param → 200
POST
/call-providers/{settingId}/capability-token
Authenticate when client connect to Call center
AuthCapabilityToken 2 params → 200
conference 4
GET
/call-providers/{settingId}/conference
Get xml setting for hold music
ConferenceHoldMusic 1 param → 200
POST
/call-providers/{settingId}/conference
Get xml setting for creating conference
ConferenceCreate 2 params → 200201
POST
/call-providers/{settingId}/conference/join-callback
Show xml setting for redirect call from phone numer to web client
ClientReceiveCallXml 4 params → 200
POST
/call-providers/{settingId}/conference/status
Hold / un-Hold the call by change conference status
ChangeConferenceStatus 2 params → 200
utils 1
GET
/healthcheck
ヘルスチェック
healthCheck → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are CallProviderSetting (7 properties), MiitelSetting (4 properties), Response (3 properties), principal (2 properties). Each schema is shown below with its type and property counts.

CallProviderSetting
object
7 properties
MiitelSetting
object
4 properties
Response
object
xml response for TwiML
3 properties
error
object
2 properties 1 required
operator
object
2 properties
principal
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

magic-moment-call-integration-openapi.yml Raw ↑
#Sales#CRM#Sales Automation#Integration#Japan
← Back to M APIs
API Details
ID
magic-moment:magic-moment-playbook-call-integration-api
Base URL
https://call.magicmoment.co.jp/
Docs
https://magicmoment.jp/playbook
Provider
Magic Moment
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=magic-moment-magic-moment-playbook-call-integration-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/magic-moment-magic-moment-playbook-call-integration-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Magic Moment Playbook Call 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.