Aircraft Intelligence API
FAA registry data and observed change history
api.grizzlybulls.com/v1/aircraftDeveloper API platform guide
Use one account credential across Grizzly Bulls developer APIs while following each product's own endpoint, access, quota, and data rules.
Account and credential
Create one key and keep it private
Generate your API key from Developer settings. Store it on the server side rather than in browser code, mobile bundles, public repositories, or logs.
- Authenticate
- Send the account key as a Bearer credential in the Authorization header.
- Authorize
- Authentication identifies your account. Each product separately decides whether the requested capability is available to that account.
- Rotate
- Manage the account credential from Developer settings and update callers that depend on it when the key changes.
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.
Wealth Intelligence API
People, ownership, and financial-event history
grizzlybulls.com/api/v1/wealthSEC Data API
Filings, financials, ownership, and Form 13F data
grizzlybulls.com/api/v1/secResilient clients
Treat product limits and failures deliberately
There is no single numeric quota to apply across every Grizzly Bulls API. Use the product documentation for its current access and usage rules.
- 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.