Acall

Q: How much does the Acall API cost?

Acall publishes its prices; its 月額費用 plan is 会議室数に合わせて お見積り as of 2026-10-28. APIs.io lists 2 pricing plans for Acall, with each plan's price, limits and inclusions under Pricing on this page.

Acall Inc. (アコール株式会社) is a Japanese workplace-experience software company, founded in 2010 and headquartered in Tokyo with a Kobe office, whose Acall / WorkstyleOS platform runs the physical side of hybrid work for more than 7,000 organizations. The product is a set of check-in surfaces — Acall Reception (iPad visitor reception and entry/exit records), Acall Meeting (meeting-room booking and utilization), Acall Desktop (free-address desk and workspace "spot" reservation / hoteling), Acall Gate (entry-gate integration), AI Meeting, Neat device integration and a multi-tenant building mode — stitched to Microsoft 365 and Google Calendar, Teams/Slack/Chatwork notifications, and SSO/SCIM-style provisioning. Acall publishes a REST "Acall Public API" (v1, bearer token) covering workers, facilities, events, gate access logs, spots and spot reservations, plus an outbound Webhook surface for appointment and internal-meeting events. API access is not self-serve: a token is issued only after a request through the contact form, and the API is unavailable on the multi-tenant plan.

Acall publishes 6 API contracts indexed on the APIs.io network, including Event API, Facility API, Gate API, and 3 more. Tagged areas include Workplace Management, Visitor Management, Meeting Room Booking, Desk Booking, and Hybrid Work.

The Acall catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Acall’s developer surface includes engineering blog, authentication, documentation, API reference, support, pricing, changelog, and 24 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

51.3/100 developing ▬ flat Agent 29/100 agent ready Front door AI 1/6 silent Heartbeat 64/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 2 Agent Skills

Workplace Management Visitor ManagementMeeting Room BookingDesk Booking Hybrid Work Access Control Facilities Smart Office Japan Software-as-a-Service

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Facilities Management

BC-700

Spot Reservation API

POST /spot_reservations/

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 51.3/100 · developing

Contract Quality 10.0 / 19

Developer Ergonomics 5.6 / 15

Access Clarity 10.1 / 15

Operational Transparency 5.1 / 10

Contract Governance 1.6 / 9

Discoverability 5.0 / 8

Regulatory Posture 4.4 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 29/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/acall/"><img src="https://apis.io/badge/acall/card.svg" alt="Acall on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

6 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Developer Ergonomics scores 37.5 — up to +12.5 composite points
Contract Quality scores 53.1 — up to +11.7 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/acall/apis.yml: open an issue on github.com/api-evangelist/acall to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Japan ISMAP Cloud Security Assessments (TISAX unreadable)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

SCIM 2.0

prose — states compatibility; nothing published to check it against

5 core of 24 operations graded · api-commons/identity

OpenAPI

measured — observed by APIs.io (published)

APIs 6

Individual APIs this provider publishes, each with its own machine-readable definition.

Acall Event API

The Event API API from Acall — 2 operation(s) for event api.

Acall Facility API

The Facility API API from Acall — 2 operation(s) for facility api.

Acall Gate API

The Gate API API from Acall — 1 operation(s) for gate api.

Acall Spot API

The Spot API API from Acall — 1 operation(s) for spot api.

Acall Spot Reservation API

The Spot Reservation API API from Acall — 2 operation(s) for spot reservation api.

Acall User API

The User API API from Acall — 2 operation(s) for user api.

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Book a workspace for a worker in Acall

AGENT SKILL

Reconcile Acall appointments against entry-gate access logs

AGENT SKILL

Acall API pricing

Prices published by Acall, read 2026-10-28 from www.workstyleos.com/pricing/.

Plan	Price
月額費用	会議室数に合わせてお見積り
初期費用	機器類・導入サポート(オプション)

Plan details, limits and sources →

Pricing Plans 1

Published pricing tiers and plan structures.

Acall Plans Pricing

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Acall Rate Limits

0 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Acall

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Acall Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Acall Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Acall API Rules

51 rules · 47 errors 3 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Acall Public Api Overlay

6 actions · documentation · acall-public-api-openapi.yml

DERIVED

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Acall Authentication

http · 1 scheme

SECURITY

Acall Domain Security

TLSv1.3 · DMARC

SECURITY

Acall Trust Center

ISO/IEC 27001 (ISMS)

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Acall Agentic Access

13 operations · 3 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

AgentSkill

AgentSkill

LLMsTxt

LLMsTxt

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Webhooks

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Compliance

Compliance

Operate 5

Status, limits, changes, and where to get help

Support

StatusPage

ChangeLog

RateLimits

ChangeLog

Commercial 4

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

Plans

Company 3

The organization behind the API

Blog

Blog

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: acall
name: Acall
description: 'Acall Inc. (アコール株式会社) is a Japanese workplace-experience software company, founded in 2010 and headquartered
  in Tokyo with a Kobe office, whose Acall / WorkstyleOS platform runs the physical side of hybrid work for more than 7,000
  organizations. The product is a set of check-in surfaces — Acall Reception (iPad visitor reception and entry/exit records),
  Acall Meeting (meeting-room booking and utilization), Acall Desktop (free-address desk and workspace "spot" reservation
  / hoteling), Acall Gate (entry-gate integration), AI Meeting, Neat device integration and a multi-tenant building mode —
  stitched to Microsoft 365 and Google Calendar, Teams/Slack/Chatwork notifications, and SSO/SCIM-style provisioning. Acall
  publishes a REST "Acall Public API" (v1, bearer token) covering workers, facilities, events, gate access logs, spots and
  spot reservations, plus an outbound Webhook surface for appointment and internal-meeting events. API access is not self-serve:
  a token is issued only after a request through the contact form, and the API is unavailable on the multi-tenant plan.'
url: https://raw.githubusercontent.com/api-evangelist/acall/refs/heads/main/apis.yml
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - plans
  - authentication
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
image: https://www.workstyleos.com/images/common/ogp/acall_ogp.png
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-09-06'
modified: '2026-10-06'
tags:
- Workplace Management
- Visitor Management
- Meeting Room Booking
- Desk Booking
- Hybrid Work
- Access Control
- Facilities
- Smart Office
- Japan
- Software-as-a-Service
tags_raw:
- workplace-management
- visitor-management
- meeting-room-booking
- desk-booking
- hybrid-work
- access-control
- facilities
- smart-office
- japan
- saas
apis:
- aid: acall:acall-event-api-api
  name: Acall Event API
  description: The Event API API from Acall — 2 operation(s) for event api.
  humanURL: https://www.workstyleos.com/publicapi/index.html
  baseURL: https://api.workstyleos.com/v1/
  tags:
  - Event API
  properties:
  - type: OpenAPI
    url: openapi/acall-event-api-api-openapi.yml
  - type: APIReference
    url: https://www.workstyleos.com/publicapi/index.html
  - type: Documentation
    url: https://support.workstyleos.com/faq/show/598?site_domain=default
- aid: acall:acall-facility-api-api
  name: Acall Facility API
  description: The Facility API API from Acall — 2 operation(s) for facility api.
  humanURL: https://www.workstyleos.com/publicapi/index.html
  baseURL: https://api.workstyleos.com/v1/
  tags:
  - Facility API
  properties:
  - type: OpenAPI
    url: openapi/acall-facility-api-api-openapi.yml
  - type: APIReference
    url: https://www.workstyleos.com/publicapi/index.html
  - type: Documentation
    url: https://support.workstyleos.com/faq/show/598?site_domain=default
- aid: acall:acall-gate-api-api
  name: Acall Gate API
  description: The Gate API API from Acall — 1 operation(s) for gate api.
  humanURL: https://www.workstyleos.com/publicapi/index.html
  baseURL: https://api.workstyleos.com/v1/
  tags:
  - Gate API
  properties:
  - type: OpenAPI
    url: openapi/acall-gate-api-api-openapi.yml
  - type: APIReference
    url: https://www.workstyleos.com/publicapi/index.html
  - type: Documentation
    url: https://support.workstyleos.com/faq/show/598?site_domain=default
- aid: acall:acall-spot-api-api
  name: Acall Spot API
  description: The Spot API API from Acall — 1 operation(s) for spot api.
  humanURL: https://www.workstyleos.com/publicapi/index.html
  baseURL: https://api.workstyleos.com/v1/
  tags:
  - Spot API
  properties:
  - type: OpenAPI
    url: openapi/acall-spot-api-api-openapi.yml
  - type: APIReference
    url: https://www.workstyleos.com/publicapi/index.html
  - type: Documentation
    url: https://support.workstyleos.com/faq/show/598?site_domain=default
- aid: acall:acall-spot-reservation-api-api
  name: Acall Spot Reservation API
  description: The Spot Reservation API API from Acall — 2 operation(s) for spot reservation api.
  humanURL: https://www.workstyleos.com/publicapi/index.html
  baseURL: https://api.workstyleos.com/v1/
  tags:
  - Spot Reservation API
  properties:
  - type: OpenAPI
    url: openapi/acall-spot-reservation-api-api-openapi.yml
  - type: APIReference
    url: https://www.workstyleos.com/publicapi/index.html
  - type: Documentation
    url: https://support.workstyleos.com/faq/show/598?site_domain=default
- aid: acall:acall-user-api-api
  name: Acall User API
  description: The User API API from Acall — 2 operation(s) for user api.
  humanURL: https://www.workstyleos.com/publicapi/index.html
  baseURL: https://api.workstyleos.com/v1/
  tags:
  - User API
  properties:
  - type: OpenAPI
    url: openapi/acall-user-api-api-openapi.yml
  - type: APIReference
    url: https://www.workstyleos.com/publicapi/index.html
  - type: Documentation
    url: https://support.workstyleos.com/faq/show/598?site_domain=default
common:
- url: https://www.acall.inc/news/
  type: Blog
- type: CapabilityMap
  url: capabilities/acall-capability-edges.yml
  name: Acall Business Capability Map
- type: AgenticAccess
  url: agentic-access/acall-agentic-access.yml
- type: DomainSecurity
  url: security/acall-domain-security.yml
- type: Authentication
  url: authentication/acall-authentication.yml
- type: Website
  url: https://www.acall.inc/
- type: Documentation
  url: https://support.workstyleos.com/faq/show/598?site_domain=default
- type: APIReference
  url: https://www.workstyleos.com/publicapi/index.html
- type: Support
  url: https://support.workstyleos.com/?site_domain=default
- type: Login
  url: https://portal.workstyleos.com/login
- type: Pricing
  url: https://www.workstyleos.com/pricing/
- type: TermsOfService
  url: https://www.workstyleos.com/terms_of_use/
- type: PrivacyPolicy
  url: https://www.acall.inc/privacypolicy
- type: StatusPage
  url: https://status.acall.inc/
- type: ChangeLog
  url: https://www.workstyleos.com/info/release/
- type: Blog
  url: https://workstylelab.acall.inc/
- type: GitHubOrganization
  url: https://github.com/acall-inc
- type: Compliance
  url: https://www.workstyleos.com/security/
- type: Conventions
  url: conventions/acall-conventions.yml
- type: ErrorCatalog
  url: errors/acall-problem-types.yml
- type: Lifecycle
  url: lifecycle/acall-lifecycle.yml
- type: Conformance
  url: conformance/acall-conformance.yml
- type: DataModel
  url: data-model/acall-data-model.yml
- type: Packages
  url: packages/acall-packages.yml
- type: Webhooks
  url: asyncapi/acall-webhooks.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/acall-llms.txt
- type: Overlay
  url: overlays/acall-public-api-overlay.yaml
- type: RateLimits
  url: rate-limits/acall-rate-limits.yml
- type: Plans
  url: plans/acall-plans-pricing.yml
- type: ChangeLog
  url: changelog/acall-changelog.yml
x-enrichment:
  date: '2026-09-06'
  status: enriched
  artifacts_added: 24
  pass: local-v3
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io

Acall API — frequently asked questions

Does Acall have an API?

Yes. APIs.io lists 6 APIs from Acall, including Acall Event API, Acall Facility API and Acall Gate API, and 3 more.

Is there an OpenAPI specification for the Acall API?

Yes. APIs.io indexes 6 OpenAPI specifications for Acall, each linked for download from this page.

How do I authenticate with the Acall API?

Acall uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Acall Authentication.

How much does the Acall API cost?

Acall publishes its prices; its 月額費用 plan is 会議室数に合わせてお見積り as of 2026-10-28. APIs.io lists 2 pricing plans for Acall, with each plan's price, limits and inclusions under Pricing on this page.

Is the Acall API ready for AI agents?

Acall has a Kin Score of 51.3 out of 100 (developing) and an Agent Readiness score of 28.6 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/acall"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/acall/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/acall/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

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