Register once. Recognised everywhere you're invited.

Organization → Project → Scope

Access splits three ways: the organization is the tenant, the project is the deployment, and the scope is the place people actually walk through. Each installation authenticates with a capture key — the bearer credential bound to that scope.

Organization

The tenant boundary — members and billing.

Project

One deployment, holding its scopes and capture keys.

Scope

A desk, an entrance, a floor — the place itself.

Static keys for devices, short-lived sessions for browsers

Installed devices POST /capture with a static bearer key. Browser ingest goes through a capture session minted per use, so no long-lived credential is ever left on the client.

One REST surface

The reference lives at api.meeeetup.com/docs. These are the endpoints that matter.

• POST/v1/persons/resolveIdentify a person from a face
• POST/v1/scopesCreate a scope
• PATCH/v1/scopes/{scopeId}Update a scope
• POST/v1/scopes/{scopeId}/profilesEnrol into a scope
• POST/v1/capture-sessionsIssue a short-lived capture session
• GET/v1/journalAudit recognition events

Using an AI coding assistant? Hand it api.meeeetup.com/v1/llms.txt — a plain-text integration guide covering auth, the data hierarchy and every endpoint, generated from the OpenAPI spec. No API key required to read it.

Web and React Native

Both packages are public on npm — no access token, no registry config. The Flutter package was dropped in cameraSDK v0.3.0 and is not offered.

Web

npm i @meeeetup/camera-web react react-dom

React Native

npm i @meeeetup/camera-react-native

Capture is all the SDK does: it hands you the selected face images through a callback and never talks to a backend, so the upload stays your code. Package details on npmjs.com.