G.I.S., Inc., doing business as VirtuWorks ("VirtuWorks", "we") Version: 2026-10 Effective date: October 22, 2026 Contact: help@camra.ai — 3850 Bird Road, Suite 103, Miami, FL 33146
These terms govern your use of the CamRA API: the REST API at https://app.camra.ai/api/v1, the
MCP server for AI assistants at https://app.camra.ai/mcp, the OAuth 2.1 authorization server that
lets applications act for a CamRA user, and the webhooks CamRA sends to receivers you register. They
apply in addition to the Terms of Service, the
Acceptable Use Policy and the Data Processing Addendum. Words defined in
the Terms of Service have the same meaning here. Where these terms and the Terms of Service conflict
on the subject of the API, these terms prevail.
You accept these terms before you create an integration token, approve an application through OAuth, or register an OAuth application for your organisation. CamRA asks for the acceptance at that point and records the version you accepted.
1. Who may use the API#
1.1 The API is part of the Service. You may use it only for an organisation that holds a CamRA account, as one of its Authorised Users, or as a developer acting for such an organisation.
1.2 Every request acts as a CamRA user. It can never see or do more than that user can in the web application, and it is narrowed further by the token or grant it carries (section 2). Anything done through a token or grant issued from your account is done under your account, as section 2.2 of the Terms of Service says.
2. Credentials, scopes and limits on access#
2.1 Kinds of credential.
- A personal API token, created on the API tokens page of your account. It acts as you, or as much of you as the scopes you chose allow, and lasts until it is revoked unless you set a last day.
- An integration token, for a system rather than a person. It is bound to one organisation, carries an explicit list of scopes and always has a last day, at most one year after it is created.
- The sign-in of the CamRA desktop and iOS apps, which carries a fixed set of scopes for viewing and ends after 90 days without use.
- An OAuth access token, issued to an application you approve (section 3).
Each account may hold up to 25 active API tokens; OAuth grants do not count towards that number.
2.2 Scopes. A scope names an area of the API and whether it reads or writes (for example
cameras:read or alerts:write). A request may do what the user's permissions allow, within the
scopes of its token or grant and within the organisation or site the token is restricted to. A scope
never grants anything the user lacks. Recorded and still imagery and their links need footage:read;
live video needs live, and an integration token or OAuth grant needs footage:read as well. A
request outside its scopes is refused.
2.3 Keep credentials secret. API tokens, OAuth client secrets, refresh tokens and webhook signing secrets are secrets. We show a token or a secret once, when it is created, and store only a hash of a token. Do not embed them in code others can read, in a web page, or in a public repository, and do not share a token with someone who should not have the account's access. Revoke a credential as soon as it may be exposed, when a device is lost, or when a person or system no longer needs it.
2.4 Revocation. You can revoke your tokens and the applications connected to your account from the API tokens page; an administrator of an organisation can see and revoke the tokens bound to it. A revocation takes effect on the next request. Deleting your account revokes all of your tokens and grants.
3. OAuth applications and AI assistants#
3.1 How an application connects. An application obtains access through the authorization code
flow with PKCE: you sign in to CamRA in your browser, choose the one organisation the application may
act for, and approve the scopes it asks for on the consent page. Write scopes, footage:read and
live are granted only when you tick them. An access token lasts one hour and a refresh token 30
days; each refresh returns a new refresh token, and presenting an old one again revokes the whole
grant.
3.2 Which applications. An application is known to CamRA either because an administrator of your organisation registered it for that organisation, or because it identifies itself by a client metadata document published at its own web address (as claude.ai and Claude Code do). There is no other way to register one. An administrator who registers an application keeps its client secret, if any, secret under section 2.3, and is responsible for the redirect addresses registered for it.
3.3 AI assistants and the MCP server. The MCP server lets an AI assistant use CamRA on your behalf with an integration token or an OAuth grant for that server. The assistant sees the results of the tools it calls, which can include personal information from your organisation's cameras, parking and people records, within the scopes you granted. Those results are sent to the assistant and to the company that operates it, and they are handled under that company's terms, not ours. Grant only the scopes the assistant needs, and connect only assistants your organisation is allowed to share that data with.
4. Webhooks#
4.1 An administrator of an organisation may register up to 25 webhook receivers for it. A receiver must be a public HTTPS address. CamRA signs each delivery with the subscription's secret (HMAC-SHA256) so that you can check it came from CamRA.
4.2 Deliveries are made at least once and in no guaranteed order; use the event's identifier to recognise a repeat. A delivery that does not succeed within 10 seconds is retried on a fixed schedule for about a day and a half, and a subscription whose deliveries have failed for 7 days without a success is disabled and its organisation's administrators are told. A subscription stops when its owner leaves the organisation or loses the permission to manage it. We keep a delivery log for 30 days and store nothing from your receiver's answer other than its status code.
4.3 What a webhook delivers is sent to the address you chose, on your instruction. Once it arrives, it is in your systems and your responsibility.
5. Rate limits and fair use#
5.1 Requests made with a token or an OAuth grant count against budgets per minute, per token or grant
and per organisation, separately for reads, writes, footage and the MCP server. The sign-in and OAuth
endpoints have their own limits per address. A request over a budget is refused with HTTP status 429
and a Retry-After header; wait at least that long before trying again.
5.2 The budgets are set by us, may differ between organisations, and may change. They protect the Service from abuse and are not a promised capacity. Do not try to get around them, for example by spreading one workload over many tokens or accounts.
5.3 We meter requests per token and per hour (the number of requests, errors and footage bytes), keep those records for 90 days, and show them to you on the API tokens page.
6. Acceptable use#
6.1 The Acceptable Use Policy applies to everything you do through the API, and in particular its rules on surveillance, automated analysis, sharing and system integrity.
6.2 You must not use the API to:
- reach data of an organisation you do not belong to, or probe the permission model;
- collect footage, plates or records of people to build a profile of an individual unrelated to the security or parking management of your own sites, or to sell or share them with a data broker;
- combine CamRA's output with a facial recognition service;
- interfere with the Service or with other customers' use of it; or
- build a product that competes with CamRA, or publish a benchmark of the API, without our written consent.
7. Data you receive through the API#
7.1 Your Customer Data stays yours. The API is one of the ways the Service makes it available to you.
7.2 When data leaves CamRA through the API, the MCP server or a webhook, it is in a system you or your Authorised Users chose. From then on you are responsible for it: for keeping it secure, for keeping it only as long as you need it, for honouring the requests of the people it is about, and for any notice or consent the law requires for what that system does with it. Our Data Processing Addendum covers our processing of Customer Data, not what a system you connect does with it.
7.3 A recording's video and images are handed out as short-lived links. Do not republish a link, or the file behind it, beyond the people who are entitled to see it.
7.4 Changes made through the API, and the opening, download and sharing of recordings through it, are recorded in your organisation's audit log as they are in the web application, with the token or application used.
8. Changes to the API#
8.1 Changes to /api/v1 are additive: new endpoints, new optional parameters and new members in a
response. Write your client to ignore members it does not know.
8.2 A change that would break a working client (removing or renaming something, changing a type or a
meaning, or making an optional input required) ships in a new version of the API next to /api/v1,
which keeps answering through a deprecation period announced with the change. Something to be removed
is marked deprecated first, names what replaces it and keeps working until the version that removes
it. While CamRA is in its closed beta, we may make such a change in place when we change our own apps
with it, and we say so in the changelog.
8.3 Changes are listed in the changelog of our developer documentation.
9. Changes to these terms#
We may update these terms. Each version carries a version stamp and an effective date. When the version changes, you are asked to accept the new one before you next create an integration token, approve an application or register one; tokens and grants you created before keep working.
10. Suspension and termination#
10.1 We may suspend or revoke a token, an OAuth grant, an application's registration or a webhook subscription, or limit your use of the API, if we reasonably believe it presents a security risk, breaches these terms or the Acceptable Use Policy, is unlawful, or harms the Service or other customers. Where practical we will tell you first and give you a chance to fix it. Section 9 of the Terms of Service applies as well.
10.2 Your access to the API ends when your account or your organisation's use of the Service ends. Every token and grant issued from your account then stops working.
11. Warranty and liability#
The API is part of the Service and is provided on the terms of sections 10 (warranties and disclaimers) and 11 (limitation of liability) of the Terms of Service. In particular, the API, its documentation and any sample code are provided "as is", we do not warrant that the API will be available without interruption, and we are not liable for what a system you connect does with data it received through the API.
12. General#
12.1 Governing law and venue. These terms are governed by the laws of the State of Florida, without regard to conflict of laws rules, and the state and federal courts located in Miami-Dade County, Florida have exclusive jurisdiction, as in section 14 of the Terms of Service.
12.2 Questions about these terms go to help@camra.ai.