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 Reporting API

Swagger 2.0 contract for the Playbook aggregation/reporting service: performance summary and detail by team, rep, and playbook phase, achievement by unit and user, performance targets, playbook phase aggregation, MRR and contract sales reports, and input-form value reads. Authenticated with an x-access-token or x-api-key header.

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

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

22 operations 21 paths 31 schemas 19 GET3 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 2

Magic Moment Playbook Reporting 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 (apiKey).

Paths & Operations 22

Across 21 paths, the API surfaces 22 operations — 19 GET, 3 PUT. They span 7 resource areas: aggregate, healthcheck, performance-target, performance, playbook-phase, sales, value. Each is listed below with its method, path, parameters, and response codes.

aggregate 2
PUT
/aggregate/playbook-phases
savePlaybookReport 1 param → 200
PUT
/aggregate/playbook-phases/daily
saveDailyPlaybookReport 1 param → 200409
healthcheck 1
GET
/healthcheck
Your GET endpoint
get-healthcheck → 200
performance-target 3
GET
/performance-target/unit
getUnitPerformanceTarget 3 params → 200
GET
/performance-target/user
getUserPerformanceTarget 3 params → 200
PUT
/performance-target/user
savePerformanceTarget 1 param → 200
performance 9
GET
/reports/achievement/unit
getUnitAchievement 5 params → 200
GET
/reports/achievement/user
getUserAchievement 5 params → 200
GET
/reports/engagement-ids
getEngagementIdsOfPerformanceSummary 7 params → 200
GET
/reports/performance-detail/phase/{phaseValue}
getPhasePerformanceDetail 7 params → 200
GET
/reports/performance-detail/rep/{engagementOwnerId}
getRepPerformanceDetail 6 params → 200
GET
/reports/performance-detail/team
getTeamPerformanceDetail 6 params → 200
GET
/reports/performance-summary/phase
getPhasePerformanceSummary 4 params → 200
GET
/reports/performance-summary/rep
getRepPerformanceSummary 4 params → 200
GET
/reports/performance-summary/team
getTeamPerformanceSummary 4 params → 200
playbook-phase 4
GET
/reports/playbook-phases/{playbookPhaseId}/detail
Get Playbook Phase Details
getPlaybookDetailReport 3 params → 200
GET
/reports/playbook-phases/{playbookPhaseId}/items/summary
getPlaybookItemSummaryReport 6 params → 200
GET
/reports/playbook-phases/{playbookPhaseId}/items/{playbookItemId}/word-counts
listPlaybookItemWordCounts 6 params → 200
GET
/reports/playbook-phases/{playbookPhaseId}/summary
Get Playbook Summary
getPlaybookSummaryReport 5 params → 200
sales 2
GET
/reports/sales/contract
getContractSalesReport 6 params → 200
GET
/reports/sales/mrr
getMrrSalesReport 6 params → 200
value 1
GET
/values/playbook_input_forms/{playbookInputFormId}
getAchievedInputFormValues 3 params → 200

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are PerformanceSummaryValue (16 properties), playbookPhaseDetail (8 properties), playbookItemSummary (8 properties), playbookSummary (7 properties). Each schema is shown below with its type and property counts.

AchievedInputFormValue
object
2 properties
AchievedPhase
object
7 properties
DecisivePlaybookItem
object
2 properties
EngagementAssignment
object
6 properties
EngagementOwner
object
4 properties
FixedPhaseValue
object
4 properties
FormType
string
PerformanceDetailValue
array
PerformanceSummaryValue
object
16 properties 4 required
PerformanceTarget
object
4 properties
PerformanceTargetType
string
PhasePerformanceDetail
object
2 properties
PhasePerformanceSummary
array
PhaseValue
string
RepPerformanceDetail
object
2 properties
RepPerformanceSummary
array
SalesValue
object
4 properties 4 required
TeamPerformanceDetail
object
1 property
TeamPerformanceSummary
object
1 property
TeamPerformanceSummaryEngagementIds
object
1 property
UUID
string
UnitAchievement
object
1 property
UserAchievement
object
1 property
WordCount
object
2 properties
error
object
2 properties 1 required
playbookFormSummary
object
3 properties
playbookItemOptionSummary
object
2 properties
playbookItemSummary
object
8 properties
playbookPhaseDetail
object
8 properties
playbookSummary
object
7 properties
principal
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

magic-moment-reporting-openapi.yml Raw ↑
Where this information came from

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