API Terms of Use
TradingBase API Terms of Use
Document ID: LEG-009Version: 1.0Status: Draft for Legal ReviewEffective Date: [To be inserted]Last Updated: [To be inserted]
- Purpose
These API Terms of Use (“API Terms”) govern access to and use of the TradingBase Application Programming Interfaces (“APIs”), Software Development Kits (“SDKs”), Webhooks, developer tools, and related technical services provided by TradingBase.
These API Terms form part of the TradingBase Terms of Service.
- Scope
These API Terms apply to:
Public APIs;
Partner APIs;
Enterprise APIs;
Internal integration APIs where authorized;
Webhooks;
SDKs;
Developer Portals;
API documentation;
API Keys;
OAuth integrations.
- Eligibility
To access the APIs, you must:
maintain an active TradingBase account;
comply with applicable laws;
comply with these API Terms;
maintain appropriate security controls;
obtain any required API credentials.
TradingBase may impose additional requirements for Partner or Enterprise APIs.
- API Credentials
Access credentials may include:
API Keys;
OAuth tokens;
Client IDs;
Client Secrets;
JWT tokens;
other authentication mechanisms approved by TradingBase.
API credentials are confidential.
Developers must:
protect credentials from unauthorized disclosure;
rotate credentials where appropriate;
immediately report suspected compromise;
avoid embedding secrets in publicly accessible code repositories.
- Permitted Use
Developers may use the APIs only for lawful purposes consistent with:
official documentation;
published rate limits;
licensing terms;
applicable law;
Platform policies.
Use beyond the documented scope requires prior authorization.
- Prohibited Activities
Developers must not:
attempt unauthorized access;
bypass authentication mechanisms;
exceed published rate limits through abusive techniques;
reverse engineer restricted services;
interfere with Platform availability;
distribute malware;
exploit vulnerabilities;
scrape data in violation of Platform policies;
misuse user credentials.
- Rate Limits
TradingBase may establish:
request limits;
concurrency limits;
bandwidth limits;
quota allocations;
burst limits.
Limits may vary depending on:
subscription plan;
API type;
Partner status;
Enterprise agreement.
TradingBase may modify limits as operational requirements evolve.
- Availability
TradingBase aims to provide reliable API availability but does not guarantee uninterrupted service.
API availability may be affected by:
maintenance;
upgrades;
infrastructure failures;
third-party dependencies;
security incidents;
force majeure events.
No specific uptime commitment exists unless expressly provided in a separate Service Level Agreement (SLA).
- Versioning
TradingBase may release:
new API versions;
beta endpoints;
deprecated endpoints;
experimental features.
Developers are responsible for maintaining compatibility with supported API versions.
Reasonable notice will generally be provided before removal of stable endpoints where practicable.
- Security Requirements
Developers must implement reasonable security measures including:
secure credential storage;
encrypted communications using supported protocols;
input validation;
access controls;
logging where appropriate;
incident response procedures.
Failure to maintain adequate security may result in suspension of API access.
- User Data
Where APIs process Personal Data, Developers must:
comply with applicable privacy laws;
process data only for authorized purposes;
implement appropriate safeguards;
promptly report data breaches where legally required;
respect user rights under applicable law.
These obligations are in addition to the TradingBase Privacy Policy and any applicable Data Processing Agreement.
- Intellectual Property
TradingBase retains all intellectual property rights relating to:
APIs;
SDKs;
documentation;
sample code;
trademarks;
technical specifications.
Except as expressly permitted, no license is granted beyond the limited right to use the APIs in accordance with these API Terms.
- Monitoring
TradingBase may monitor API usage for purposes including:
security;
fraud prevention;
abuse detection;
performance optimization;
compliance verification;
operational analytics.
Monitoring is conducted in accordance with applicable law and the Privacy Policy.
- Suspension
TradingBase may temporarily suspend API access where necessary to:
investigate suspected abuse;
protect Platform security;
prevent service disruption;
comply with legal obligations;
respond to cybersecurity incidents.
Where appropriate, TradingBase may notify affected Developers.
- Termination
TradingBase may revoke API access where:
these API Terms are violated;
misuse is identified;
required credentials are compromised;
legal obligations require termination;
Platform security is endangered.
Termination does not affect obligations that survive by their nature.
- Beta Services
Certain APIs may be designated as beta, preview, experimental, or early access.
Such services:
may change without notice;
may contain defects;
may have limited documentation;
may be discontinued at any time.
Beta services are provided primarily for evaluation purposes.
- Limitation of Liability
To the fullest extent permitted by applicable law, TradingBase shall not be liable for losses arising from:
API downtime;
integration failures;
software defects;
third-party dependencies;
developer implementation errors;
unauthorized credential disclosure by Developers.
Nothing in these API Terms excludes liability that cannot lawfully be excluded.
- Changes to the APIs
TradingBase reserves the right to:
introduce new endpoints;
modify existing endpoints;
retire obsolete functionality;
improve security requirements;
adjust quotas;
update technical documentation.
Developers are responsible for monitoring official API announcements.
- Changes to these API Terms
TradingBase may revise these API Terms from time to time.
Updated versions become effective on the date specified in the revised document.
Continued use of the APIs constitutes acceptance of the updated API Terms.
- Contact
Questions regarding these API Terms should be directed through TradingBase’s official developer support channels.
Appendix A — Examples of API Services
Examples of API functionality may include:
authentication;
user profiles;
learning progress;
portfolio management;
market data access;
AI services;
notifications;
Marketplace integration;
payment events;
reporting;
analytics.
Availability depends on subscription level and technical implementation.
Appendix B — Security Best Practices
Developers are encouraged to:
rotate API Keys periodically;
store secrets securely;
enable multi-factor authentication where available;
validate all incoming data;
implement retry logic responsibly;
monitor abnormal API usage;
review access logs regularly.
These practices reduce operational and security risks.
Appendix C — Developer Responsibilities
Developers acknowledge responsibility for:
complying with applicable laws;
maintaining secure systems;
protecting API credentials;
ensuring compatibility with supported API versions;
respecting Platform policies;
avoiding abusive or excessive API usage.
Compliance with these responsibilities supports the stability and security of the TradingBase ecosystem.