Skip to Content
FlowVerifyDevelopers

Versioning, access and support

How the API evolves, what stays stable, how to get access, and where to ask for help.

Versioning

The version is in the path: https://api.flowverify.co/v1. Inside a version, changes are additive only:

  • New endpoints, new optional request fields, new response fields and new webhook event types may appear at any time. Parse responses and events tolerantly and ignore what you do not know.
  • Existing fields keep their names, types and meaning; enum values are never removed; error codes are never renamed.
  • Anything that would break the above ships as a new version (/v2) alongside /v1.

Every developer-visible change is listed in the changelog. Webhook payloads carry api_version so you can tell which schema produced them.

Deprecation

When an endpoint or field is scheduled for removal it is marked deprecated in the changelog and in the API reference, and responses carry Deprecation and Sunset headers with the retirement date well in advance. Deprecated features keep working until the sunset date.

Getting access

The API and webhooks are available on the Enterprise plan. Workspace admins can request access from Settings → Integrations in the dashboard; keys and webhooks are managed under Settings → Developers. There is no separate developer login — the people who administer your FlowVerify workspace administer its API access.

A dedicated test mode with fv_test_ keys that never emails anyone is planned; until then, develop against a separate sandbox workspace.

Support

  • Email [email protected]. Include the request_id (from the X-Request-Id header or the JSON body) of any failing call, the endpoint, and the time in UTC.
  • For webhook problems include the webhook id and a delivery id from the delivery log.
  • Product questions, pricing and enterprise agreements: flowverify.co/contact.

Operational limits at a glance

LimitValue
Standard rate limit120 requests per minute per key (configurable lower per key)
Expensive routes (send, remind, bulk send, uploads, send-from-template, webhook test/rotate/replay)30 requests per minute per key
JSON body1 MB (36 MB on the file-upload route for base64 payloads)
File upload25 MB per file
Recipients per envelope100
Fields per request500
Recipients per bulk send5,000 per request, subject to the plan's cap
Webhooks per workspace20
Webhook delivery log30 days
Idempotency keysremembered for 24 hours
List page sizeup to 100

Plan-specific quotas (envelopes per month, SMS/Aadhaar allowances) are visible in GET /me under usage.

On this page