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

Acall Public API

REST API (v1) for the Acall / WorkstyleOS workplace platform. Thirteen operations across six resource families — workers (users), facilities, events, gate access logs, spots, and spot reservations — with spot reservations being the only writable surface (create, update, delete). Authentication is an HTTP bearer access token issued by Acall on request; the API is in beta and is not available on the multi-tenant plan.

This API exposes 13 operations across 10 paths, organized into 6 resource areas, and defines 24 schemas. It is described by OpenAPI 3.0.0, at version v1.

Requests are made against a single base URL, https://api.workstyleos.com/v1/.

13 operations 10 paths 24 schemas 1 DELETE10 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
v1
Base URL
https://api.workstyleos.com/v1/
Authentication
HTTP Bearer
Resource Areas
6

Authentication & Security 1

Acall Public API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (Bearer). By default, every request must be authenticated.

  • Bearer — Access token for API

Paths & Operations 13

Across 10 paths, the API surfaces 13 operations — 1 DELETE, 10 GET, 1 PATCH, 1 POST. They span 6 resource areas: User API, Facility API, Event API, Gate API, Spot API, Spot Reservation API. Each is listed below with its method, path, parameters, and response codes.

User API 2
GET
/users
ユーザー 一覧取得
getUsers 3 params → 200
GET
/users/{user_id}
ユーザー 詳細取得
getUser 1 param → 200
Facility API 2
GET
/facilities
設備 一覧取得
getFacilities 3 params → 200
GET
/facilities/{facility_id}
設備 詳細取得
getFacility 1 param → 200
Event API 2
GET
/events
イベント 一覧取得
getEvents 5 params → 200
GET
/events/{event_id}
イベント 詳細取得
getEvent 1 param → 200
Gate API 1
GET
/gates/logs
ゲートアクセスログ 一覧取得
getGateLogs 5 params → 200
Spot API 1
GET
/spots
スポット 一覧取得
getSpots 3 params → 200
Spot Reservation API 5
GET
/spot_reservations/
スポット予約 一覧取得
getSpotReservations 5 params → 200
POST
/spot_reservations/
スポット予約 新規作成
postSpotReservation body → 201
DELETE
/spot_reservations/{spot_reservation_id}
スポット予約 削除 (複数スポットに紐づく予約データは削除不可)
deleteSpotReservation 1 param body → 204
GET
/spot_reservations/{spot_reservation_id}
スポット予約 詳細取得
getSpotReservation 1 param → 200
PATCH
/spot_reservations/{spot_reservation_id}
スポット予約 更新
putSpotReservation 1 param body → 200

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are Event (11 properties), EventDetail (11 properties), UserDetail (9 properties), User (9 properties). Each schema is shown below with its type and property counts.

User
object
9 properties
UserBelongGroup
object
2 properties
UserDetail
object
9 properties
UserDetailBelongGroup
object
2 properties
Facility
object
6 properties
FacilityDetail
object
6 properties
Event
object
11 properties
EventGuest
object
7 properties
EventAttendUser
object
4 properties
EventFacility
object
3 properties
EventDetail
object
11 properties
EventDetailGuest
object
7 properties
EventDetailAttendUser
object
4 properties
EventDetailFacility
object
3 properties
GateLog
object
6 properties
GateOperator
object
2 properties
GatePasser
object
5 properties
Spot
object
3 properties
SpotReservation
object
7 properties
InvitedUser
object
1 property
SpotReservationDetail
object
7 properties
inline_object
object
7 properties
inline_object_1
object
1 property
inline_object_2
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

acall-public-api-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of Acall Public 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.