API Access, Commercial Licensing, Dataset Usage & Developer Agreement

Effective Date: September 2026 Version: 1.0 Jurisdiction: Federal Republic of Nigeria

1.0 Agreement & Platform Scope

Welcome to SdashAPI ("SdashAPI", "Platform", "we", "us", or "our").

These Developer Terms of Service ("Terms") constitute an agreement between SdashAPI and any developer, individual, business, startup, educational institution, school, organization, enterprise, or other entity ("Developer", "Customer", "User", "you", or "your") that creates an account, purchases API credits, subscribes to a plan, accesses SdashAPI documentation, obtains an API key, accesses a dataset, or uses any SdashAPI endpoint or service.

SdashAPI provides educational and assessment data infrastructure designed to help developers build examination-preparation, CBT, learning, assessment, educational and related applications.

Depending on the API version, endpoint, plan and dataset, SdashAPI content may include:

Examination and practice questions;
Question options;
Correct answers;
Sections and instructions;
Passages;
Solutions and explanations;
Topics and subtopics;
Difficulty classifications;
Common mistakes;
Images and diagrams where available;
Mathematical formatting where applicable;
Examination year and examination type;
University or institutional information where applicable;
Question metadata;
AI-generated or AI-enhanced educational content;
Synthetic practice questions;
Curriculum classifications;
Other structured educational and assessment information.

By creating a SdashAPI account, purchasing credits, subscribing to a paid plan, obtaining or using an API key, accessing a licensed dataset, or making a request to a SdashAPI endpoint, you agree to be bound by these Terms.

If you are using SdashAPI on behalf of a company, school, organization or other legal entity, you represent that you have authority to accept these Terms on its behalf.

2.0 Accounts, Authentication & API Keys

Access to SdashAPI may require a registered account and valid API credentials.

2.1 API Keys

API keys are used to authenticate requests, identify accounts, apply rate limits, determine plan access, measure usage and deduct applicable API credits.

Your API key is confidential.

You are responsible for protecting your API credentials against unauthorized access.

2.2 Client-Side API Key Exposure

Developers must take reasonable measures to prevent SdashAPI API keys from being publicly exposed.

API keys should not be intentionally published in:

Public source-code repositories;
Public JavaScript bundles;
Public websites;
Public documentation;
Shared code snippets;
Mobile applications where the key can be easily extracted;
APK or IPA files without appropriate server-side protection; or
Any other publicly accessible location.

Where reasonably possible, SdashAPI requests should be routed through a secure backend controlled by the Developer.

2.3 Responsibility for API Usage

You are responsible for API requests made using your credentials until the credentials are revoked or replaced.

This includes applicable:

API credit deductions;
Rate-limit usage;
Endpoint requests;
Data retrieval;
Charges; and
Activities performed through your API key.

2.4 Credential Sharing

You may not sell, rent, sublicense or provide your SdashAPI API key to an unrelated third party for that party to independently consume SdashAPI services.

This does not prevent employees, contractors or infrastructure providers working on your authorized application from accessing credentials where reasonably necessary and appropriately secured.

2.5 Compromised Credentials

If you believe an API key has been leaked, stolen or otherwise compromised, you should revoke or replace the affected key as soon as reasonably possible.

SdashAPI may revoke or rotate compromised credentials where necessary to protect the Platform.

3.0 API Versions & Data Access

SdashAPI may provide multiple API versions, including V1, V2, V3 and V4.

Access to a particular API version, endpoint, feature or data field depends on your applicable plan.

Purchasing access to one version does not automatically grant access to every other version.

3.1 V1

V1 provides core examination-question functionality.

Depending on the applicable question, V1 data may include:

Question;
Options;
Correct answer;
Section or instruction where applicable;
Solution or explanation;
Image where applicable;
Examination type;
Examination year;
University where applicable; and
Other basic question fields.

Not every question necessarily contains every optional field.

3.2 V2–V4

V2, V3 and V4 may provide progressively richer, enhanced or differently structured educational data.

Depending on the version, subject and available source material, these versions may include:

Questions;
Options;
Correct answers;
Sections;
Instructions;
Passages;
Detailed solutions and explanations;
Topics;
Subtopics;
Difficulty classifications;
Question types;
Common mistakes;
Explanations of why alternative options are incorrect;
Images and diagrams where available;
Mathematical expressions and formatting;
Curriculum classifications;
Additional metadata; and
Other structured educational information.

SdashAPI may introduce, modify, improve, rename, deprecate or replace API versions and individual fields as the Platform develops.

3.3 Plan-Based Access

Developers may only access API versions, subjects, endpoints, features and datasets included in their current plan or separately purchased licence.

Attempting to bypass plan restrictions or access unauthorized versions is prohibited.

4.0 Commercial Rights & White-Label Use

4.1 Commercial Application Rights

Subject to these Terms, an eligible paid SdashAPI plan grants the Developer a limited, non-exclusive, worldwide, revocable licence to use permitted SdashAPI API responses within the Developer's own applications and services.

This includes commercial products such as:

CBT applications;
Examination-preparation applications;
JAMB/UTME preparation platforms;
WAEC/WASSCE preparation platforms;
Educational websites;
Mobile applications;
Desktop applications;
Learning management systems;
School portals;
Assessment platforms;
Telegram or messaging bots;
Educational AI applications; and
Similar student-facing educational products.

Developers may charge their own customers for products incorporating SdashAPI functionality where their applicable SdashAPI plan permits commercial use.

4.2 White-Label Rights

Paid SdashAPI customers may generally integrate permitted API content on a white-label basis.

Unless a particular plan, promotion or separate agreement expressly states otherwise, you are not required to display "Powered by SdashAPI" to your end users.

4.3 Commercial Use Does Not Mean Ownership

Commercial-use permission does not transfer ownership of SdashAPI or its database to the Developer.

A Developer's right to use API responses within an application is separate from the right to:

Own the underlying dataset;
Download the complete database;
Permanently mirror SdashAPI;
Redistribute the database;
Sell raw questions;
Operate a competing API; or
Sublicense SdashAPI data.

Those rights are not granted unless expressly provided under a separate Dataset Licence or written agreement.

5.0 Pay As You Go

SdashAPI may provide a Pay As You Go ("PAYG") plan.

5.1 Usage-Based Charging

PAYG is a usage-based service.

API usage is charged according to the API requests, calls, credits, endpoints, resources or usage rules applicable to the PAYG plan.

PAYG does not mean unlimited API calls.

Each applicable request consumes the corresponding amount of purchased API balance or credits.

5.2 PAYG Credits

Purchased PAYG credits remain available until consumed and do not expire solely because they remain unused.

SdashAPI may nevertheless suspend access to credits where an account is terminated for fraud, abuse or material breach of these Terms.

5.3 PAYG Version Access

PAYG customers may only use API versions and features expressly included in PAYG at the time of use.

PAYG access does not automatically include V2, V3, V4 or future API versions.

6.0 Monthly Subscription Plans & API Credits

SdashAPI may offer recurring subscription plans with different credit allocations, rate limits, API versions, subjects, endpoints and features.

6.1 Monthly Credits

Each monthly plan receives the API credit allocation advertised for that plan.

Monthly credits reset at the end of the applicable billing cycle.

Unless expressly stated otherwise for a particular plan, unused monthly subscription credits do not roll over into the next billing cycle.

This rule does not apply to separately purchased PAYG credits, which do not expire merely because they remain unused.

6.2 Plan Limits

Different plans may have different:

Credit allocations;
Requests-per-minute limits;
Requests-per-day limits;
API versions;
Subject access;
Examination access;
Endpoint access;
Support levels;
Dataset features; and
Other usage restrictions.

The limits displayed on the applicable pricing page, Developer Dashboard, documentation or purchase agreement form part of the Developer's plan.

6.3 Changes Between Plans

Upgrading or downgrading may alter your available API versions, credits, rate limits and features.

7.0 Rate Limits & Fair Usage

SdashAPI applies rate limits to maintain Platform reliability and fair access.

Rate limits may differ between PAYG, subscription, custom and enterprise plans.

The applicable rate limit will be specified through the pricing page, Developer Dashboard, documentation, API response or separate agreement.

Developers may not attempt to bypass rate limits through:

Multiple unauthorized accounts;
Rotating API keys;
Proxy networks;
Distributed scraping;
Automated credential rotation;
Artificial request distribution; or
Other mechanisms intended primarily to circumvent Platform restrictions.

SdashAPI may temporarily throttle requests that exceed applicable limits.

8.0 Caching & Application Storage

8.1 Paid Developer Caching

Paid Developers are permitted to cache SdashAPI API responses where reasonably necessary for the operation and performance of their applications.

Permitted purposes include:

Improving application performance;
Reducing unnecessary duplicate requests;
Maintaining active CBT sessions;
Supporting temporary connectivity interruptions;
Improving user experience; and
Providing reasonable application functionality.

SdashAPI does not impose a fixed short caching period on legitimate paid application usage unless otherwise specified for a particular plan or endpoint.

8.2 Caching Is Not Dataset Extraction

Caching rights do not authorize Developers to systematically retrieve the SdashAPI catalogue for the purpose of reconstructing, cloning or permanently storing the entire SdashAPI database.

A cache must not be used as a disguised bulk dataset extraction system.

8.3 Permanent Database Mirroring

PAYG and standard monthly subscriptions do not grant permission to:

Download the entire SdashAPI database;
Systematically crawl all questions;
Permanently mirror substantial portions of SdashAPI;
Reconstruct the SdashAPI question bank;
Maintain an independent permanent copy intended to replace API consumption; or
Continue operating a copied SdashAPI database after API access ends.

Permanent dataset rights require an appropriate Custom Plan, Enterprise arrangement or separate Dataset Licence.

9.0 Offline Products & Dataset Licences

Standard API subscriptions are intended primarily for applications consuming SdashAPI through authorized API access.

Organizations requiring permanent datasets for:

Offline CBT centres;
Offline mobile applications;
Air-gapped systems;
Schools with limited connectivity;
Institutional deployments;
Government deployments;
Local examination servers; or
Other systems requiring permanent local question storage

must obtain an appropriate special plan or separate Dataset Licence from SdashAPI.

9.1 Dataset Licence Rights

A Dataset Licence may permit the customer to permanently download, store and incorporate specifically licensed SdashAPI data into approved products.

The exact rights depend on the applicable licence.

A Dataset Licence may specify:

Subjects;
Examination types;
Years;
API/data versions;
Duration;
Number of products;
Commercial rights;
Storage rights;
Update rights;
Redistribution restrictions;
Geographic scope;
Organization or application scope; and
Other conditions.

9.2 Dataset Licence Does Not Automatically Permit Resale

Permanent storage rights do not automatically include the right to resell or redistribute the licensed dataset.

Redistribution requires explicit written permission.

10.0 Custom Plans & Separate Commercial Agreements

SdashAPI may negotiate Custom, Enterprise, Bulk Dataset or other commercial arrangements with individual customers.

Where SdashAPI and a Developer execute a separate written agreement, commercial licence or Dataset Licence, that agreement supplements these Terms.

If a provision of a specifically negotiated written agreement conflicts with these standard Terms, the specifically negotiated agreement shall control with respect to the subject matter covered by that agreement.

All provisions of these Terms that do not conflict with the separate agreement continue to apply.

11.0 Intellectual Property, Examination Content & Proprietary Data

11.1 Historical Examination Content

SdashAPI curates, structures, organizes, digitizes, enhances and makes historical examination questions and educational assessment materials available for educational, study, research, practice and examination-preparation purposes.

Such materials may include historical questions associated with examination bodies and educational institutions, including JAMB/UTME, WAEC/WASSCE, NECO, Post-UTME examinations and university examinations.

11.2 SdashAPI Proprietary Enhancements

Regardless of the source of any underlying historical examination question, the SdashAPI database may contain substantial original or proprietary enhancements, including:

Metadata;
Topic classifications;
Subtopic classifications;
Difficulty classifications;
Detailed solutions;
Explanations;
Common-mistake analyses;
Explanations of incorrect options;
Structured formatting;
Mathematical formatting;
Sections and passage organization;
Image and diagram processing;
Curriculum mappings;
Database organization;
Taxonomies;
Synthetic questions;
AI-generated educational content;
Question relationships; and
Other enriched data.

11.3 SdashAPI Platform Intellectual Property

SdashAPI's original API architecture, documentation, database organization, software, source code, algorithms, branding, original educational materials, synthetic materials, proprietary datasets, metadata systems and other SdashAPI-created components remain the intellectual property of SdashAPI or its applicable licensors.

11.4 No Transfer of Ownership

Purchasing credits, paying for a subscription or accessing an API does not transfer ownership of SdashAPI's database, Platform or proprietary content to the Developer.

You receive only the licence rights expressly granted under these Terms or your applicable separate agreement.

11.5 Reservation of Rights

Rights not expressly granted under these Terms, a Dataset Licence, Custom Plan or separate written agreement are reserved by SdashAPI and its applicable licensors.

12.0 Examination Bodies, Trademarks & Independence

References to examination bodies, institutions and examination names are used for identification, classification, educational reference and examination-preparation purposes.

Names and trademarks associated with JAMB, UTME, WAEC, WASSCE, NECO, universities, educational institutions and other third parties remain associated with their respective rights holders.

SdashAPI is an independent educational technology and API infrastructure provider.

Unless expressly stated otherwise, SdashAPI is not affiliated with, endorsed by, sponsored by, operated by, or an official representative of JAMB, WAEC, NECO, any university, or any other examination body or educational institution.

Nothing in these Terms should be interpreted as claiming ownership by SdashAPI of a third party's registered trademark merely because the trademark is used to identify an examination or educational dataset.

13.0 Redistribution, Resale & Competing Services

13.1 No Raw Dataset Redistribution

Unless separately authorized in writing, Developers may not resell, sublicense, publish, distribute or make substantial SdashAPI content available as:

JSON datasets;
CSV datasets;
SQL databases;
ZIP archives;
Spreadsheet exports;
Database dumps;
Bulk downloadable question banks;
Public repositories;
Data feeds;
Torrents;
Scraped collections; or
Other substantially equivalent raw-data products.

13.2 End-User Products Are Permitted

This restriction does not prevent eligible paid Developers from displaying and using permitted SdashAPI content as part of the normal functionality of their commercial educational applications.

For example, displaying a question to a student inside a licensed CBT application is permitted.

Selling a downloadable JSON database containing thousands of SdashAPI questions is not permitted unless separately licensed.

13.3 Competing APIs

You may not use SdashAPI content to operate another API whose primary purpose is to redistribute, sublicense or expose SdashAPI content to other developers.

You may not simply place your own API layer in front of SdashAPI and sell access to SdashAPI's question database.

A separate redistribution, reseller or data-provider agreement is required for such use.

14.0 AI & Machine Learning Use

SdashAPI recognizes that modern educational applications may use artificial intelligence.

14.1 Permitted Application-Level AI Use

Developers may send individual SdashAPI responses or reasonable portions of content to AI systems where reasonably necessary to provide legitimate features to their end users.

Examples may include:

Additional explanations;
Student tutoring;
Personalized feedback;
Question discussion;
Study assistance;
Answer analysis; and
Similar educational features.

14.2 Prohibited Bulk AI Training

Unless expressly authorized in writing by SdashAPI, Developers may not systematically harvest substantial quantities of SdashAPI content for the purpose of:

Training an AI model;
Pre-training a model;
Fine-tuning a model;
Distilling a model;
Creating a competing educational model;
Reconstructing SdashAPI's question bank;
Creating a competing examination dataset; or
Building a substantially equivalent assessment-data service.

The fact that individual application-level AI processing is permitted does not authorize bulk extraction of the SdashAPI database.

15.0 Scraping, Bulk Extraction & Abuse

Developers must access SdashAPI using authorized methods and within their applicable plan limits.

The following activities are prohibited unless expressly authorized:

Automated bulk scraping;
Systematic database harvesting;
Attempting to enumerate the entire SdashAPI database;
Distributed scraping;
Using rotating proxies to evade restrictions;
Circumventing pagination restrictions;
Circumventing rate limits;
Using multiple accounts to bypass plan limits;
Credential theft;
Fraudulent API usage;
Unauthorized database extraction;
Reverse engineering intended to reproduce SdashAPI's proprietary database;
Attacking or interfering with SdashAPI infrastructure; or
Using the Platform in a manner reasonably likely to degrade service for other Developers.

SdashAPI may monitor request patterns for security, fraud prevention, abuse detection, metering and Platform reliability.

16.0 Developer & Student Data

16.1 Developer Ownership

SdashAPI does not claim ownership of the Developer's independent application data merely because the Developer uses SdashAPI.

Developers retain their rights in data generated through their applications, including:

Student accounts;
Student profiles;
Test attempts;
Student responses;
Scores;
Performance records;
Progress histories;
Custom analytics;
Internal application telemetry; and
Other Developer-generated information.

16.2 Student Privacy

Developers are responsible for the personal data they independently collect from their users.

Developers must comply with applicable privacy and data-protection requirements, including the Nigeria Data Protection Act 2023 where applicable.

Developers should not transmit unnecessary sensitive or personally identifiable student information to SdashAPI through fields that are intended only for assessment-content requests.

16.3 Developer Responsibility

Each Developer is responsible for:

Providing appropriate privacy notices;
Obtaining legally required consent;
Protecting student information;
Securing its own databases;
Handling children's information appropriately;
Responding to applicable data-subject requests; and
Complying with applicable privacy laws.

17.0 Payments, Credits, Deposits & Refunds

17.1 Non-Refundable Payments

Except where required by applicable law or expressly agreed otherwise in writing by SdashAPI, completed payments are non-refundable.

This includes:

Subscription payments;
PAYG credit purchases;
Dataset licence payments;
Custom plan payments;
Deposits;
Setup fees; and
Other Platform payments.

17.2 PAYG Credit Expiry

Unused PAYG credits do not expire merely because a particular amount of time has passed.

17.3 Monthly Credit Reset

Credits included as part of a monthly subscription reset at the end of the applicable monthly billing cycle.

Unless a particular plan expressly provides otherwise, unused monthly credits are not carried forward.

17.4 Pricing Changes

SdashAPI may change pricing, credit costs, plan structures and included features.

Changes ordinarily apply prospectively rather than retroactively to API requests already consumed.

Where practical, material changes affecting active recurring plans may be communicated through the Platform, email, dashboard or other reasonable means.

18.0 Suspension & Termination

SdashAPI may suspend, throttle, restrict or terminate access where reasonably necessary because of:

Fraud;
Payment abuse;
Scraping;
Credential sharing;
Security threats;
Attempts to bypass rate limits;
Unauthorized database extraction;
Resale of API credentials;
Operating a prohibited competing API;
Serious infrastructure abuse;
Illegal use;
Material breach of these Terms; or
Conduct that materially threatens SdashAPI or other Developers.

Where appropriate, SdashAPI may provide the Developer an opportunity to correct a violation.

However, immediate suspension may occur where necessary to prevent ongoing scraping, security threats, fraud, unauthorized extraction or other serious abuse.

Termination of standard API access does not create permanent dataset rights.

A customer's rights under a separately purchased Dataset Licence will be determined by that Dataset Licence.

19.0 API Availability, Maintenance & Changes

SdashAPI aims to provide reliable API infrastructure but does not guarantee uninterrupted availability.

The Platform may occasionally experience:

Scheduled maintenance;
Emergency maintenance;
Hosting-provider failures;
Network interruptions;
Database maintenance;
Security incidents;
Software bugs;
Third-party infrastructure failures;
Upgrades; or
Other technical interruptions.

SdashAPI may modify endpoints, response structures or Platform functionality as the service develops.

Where reasonably practical, Developers will be given notice before material breaking changes or permanent endpoint deprecations.

Developers are responsible for maintaining their integrations and adapting to documented API changes.

20.0 Content Accuracy & Educational Disclaimer

SdashAPI takes reasonable steps to improve the quality, structure and usefulness of its educational data.

However, examination content, answers, explanations, metadata, classifications, AI-generated material and other information are provided on an "AS IS" and "AS AVAILABLE" basis.

SdashAPI does not guarantee that every:

Question is error-free;
Answer is error-free;
Explanation is exhaustive;
Metadata classification is perfect;
Historical question exactly reflects an original examination paper;
Curriculum remains unchanged;
Examination format remains unchanged; or
Future examination follows historical patterns.

Developers should provide reasonable mechanisms for reporting suspected errors.

SdashAPI may correct, replace, update or remove content when errors are identified.

21.0 No Guarantee of Examination Results

SdashAPI is an educational and assessment infrastructure service.

Use of SdashAPI does not guarantee:

A particular JAMB/UTME score;
A particular WAEC/WASSCE grade;
A particular NECO grade;
University admission;
Scholarship eligibility;
Examination success;
Employment;
Certification; or
Any other academic outcome.

Developers must not falsely represent SdashAPI content as guaranteeing official examination results.

The reference agreement similarly separates assessment infrastructure from official examination outcomes and disclaims guarantees regarding future examination structures.

22.0 Prohibited & Unlawful Uses

Developers may not knowingly use SdashAPI to:

Facilitate examination malpractice;
Obtain unauthorized access to live examination systems;
Distribute stolen unreleased examination papers;
Commit fraud;
Violate applicable laws;
Infringe third-party rights;
Attack another computer system;
Misrepresent affiliation with an examination body;
Impersonate SdashAPI;
Circumvent Platform security; or
Engage in activity materially inconsistent with these Terms.

SdashAPI is intended for legitimate educational, study, practice, assessment and examination-preparation purposes.

23.0 Support

Support availability may depend on the Developer's plan.

Support channels may include:

Email;
WhatsApp;
Developer documentation;
Dashboard assistance; and
Other channels made available by SdashAPI.

Higher-tier or Custom Plans may receive different support arrangements.

Support does not guarantee custom development, debugging of unrelated third-party software or immediate resolution of every integration problem unless specifically included in the applicable plan.

24.0 Limitation of Liability

To the maximum extent permitted by applicable law, SdashAPI shall not be liable for indirect, incidental, special, consequential, exemplary or punitive damages arising from use of or inability to use the Platform.

This includes, where legally permitted:

Lost profits;
Lost revenue;
Lost business opportunities;
Loss of goodwill;
Business interruption;
Loss of application data;
Failed examinations;
Admission outcomes; or
Losses resulting from temporary API unavailability.

To the maximum extent permitted by applicable law, SdashAPI's aggregate liability arising from a standard API subscription or PAYG account shall not exceed the total amount actually paid by the Developer to SdashAPI during the three months immediately preceding the event giving rise to the claim.

Different liability arrangements may apply where expressly provided in a separately executed Enterprise or Dataset Licence agreement.

25.0 Indemnification

To the extent permitted by applicable law, you agree to indemnify and hold SdashAPI harmless against third-party claims, liabilities, damages and reasonable costs arising directly from:

Your unlawful use of the Platform;
Your material violation of these Terms;
Your unauthorized redistribution of SdashAPI data;
Your infringement of another person's rights through your application;
Your mishandling of student personal data;
Your misleading representations to your customers; or
Your use of SdashAPI in an unauthorized product or service.

This provision does not require you to indemnify SdashAPI for claims caused solely by SdashAPI's own unlawful conduct.

26.0 Changes to These Terms

SdashAPI may update these Terms as the Platform, API versions, pricing models, laws and services evolve.

The latest version may be published on the SdashAPI website or Developer documentation.

Where a change materially affects existing Developers' rights or obligations, SdashAPI may provide reasonable notice through:

Email;
Developer Dashboard;
Website notification;
Documentation; or
Another reasonable communication method.

Continued use of SdashAPI after updated Terms become effective constitutes acceptance of the revised Terms, subject to applicable law.

A separately executed written agreement remains governed by its own amendment provisions.

27.0 Governing Law & Dispute Resolution

These Terms shall be governed by and construed in accordance with the laws of the Federal Republic of Nigeria.

If a dispute arises between a Developer and SdashAPI, the parties should first attempt to resolve the matter through good-faith informal negotiations.

A party raising a dispute should provide sufficient information for the other party to understand the nature of the complaint.

The parties should attempt informal resolution for at least thirty (30) days before commencing formal proceedings, except where urgent legal relief is reasonably necessary.

Where a dispute cannot be resolved informally, it may be referred to arbitration or another dispute-resolution mechanism permitted under Nigerian law, including the Arbitration and Mediation Act 2023, where applicable.

Proceedings shall be conducted in English.

28.0 Severability

If a court or other competent authority determines that any provision of these Terms is invalid, unlawful or unenforceable, that provision shall be interpreted or limited to the minimum extent necessary while the remaining provisions continue in effect.

29.0 No Waiver

If SdashAPI does not immediately enforce a provision of these Terms, that does not mean SdashAPI has permanently waived the right to enforce that provision.

A waiver concerning one violation does not automatically constitute a waiver concerning another violation.

30.0 Assignment

Developers may not transfer or assign their SdashAPI account, Dataset Licence or rights under these Terms to another unrelated entity without SdashAPI's written authorization where such transfer would materially change the licensed customer or permitted use.

SdashAPI may transfer its rights and obligations as part of a legitimate restructuring, acquisition, merger or transfer of the Platform, subject to applicable law.

31.0 Entire Agreement & Order of Precedence

These Terms, together with the Developer's applicable:

Pricing plan;
API documentation;
Dataset Licence;
Custom Plan;
Enterprise agreement; and
Other written commercial agreement

constitute the agreement governing the applicable SdashAPI services.

Where there is a conflict, the following order generally applies:

1. Separately signed Custom, Enterprise or Dataset Licence agreement 2. Specific written commercial terms issued by SdashAPI for the customer's purchase 3. These Developer Terms of Service 4. General API documentation

A specifically negotiated agreement controls only to the extent of the matters it addresses.

32.0 Contact

Questions concerning these Terms, commercial licensing, Dataset Licences, API usage or legal matters may be directed to:

SdashAPI Email: chat@sdashapi.com Website: sdashapi.com

33.0 Acceptance

By creating a SdashAPI account, purchasing API credits, subscribing to a plan, obtaining an API key, accessing a licensed dataset, or continuing to use SdashAPI after these Terms become effective, you acknowledge that you have read and understood these Terms and agree to be bound by them.

SdashAPI Developer Terms of Service