<aside> 🔐
API Keys let your own systems send transactions to HOST (and read them back) through the HOST Transactions API instead of uploading files. There are two environments: Development keys for building and testing, and Production keys for live data. Production keys require a one-time data review by HOST.
</aside>
Sidebar → Help & Tools → API Keys — managers only; the entry is hidden from everyone else, and the page itself says "API keys can only be viewed and created by organization managers." It opens on the Development tab (/api-keys/dev); Production is /api-keys/prod. API reference: the API overview link in the page header opens the HOST Transactions API Overview, and the View Docs link on an issued key opens that environment's own endpoint reference.
| Aspect | Development | Production |
|---|---|---|
| Data | Test data only — never touches live filings | Your real transaction data |
| Availability | Immediately | After HOST approves a data review |
| Handling | Safe to share with engineers and keep in staging configs | Treat like a password; never commit to source control; rotate if exposed |
The two environments are entirely separate services — a key from one is unknown to the other.

The Development tab: the create form (name and scopes) and the Issued Development Keys table.
write:transaction) and/or Read transaction (read:transaction).
The Production tab before approval: the Data review required card replaces the create form.
Before issuing production keys, HOST reviews your transaction data to confirm it's ready to file against. This happens once per organization.