Documentation
Contents
By Arizmic LLC2 min readPublished Last reviewed

System & Jobs

Data API Keys

Store protected historical-data credentials, read field-level status, manage provider plugins, and troubleshoot authentication without exposing secrets.

App path

  • System & Jobs -> Data API Keys
  • Data Manager -> API Import

What Data API Keys is for

Data API Keys stores credentials used by supported historical-data import plugins. It is separate from Broker Connections and AI Models because each credential domain grants different access and follows a different workflow.

The provider list reflects the plugins currently available to the workstation. The presence of a provider or stored key does not by itself confirm an account's subscription, dataset entitlement, symbol access, or import readiness.

Store a provider credential

  1. Select the exact data provider.
  2. Complete every credential field shown for that provider.
  3. Choose Store Keys.
  4. Confirm the field status and masked reference in the table.
  5. Return to Data Manager -> API Import and verify the provider request before ordering data.

The form is defined by the provider plugin. A field named API key, secret, client ID, or account token is not interchangeable with another field.

Obtain credential values from the provider's own account dashboard or developer portal. Dataset names, schemas, exchanges, entitlements, and symbols normally come from the provider's documentation or account configuration rather than from the credential itself.

Arizmic stores the secret through the operating system's protected secret store. After saving, the table shows configuration state and a reference—not the reusable secret.

Replace or remove credentials

Paste a new value into a configured field to replace it. Rotate credentials when the provider revokes them, their scope changes, or a team access policy requires it. After rotation, run a small API Import request before starting a large order.

Removing a provider's key deletes all stored Data API credential fields for that provider from the operating system secret store. Existing local Datasets and Results remain, but new provider requests can no longer authenticate until credentials are restored.

Understand Provider Plugins

The Provider Plugins table shows the discovered historical-data adapters, their origin, version, state, and diagnostics. A built-in plugin ships with Arizmic; an operator plugin was installed locally. In either case, the plugin still needs compatible credentials and a supported request.

Use Sync Provider Plugins after installing or updating a provider plugin. The sync is blocked while provider-import Jobs are queued, running, or paused so that an active request cannot change adapters underneath itself. Finish or cancel those Jobs, then sync again.

Troubleshoot an import credential

If an API Import cannot authenticate:

  • confirm the provider selected in Data Manager matches the stored key;
  • check every required credential field, not only the first one;
  • confirm the provider account and requested dataset are entitled;
  • look for plugin diagnostics and version mismatch;
  • rotate the credential if the provider reports it expired or revoked; and
  • inspect the failed Job without including the secret in notes or support mail.

Historical-data support does not imply Live brokerage support. Configure a supported trading provider separately in Broker Connections.