Account and Transaction API Specification - UK vs SEC EDGAR Data
If you need a Finance API that's easy to integrate, go with SEC EDGAR Data.
Account and Transaction API Specification - UK
## Functionality at a glance The NBG "UK OPB - Account and Transaction v3.1.5" API follows the [UK Open Banking Specification v3.1.5](https://openbankinguk.github.io/read-write-api-site3/v3...
SEC EDGAR Data
API to access annual reports of public US companies
Account and Transaction API Specification - UK
- Simple API key authentication
- HTTPS supported
- Currently flagged as inactive
SEC EDGAR Data
- No authentication required
- HTTPS supported
- CORS enabled for frontend use
- Currently flagged as inactive
| Feature | Account and Transaction API Specification - UK | SEC EDGAR Data |
|---|---|---|
| Authentication | apiKey | None |
| HTTPS | Yes | Yes |
| CORS | Unknown | Yes |
When to use which?
SEC EDGAR Data is the better choice for quick prototypes and hackathons since it requires no authentication. SEC EDGAR Data works directly from the browser with CORS enabled, making it better for frontend-only apps.