Can an Arkvos partner integrate multiple client companies?

Yes, but each unrelated client company must have its own Arkvos customer organization, active subscription and separately authorized API credential unless Arkvos has approved a different enterprise agreement in writing.

Does Arkvos provide one master API key for every client?

No. Client operational data is tenant-scoped. One customer API key cannot access another Arkvos customer organization.

Can one construction company use Arkvos across many jobsites?

Yes. A subscribed customer organization may use Arkvos across its own branches, jobsites and controlled operating locations. The restriction is against pooling unrelated third-party customer companies into one subscription.

Partner architecture

Integrate Arkvos across your client base—without mixing customer accounts.

Safety consultants, staffing firms, brokers and software partners can bring Arkvos to multiple customers. Each customer remains a separately secured and subscribed Arkvos organization.

The customer-isolated model

Partner / integration

Your consulting practice, staffing platform, EHS product or workflow.

→

Customer A · its own Arkvos tenant

Its own subscription, sites, workers and API credentials.

Same partner

You may refer, configure or integrate another customer.

→

Customer B · separate Arkvos tenant

Separate subscription, authorization and organization-scoped key.

Allowed: one company, many locations

A contractor may operate many branches, projects or jobsites inside its own Arkvos organization. Multi-site operations are a core Arkvos use case.

Not allowed: one subscription, many unrelated client companies

A consultant, reseller or software provider may not label unrelated customer businesses as branches or sites in order to serve those customers through one paid Arkvos subscription.

Why Arkvos does not issue a master customer-data key

A universal reseller key would weaken tenant isolation and make it too easy for an accidental or malicious integration to cross customer boundaries. Instead, the API key itself resolves to one Arkvos organization and API queries remain constrained to that organization. When the customer's paid subscription becomes inactive, its active API credentials are revoked.

What partners can build

Safety consultant dashboards that deep-link or synchronize separately authorized client accounts.
Staffing reconciliation workflows that connect a worker-placement system to each participating contractor.
Reporting exports and BI pipelines for individual customers.
Project-management integrations that create briefings and retrieve verification records.
Referral and implementation services while Arkvos remains the system of record for each customer's briefing verification.

Customer API access

Customer A → ARKVOS_API_KEY_A → Customer A data only Customer B → ARKVOS_API_KEY_B → Customer B data only Customer C → ARKVOS_API_KEY_C → Customer C data only No master key → all customer operational data

API safeguards

Arkvos API v1 uses organization-scoped, revocable API keys. Credentials are available to active paid customer organizations, support Bearer or X-API-Key authentication and are rate-limited at 600 requests per minute per key. Public API v1 does not expose QR secrets, worker selfie image blobs or billing credentials.

Become an Arkvos partner

The Partner Program is built for organizations that already advise or serve employers. Refer each client into its own Arkvos account and keep the customer relationship clean instead of building a shadow multi-tenant copy of Arkvos.

View the Partner Program · Partner Agreement · Developer docs · Workforce Safety API