Provider API Import

What this tab is for

Use Provider API Import to request historical data from a supported provider. The provider owns its products, symbols, availability, and commercial terms. Arizmic uses the confirmed request to publish a local Dataset and retain its source lineage.

1. Provider and credentials

Select an installed provider, then add its historical-data credential in System & Jobs → Data API Keys. Use a credential created for historical data access, not a brokerage login unless the provider explicitly uses the same credential for both.

The status beside the provider applies to that exact provider and acquisition mode. A connected credential does not guarantee access to every product, exchange, schema, or date range. If the provider requires a key, get it from that provider's account dashboard or developer portal. Use the provider's support and entitlement pages—not a copied key from another service—to resolve missing access.

2. Provider source selection

The choices in this stage are published by the selected provider. Depending on the provider, they can include a delivery method, dataset, feed, venue, provider schema, or other source-defining values. Pick the source that matches the market and record type you need.

• Data product chooses the canonical output you are requesting, such as bars, trades, quotes, or supported depth records. It also determines which provider endpoint and source choices are relevant.
• Provider source fields identify the provider's actual product and feed. They are not generic Arizmic labels, so their options change by provider.
• Context status reports whether the complete set of selected provider values is available, blocked, or otherwise limited.

Downstream choices reset when an earlier source choice changes. That is intentional: an Instrument or schema selected for one provider product may not exist in another. If you do not know what a provider field means, use the provider's product catalogue, schema documentation, or account-entitlement screen. Do not guess a value or type a provider identifier manually.

3. Provider instrument

Search the selected provider's credential-scoped inventory for the Instrument. The tab uses the provider's symbols and identifiers rather than asking you to re-enter them by hand. For a future, select the exact contract or the provider option that clearly states its roll construction; for an option, confirm the underlying, expiry, strike, and right when the provider exposes them.

If the expected Instrument is absent, first check the provider's entitlement, product coverage, symbol guide, and date range. A symbol that looks correct on another platform is not proof that this provider offers the same history.

4. Request window and bars

• Start is the first requested moment, entered in local time in the form.
• End (exclusive) is the first moment after the requested history. Use an exclusive end so adjacent imports do not unintentionally overlap.
• Bar type defines how a bar is constructed. For time bars, choose the Time unit and Multiplier; for trade-count, volume, or range bars, enter the number that defines one bar.

Only the bar types, units, and multipliers offered by the provider can be requested. The provider date-availability message is a boundary for the selected source and Instrument, not a promise that every record is complete or entitled.

5. Dataset target and source retention

• New Dataset creates a new local Dataset family. Its name is for Catalog; it does not alter the provider identity.
• New Version creates a candidate replacement for an existing Dataset family after you review it.
• Append Coverage adds compatible history to an existing active Dataset. It is not the right choice for a different instrument, schema, adjustment, or market identity.
• Keep Provider Source Bundle after import retains the delivered provider files locally. It is off by default; otherwise temporary provider files are removed after successful publication.

Arizmic chooses a stable local storage layout from the confirmed source. The provider's download batches do not define how the canonical Dataset is stored.

6. Resolved identity and recovery

Before estimating the request, Arizmic shows the server-resolved identity. Read this card as the meaning of the Dataset that would be created:

• Instrument, symbols, asset class, venue, and denomination identify the market and source naming.
• Price increment, quantity increment, lot size, multiplier, and tick value define valid prices, quantities, and contract economics.
• Alignment, session, timezone, and calendar define the timing and market schedule used when the data is prepared and studied.
• Activation, expiry, strike, option right, underlying, margin model, and adjustment policy appear when they apply to the selected product.
• Provider provenance records the provider dataset, schema, feed, source ID, and provider record date when supplied.

Provider-resolved values are authoritative and cannot be overridden. If the provider leaves an essential fact unresolved, Advanced recovery appears after validation. Supply only the listed missing fields, then apply them as one set for validation. Use the provider's instrument master, exchange contract specification, official calendar, or provider support to find the value. Do not fill a provider-controlled identity field from a similar instrument or from an unverified web page.

Estimate, queue, and review

Review entitlement, provider terms, estimated cost, transfer size, and storage before confirming. An estimate helps you decide on one request; it is not a price lock or a reservation of inventory. Queue the request only when the selected context and resolved identity are ready.

When it finishes, open the candidate in Catalog. Check the Instrument, coverage, source lineage, and reported issues before activating it. A failed or canceled request never becomes a usable Dataset.