API Access

Overview

VisioArt can expose API-based workflows for automation, internal tooling, or production integrations. However, API access is deployment-dependent. Some environments expose self-service API keys in the dashboard, while others keep API access disabled or provision it manually.

Finding Your API Keys

If API access is enabled for your account, go to Settings → API Keys in the VisioArt dashboard. That page lists active keys, creation timestamps, and any metadata the deployment chooses to show.

If the API Keys tab is missing, self-service API access is not currently enabled for your deployment or account tier.

Generating a New Key

When the feature is enabled:

• Click Create API Key
• Add a descriptive label such as CI Pipeline or Mobile Backend
• Copy the key immediately, because the full secret is typically shown only once
• Store it in a secure environment variable or secrets manager

Revoking Keys

Revoking a key takes effect immediately. Any future requests signed with that key will be rejected. Rotate keys promptly if you suspect accidental exposure.

Permissions

The exact permission model depends on the deployment. Some environments expose simple read/write scopes, while others restrict keys to specific actions or internal workflows. Use the narrowest scope available for each integration.

Rate Limits and Concurrency

Rate limits and concurrent job limits are not universal across all VisioArt deployments. Treat them as environment-specific. Your client should:

• Respect 429 Too Many Requests responses
• Implement retry with backoff
• Avoid assuming the same concurrency allowance across accounts or workspaces

When the API Is Not Available

If your workspace does not expose self-service API keys, use the web dashboard workflows instead, or coordinate with the deployment owner if programmatic access is required.