API Terms

1. Agreement and Order of Precedence

Your API relationship with WallStreetHack.com may include:

• these API Terms;
• the applicable API plan or order summary;
• the Terms and Conditions;
• the Acceptable Use Policy;
• the Subscription Agreement;
• the Privacy Policy;
• the API documentation and technical specifications;
• any separately signed enterprise or data-licensing agreement.

If a separately signed written agreement expressly conflicts with these API Terms, the separately signed agreement controls for the relevant API access.

2. Definitions

For these API Terms:

• API means the application programming interfaces, endpoints and technical services supplied by WallStreetHack.com.
• API Data means data, records, fields, status updates and responses delivered through the API.
• API Credential means an API key, token, secret or other authentication value.
• Application means software, a website, service, bot, dashboard or internal system using the API.
• Developer means the individual or organisation responsible for an Application.
• Webhook means an event notification sent to a destination configured by the Developer.
• Documentation means the technical materials available at API Documentation.

3. Eligibility and Authority

You may use the API only if you have the legal capacity to enter into this agreement and the technical ability to operate the integration securely.

If you use the API for an organisation, you represent that:

• you are authorised to bind that organisation;
• the organisation accepts these API Terms;
• the API use is within the organisation’s lawful activities;
• all authorised users will follow these API Terms;
• the organisation is responsible for its Applications and credentials.

API access may be unavailable in a jurisdiction where the relevant use, data or service is prohibited.

4. API Access and Approval

API access may require:

• an approved subscription or API plan;
• accurate contact and organisation information;
• a description of the intended integration;
• acceptance of applicable usage restrictions;
• successful payment where the API plan is paid;
• completion of reasonable security or compliance checks.

WallStreetHack.com may approve, reject or condition an API access request based on technical capacity, security, intended use, legal requirements and plan availability.

Approval for one Application, environment, organisation or use case does not automatically authorise another.

5. API Credentials

API Credentials are confidential and remain associated with the approved subscriber or organisation.

You must:

• store credentials using appropriate secret-management controls;
• limit access to authorised personnel and systems;
• avoid placing secrets in public repositories;
• avoid exposing secrets in browser-side source code;
• rotate credentials after suspected compromise;
• revoke credentials that are no longer required;
• maintain separate credentials where environments require separation.

You must not:

• publish or publicly disclose a credential;
• sell, rent or transfer a credential;
• use credentials issued to another subscriber;
• share a personal API plan with unrelated users;
• send a complete credential through a support form;
• attempt to recover, guess or obtain another user’s key.

6. Permitted API Use

Subject to the applicable plan, the API may be used to:

• display authorised Signal information internally;
• receive Signal status and lifecycle updates;
• receive authorised whale-activity or market-data alerts;
• build internal research and monitoring tools;
• connect authorised notification systems;
• store limited API Data required for approved functionality;
• perform internal analysis consistent with the subscribed plan;
• support another expressly approved integration purpose.

Use must remain within the endpoint scope, user count, request allowance, storage permission and commercial rights included in the relevant API plan.

7. Documentation and Technical Requirements

You must use the API according to the current API Documentation.

Your Application must correctly handle:

• authentication requirements;
• supported request methods and parameters;
• response schemas and data types;
• timestamps and timezone information;
• decimal precision and asset identifiers;
• pagination and cursor behaviour;
• rate-limit headers and responses;
• errors, retries and temporary failures;
• version changes and deprecation notices.

Examples in the Documentation may be illustrative and must be tested before production use.

8. Rate Limits and Technical Limits

WallStreetHack.com may apply request, concurrency, storage, webhook, user, environment and endpoint limits.

Limits may vary according to:

• API plan or subscription tier;
• endpoint type;
• system capacity;
• security risk;
• usage history;
• temporary service conditions.

You must respect 429 responses, rate-limit headers, retry instructions and other technical controls.

You must not circumvent limits by:

• creating multiple unauthorised accounts;
• rotating credentials, IP addresses or identifiers;
• splitting one Application across deceptive environments;
• using scraping as a substitute for authorised API capacity;
• concealing the source or volume of requests.

9. Limited API Data Licence

Subject to payment, compliance and the applicable plan, WallStreetHack.com grants you a limited, revocable, non-exclusive and non-transferable right to access and use API Data for the approved purpose.

This licence does not transfer ownership of:

• the API;
• the underlying database;
• Signal methodology;
• market-intelligence models;
• documentation;
• software or source code;
• trademarks or branding;
• other intellectual property.

Rights not expressly granted are reserved by WallStreetHack.com and its licensors.

10. Prohibited API Uses

You must not use the API to:

• violate applicable law or regulatory requirements;
• facilitate fraud, money laundering or sanctions evasion;
• coordinate market manipulation or deceptive trading;
• misrepresent API Data as guaranteed investment advice;
• reverse engineer protected systems or methodology;
• probe undocumented endpoints without permission;
• interfere with API availability or security;
• transmit malware or harmful payloads;
• access another subscriber’s data or credentials;
• create a misleading copy of WallStreetHack.com;
• perform unauthorised surveillance or profiling;
• violate the Acceptable Use Policy.

11. Redistribution, Resale and Derived Services

A standard API subscription does not authorise unrestricted redistribution or commercial resale.

Without prior written permission, you must not:

• resell raw API responses;
• operate a public clone of the Signal feed;
• republish private Signal records in public channels;
• provide API Data to unrelated third parties;
• create an unauthorised white-label service;
• sell database access built substantially from API Data;
• remove risk, status or source information;
• use one subscription to serve unauthorised customers.

A derived analytical output may require a separate data licence where it enables users to reconstruct, substitute for or commercially exploit the original API Data.

12. Attribution and Representation

Where the applicable plan or documentation requires attribution, you must display it in a clear and accurate form.

You must not:

• imply that WallStreetHack.com endorses your Application;
• describe your Application as an official product without permission;
• alter attribution in a misleading manner;
• use WallStreetHack.com trademarks beyond the authorised scope;
• present modified API Data as an unchanged official response.

Any approved attribution must not imply a guarantee, partnership, agency or advisory relationship.

13. Developer Responsibilities

You are solely responsible for your Application and its interaction with the API.

You must:

• design and test the Application responsibly;
• validate responses before processing them;
• maintain accurate asset and market mappings;
• handle null, delayed and incomplete fields safely;
• implement appropriate logging and monitoring;
• prevent duplicate event processing;
• maintain backup and recovery procedures;
• protect users from misleading displays;
• comply with applicable consumer and privacy laws;
• maintain appropriate technical documentation.

You are responsible for all activity performed through credentials issued to you, except to the extent the activity results solely from a security failure controlled by WallStreetHack.com.

14. Security Requirements

You must use reasonable technical and organisational security controls appropriate to the Application and data.

Controls should include, where relevant:

• encrypted network communication;
• secure credential storage;
• least-privilege access;
• credential rotation and revocation;
• environment separation;
• input and response validation;
• security logging and alerting;
• dependency and vulnerability management;
• incident-response procedures;
• secure deletion of unnecessary API Data.

You must notify WallStreetHack.com promptly after discovering:

• credential exposure;
• unauthorised API access;
• a vulnerability affecting the integration;
• unlawful disclosure of API Data;
• a material incident involving WallStreetHack.com systems.

15. Personal Data and Privacy

You must not send personal data to the API unless the Documentation and your applicable agreement expressly allow it.

In particular, do not place unnecessary personal data in:

• query parameters;
• request identifiers;
• webhook URLs;
• custom headers;
• logs submitted to support;
• unstructured metadata fields.

If your Application processes personal data, you are responsible for:

• establishing an appropriate lawful basis;
• providing required privacy notices;
• collecting only necessary data;
• applying suitable retention periods;
• protecting data from unauthorised access;
• responding to applicable privacy rights;
• using appropriate processor or controller agreements.

WallStreetHack.com processing is described in the Privacy Policy.

16. Webhook Services

Webhooks may deliver event data to a destination configured by the Developer.

You are responsible for:

• providing a secure and valid webhook destination;
• using HTTPS where supported or required;
• verifying signatures or authentication values;
• protecting webhook secrets;
• returning supported response codes;
• handling duplicate and delayed deliveries;
• processing events idempotently;
• monitoring failed deliveries;
• removing destinations that are no longer used.

A webhook may be delayed, retried, delivered more than once, delivered out of order or not delivered.

17. Automated Trading and Financial Systems

An Application that uses API Data in trading or financial automation must implement independent controls, including:

• maximum order and position limits;
• market and asset allowlists;
• price and liquidity validation;
• duplicate-event protection;
• stale-data detection;
• status and invalidation checks;
• error and timeout handling;
• manual override and kill-switch controls;
• exchange-side reconciliation;
• testing before production deployment.

A Signal, confidence score, risk label or API event must not be treated as a guaranteed instruction to execute a trade.

WallStreetHack.com does not review or approve your position size, leverage, venue, order type or risk management.

18. Third-Party Systems

Your Application may connect the API to exchanges, wallets, cloud systems, messaging tools or other third-party services.

WallStreetHack.com does not control third-party:

• availability or performance;
• order execution;
• security and custody;
• data accuracy;
• account restrictions;
• fees and settlement;
• legal or regulatory status;
• terms and privacy practices.

You are responsible for obtaining all permissions required to connect to and use a third-party service.

19. API Versions, Deprecation and Changes

WallStreetHack.com may release new API versions, fields, endpoints and authentication methods.

We may also:

• modify response schemas;
• add or remove optional fields;
• change endpoint behaviour;
• introduce new limits;
• deprecate older versions;
• replace an unavailable data source;
• make urgent security changes.

Where reasonably practicable, material breaking changes will be communicated through Documentation, developer notices or another appropriate channel.

You are responsible for monitoring notices, maintaining compatibility and migrating before a stated deprecation date.

20. API Availability and Service Levels

Unless a separate written service-level agreement states otherwise, the API is provided without a guaranteed uptime, response time, delivery time or support resolution time.

The API may be interrupted because of:

• maintenance and upgrades;
• security incidents;
• network or hosting failures;
• blockchain or exchange-data outages;
• provider rate limits;
• emergency changes;
• events outside reasonable control.

Current operational information may be displayed on the API Status and Platform Status pages.

You must design your Application to tolerate temporary availability problems and incomplete responses.

21. API Fees, Billing and Taxes

Paid API access is billed according to the price, currency, billing period and usage terms disclosed for the applicable plan.

Unless otherwise stated:

• fees grant access only for the paid period;
• recurring plans renew until cancelled;
• usage above the plan limit may be blocked or separately charged if disclosed;
• applicable taxes may be added or included as required;
• bank and currency-conversion fees remain the subscriber’s responsibility.

Billing, cancellation and refund rules are described in the Subscription Agreement and Refund and Cancellation Policy.

22. Usage Monitoring and Compliance Review

WallStreetHack.com may monitor API activity to operate, secure and enforce the Service.

Monitoring may include:

• credential and account identifiers;
• source IP addresses;
• endpoints and methods requested;
• request and response times;
• status and error codes;
• rate-limit consumption;
• webhook delivery results;
• suspected abuse or security events.

Where a custom enterprise agreement includes usage reporting or audit rights, you must provide reasonably requested information necessary to confirm compliance.

Monitoring will be handled according to the Privacy Policy.

23. Temporary Suspension

WallStreetHack.com may temporarily suspend or limit API access where reasonably necessary because of:

• credential compromise;
• excessive or abusive request volume;
• non-payment;
• suspected fraud or unlawful use;
• market-manipulation concerns;
• a security vulnerability;
• risk to another user or the infrastructure;
• a legal or regulatory requirement;
• a material breach of these API Terms.

Immediate suspension may occur where advance notice would increase security, legal or operational risk.

Where appropriate, WallStreetHack.com may request corrective action before access is restored.

24. Termination and Effects of Termination

You may terminate API access by cancelling the relevant plan and ceasing all use of the API.

WallStreetHack.com may terminate API access where:

• you materially breach these API Terms;
• payment remains overdue;
• you misuse credentials or API Data;
• you engage in unlawful or harmful conduct;
• continued access creates a security risk;
• the API plan or service is discontinued;
• termination is required by law.

After termination:

• API Credentials may be revoked;
• webhook delivery may stop;
• access to private Documentation may end;
• you must stop new collection of API Data;
• you must delete data where required by the applicable licence;
• accrued payment and legal obligations remain enforceable.

Provisions concerning intellectual property, confidentiality, liability, indemnity and governing law survive where their nature requires survival.

25. Intellectual Property

WallStreetHack.com and its licensors retain all rights in:

• the API and underlying software;
• API Data and databases;
• Signal structures and methodology;
• documentation and examples;
• website design and interfaces;
• trademarks, names and branding;
• updates, modifications and derivative platform technology.

Your Application remains yours, excluding WallStreetHack.com technology, API Data and intellectual property incorporated into or accessed by it.

Feedback voluntarily provided about the API may be used to improve the Service without an obligation to compensate you, unless separately agreed in writing.

26. API and Data Disclaimers

To the maximum extent permitted by law, the API is provided on an “as available” basis without warranties concerning:

• continuous availability;
• error-free operation;
• delivery timing;
• data completeness;
• fitness for a particular trading strategy;
• profitability or financial performance;
• compatibility with every system;
• continued availability of an endpoint or data source.

The Risk Disclosure and Financial Disclaimer apply to API Data and integrations.

27. Limitation of Liability

To the maximum extent permitted by applicable law, WallStreetHack.com is not liable for losses resulting from:

• trades or financial decisions made by an Application;
• market movement, slippage or liquidation;
• delayed, duplicated or missing API events;
• incorrect integration logic;
• failure to validate or reconcile data;
• third-party exchange or wallet failure;
• credential exposure caused by the Developer;
• incompatible API changes after reasonable notice;
• unauthorised resale or downstream use;
• business interruption or loss of expected profit.

The general liability limitations in the Terms and Conditions also apply.

Nothing excludes liability or rights that cannot lawfully be excluded or limited.

28. Indemnification

To the extent permitted by law, you agree to defend, indemnify and hold WallStreetHack.com harmless from third-party claims, losses and reasonable costs arising from:

• your Application;
• your breach of these API Terms;
• unlawful or unauthorised use of API Data;
• your infringement of third-party rights;
• your failure to protect credentials;
• misleading financial or performance claims;
• your automated trading or execution system;
• your violation of privacy or consumer law.

This obligation does not apply to the extent a claim results from WallStreetHack.com’s own conduct for which liability cannot lawfully be excluded.

29. Governing Law and Disputes

These API Terms are governed by the laws of the Republic of Cyprus, subject to mandatory rights that apply under another applicable law.

Before starting formal proceedings, the parties should attempt to resolve the issue through the Support page.

Subject to mandatory law and a separately signed agreement, disputes will fall within the jurisdiction of the competent courts of Nicosia, Cyprus.

30. Changes to these API Terms

WallStreetHack.com may update these API Terms to reflect:

• new endpoints or functionality;
• technical or security changes;
• new billing or usage models;
• changes in law or regulation;
• changes in data sources or licences;
• changes in business operations.

The revised version will be published with an updated revision date.

Material changes affecting an active paid API plan will be communicated where required by the applicable agreement or law.

Continued API use after an updated version becomes effective constitutes acceptance where that method of acceptance is legally valid.

31. Operator and Developer Support

Questions concerning API access, billing, security, technical restrictions or these API Terms should be submitted through the official support channel.

Include the API plan, affected endpoint, approximate request time, request ID, status code and a redacted credential identifier where relevant.

Do not submit complete API keys, webhook secrets, exchange passwords, wallet seed phrases or private keys.