Oosto OnAccess API

Per-deployment REST API for Oosto OnAccess, the facial access-control product (internal codename "Abraxas"), served from the customer's own OnAccess server under the /abx/api base path. Authentication is username/password exchanged for a bearer JWT at POST /abx/api/login. The enrolment flow published in the vendor's sample code posts an image as multipart/form-data to POST /abx/api/external-functions/extract-faces-from-image to extract face feature vectors, then creates the person record with POST /abx/api/members, carrying the extracted image features plus identity fields (name, email, phone, description), access-card credentials (card id + facility code) and member-group membership by UUID. As with OnWatch there is no vendor-hosted base URL — the API ships with the customer's installation. Reference documentation is behind an OTP login at knowledge.oosto.com; operations recorded here come from the vendor's public sample code.

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/oosto-onaccess-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

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

API entry from apis.yml

apis.yml Raw ↑
name: Oosto OnAccess API
description: Per-deployment REST API for Oosto OnAccess, the facial access-control product (internal codename
  "Abraxas"), served from the customer's own OnAccess server under the /abx/api base path. Authentication
  is username/password exchanged for a bearer JWT at POST /abx/api/login. The enrolment flow published
  in the vendor's sample code posts an image as multipart/form-data to POST /abx/api/external-functions/extract-faces-from-image
  to extract face feature vectors, then creates the person record with POST /abx/api/members, carrying
  the extracted image features plus identity fields (name, email, phone, description), access-card credentials
  (card id + facility code) and member-group membership by UUID. As with OnWatch there is no vendor-hosted
  base URL — the API ships with the customer's installation. Reference documentation is behind an OTP
  login at knowledge.oosto.com; operations recorded here come from the vendor's public sample code.
humanURL: https://github.com/AnyVisionltd/oosto-api-sample-code/tree/master/OnAccess
tags:
- Facial Recognition
- Access Control
- Biometrics
- Visitor Management
- Physical Security
tags_raw:
- facial-recognition
- access-control
- biometrics
- visitor-management
- physical-security
properties:
- type: SourceCode
  url: https://github.com/AnyVisionltd/oosto-api-sample-code
- type: Documentation
  url: https://knowledge.oosto.com/docs
- type: Authentication
  url: authentication/anyvision-authentication.yml
- type: Conventions
  url: conventions/anyvision-conventions.yml