Editorial Policy

Editorial standards

Accuracy, independence, and useful uncertainty

TraderAPI.com publishes educational developer content about trading-related software interfaces. The editorial goal is to help readers ask better engineering questions, not to promote a platform or predict market outcomes.

Source hierarchy

Platform-specific facts should be checked against primary sources such as official documentation, terms, status notices, technical specifications, or direct written clarification. Third-party commentary can identify a question but should not replace current primary evidence for a material claim.

Unknowns and changing products

APIs, products, account requirements, eligibility, pricing, rate limits, and regional access can change. When evidence is incomplete, the site uses language such as “verify in official documentation” rather than filling the gap with an assumption.

Independence and commercial relationships

Company and platform names are used for identification, comparison, and commentary. A reference does not imply affiliation. Any material sponsorship or commercial relationship affecting a page should be disclosed near the relevant content.

AI-assisted production

Automation may assist outlining, editing, consistency checks, code generation, or metadata production. Editorial responsibility remains with TraderAPI.com. Automated output is not treated as a source, and platform-specific claims require evidence.

Corrections

Readers can send corrections to [email protected]. Include the page URL, statement, and supporting evidence. Material corrections should update the page’s modification date and preserve a clear, accurate result.

Financial content boundary

The site does not recommend securities, contracts, currencies, or strategies and does not promise performance. Examples are conceptual or educational unless explicitly identified otherwise.