API Terms

1. There is no public customer API today

VERA does not currently issue API keys or personal access tokens to customers, and does not publish a documented REST or GraphQL API for programmatic access to your account. Anyone offering you a "VERA API key" is not acting on our behalf; report it to support@myvera.io.

The HTTP endpoints VERA operates are internal to the application: authentication, OAuth connect and callback routes for integrations, inbound webhook receivers, asset delivery for signed-in users, and a health check. They are not a supported integration surface, are authenticated as part of a browser session or by a provider signature, and may change without notice. Building against them is not permitted under the Terms of Service.

2. Inbound webhooks

VERA receives webhooks from platforms you connect, such as Stripe, Meta, Jobber, QuickBooks, Square, and Shopify. These are configured by VERA as the platform's developer, not by you, and are verified against each provider's signing scheme before they are processed. Deliveries are deduplicated by event id so a replayed event cannot double-apply.

VERA does not currently send outbound webhooks to endpoints you specify.

3. Terms that will apply to a future API

If and when VERA releases a public API, the following will apply in addition to the Terms of Service, and using the API will constitute acceptance of them.

• Credentials. API credentials identify your account, are confidential, and must not be shared, embedded in client-side code, or committed to a repository. You are responsible for everything done with them.
• Rate limits and metering. API calls will be subject to rate limits and, where they invoke AI, to the same credit metering as the application. Circumventing either is prohibited.
• Scope of use. The API will be licensed for use with your own account's data, and for an agency, with the accounts of clients you operate under your subscription. It will not be licensed for building a competing product or for bulk extraction of VERA-generated content.
• Stability. Endpoints will be versioned. Breaking changes will be announced with notice; beta endpoints will be labelled and excluded from that commitment.
• Data protection. The Privacy Policy and Data Processing Addendum will apply unchanged to data accessed through the API.

4. Contact

Interested in programmatic access, or building an integration with VERA? Write to partnerships@myvera.io and tell us what you are trying to build.