Developer API platform guide

Economic data is available without a key. Other developer APIs share an account credential while retaining separate quotas and data contracts.
Account and credential

Public requests need no key; protect account keys

For keyless public APIs such as economic history, make requests directly without signing in. For authenticated products, generate a key in Developer settings and keep it server-side, away from browser code, mobile bundles, public repositories and logs.

Authenticate
Use no credentials for keyless endpoints; send Bearer credentials only to APIs that require them.
Authorize
Public data stays public. Authenticated products decide independently which account capabilities are available.
Rotate
For authenticated products, rotate the credential from Developer settings and update your callers.
Requests and compatibility

Build against the product's versioned API and OpenAPI contract

Start from the versioned base path shown for the product, use its quick start for working requests, use the generated reference for endpoint details, and use its OpenAPI document as the machine-readable definition. Do not assume that fields, quotas, or capabilities from one product apply to another.

Resilient clients

Treat product limits and failures deliberately

There is no single numeric quota across every Grizzly Bulls API. Keyless routes and authenticated products have different access policies. Check each product's documentation.

Transient failures
Use bounded retries with backoff for temporary transport or server failures rather than tight retry loops.
Access failures
Do not repeatedly retry authentication or product-access failures. Check the credential and the product's access requirements first.
Usage limits
Read the selected product's documentation for its quota and plan details instead of assuming a platform-wide number.
Data provenance and freshness

Keep product data semantics with the data

Provenance, observation time, retention, and freshness differ by dataset. Preserve the metadata returned by the API and use the product documentation when your application depends on point-in-time meaning, source attribution, or update cadence.