Oosto OnWatch API

Per-deployment REST API and Socket.IO event stream for Oosto OnWatch, the real-time watchlist alerting and person-of-interest monitoring product. Served from the customer's own OnWatch server under the /bt/api base path (the product's internal codename is "Better Tomorrow"). Authentication is username/password exchanged for a bearer JWT at POST /bt/api/login, with an end-user licence acknowledgement step at POST /bt/api/eula. Administrative resources such as roles are read over REST with offset/limit/sortOrder paging, and detection events are consumed by connecting a Socket.IO client to the /bt/api/socket.io path with the token supplied as a query parameter, receiving track:created events as subjects are matched. There is no vendor-hosted multi-tenant base URL — every deployment resolves to the customer's own server IP or DNS name, so no public baseURL is recorded here. The reference documentation is behind an OTP login at knowledge.oosto.com; the operations recorded in this profile are taken from the vendor's own public sample code on GitHub.

API entry from apis.yml

apis.yml Raw ↑
name: Oosto OnWatch API
description: Per-deployment REST API and Socket.IO event stream for Oosto OnWatch, the real-time watchlist
  alerting and person-of-interest monitoring product. Served from the customer's own OnWatch server under
  the /bt/api base path (the product's internal codename is "Better Tomorrow"). Authentication is username/password
  exchanged for a bearer JWT at POST /bt/api/login, with an end-user licence acknowledgement step at POST
  /bt/api/eula. Administrative resources such as roles are read over REST with offset/limit/sortOrder
  paging, and detection events are consumed by connecting a Socket.IO client to the /bt/api/socket.io
  path with the token supplied as a query parameter, receiving track:created events as subjects are matched.
  There is no vendor-hosted multi-tenant base URL — every deployment resolves to the customer's own server
  IP or DNS name, so no public baseURL is recorded here. The reference documentation is behind an OTP
  login at knowledge.oosto.com; the operations recorded in this profile are taken from the vendor's own
  public sample code on GitHub.
humanURL: https://github.com/AnyVisionltd/oosto-api-sample-code/tree/master/OnWatch
tags:
- facial-recognition
- video-analytics
- watchlist-alerting
- physical-security
- real-time-events
properties:
- type: SourceCode
  url: https://github.com/AnyVisionltd/oosto-api-sample-code
- type: Documentation
  url: https://knowledge.oosto.com/docs
- type: Webhooks
  url: asyncapi/anyvision-onwatch-events.yml
- type: Authentication
  url: authentication/anyvision-authentication.yml
- type: Conventions
  url: conventions/anyvision-conventions.yml