Back to Blog

    November 15, 2026

    API License Agreement: 12 Clauses to Get Right (API and SDK Licensing)

    Drafting a deal? Use the free SaaS licensing agreement template.

    Looking for SaaS to license? Browse live listings or explore products by category. New to the deal structures? Compare licence and white-label types or check a term in the glossary. Explore the white-label SaaS marketplace, software to license or license vs build. SaaS founder? List your Product for licensing.

    Quick answer: An API license agreement is the contract that lets a developer or business call your API under set rules. It should define who may use it and for what, how keys are issued and protected, rate limits and fees, who owns the data and the output, how versions change, and what happens on breach or termination.

    This guide is for founders and developers who sell or license access to an API, and for the agencies and product teams who build on one. It walks through the clauses that matter in an API license agreement, explains how an SDK license differs, and shows where API deals usually go wrong. It is general information, not legal advice: have a lawyer review any agreement before you sign or publish it.

    Key takeaways

    • An API license grants a right to call a service you run; an SDK license grants a right to copy and ship your code inside someone else's product.
    • Most disputes start in four places: what counts as permitted use, who owns the output, what happens when you change the API, and who pays for overage.
    • Tie fees to a metric you already meter, such as calls, records or active end customers, and state what happens above the limit.
    • Separate a public developer licence (click-through terms) from a negotiated commercial licence for partners who resell or white-label your API.
    • Give notice before breaking changes and deprecations, and keep the right to suspend keys that put the service or other customers at risk.

    What an API license agreement covers

    An API license agreement sets the rules for calling an interface you run. Unlike selling software, nothing is handed over: the customer gets a key and a right to send requests, and you keep the code, the servers and the data behind them. That makes the agreement less about ownership of a copy and more about behaviour: how much traffic is allowed, what the customer may build, what they may do with the responses, and what you promise about uptime and change.

    Most API providers end up with two documents:

    • Developer terms: a click-through licence every developer accepts when they create a key. It covers acceptable use, rate limits, attribution and termination, and it is the same for everyone.
    • A commercial or partner licence: a negotiated agreement for customers who pay more, need higher limits, or want to resell, embed or white-label your API in their own product. It adds pricing, service levels, branding rules and longer notice periods.

    If you are licensing your API to agencies, resellers or vertical software companies, the second document is where the money is, and it is the one most templates handle badly. Our page on licensing APIs covers the commercial side; this guide covers the contract.

    API license vs SDK license vs SaaS agreement

    QuestionAPI licenseSDK licenseSaaS agreement
    What the customer getsThe right to call your hosted endpointsA copy of your code or libraries to build withAccess to a finished application
    Where the software runsOn your serversInside the licensee's app, often on end-user devicesOn your servers
    Typical restrictionsRate limits, no scraping, no reselling raw accessNo reverse engineering, attribution, distribution limitsSeats, plans, acceptable use
    Typical feePer call, per tier or per end customerPer app, per device, royalty or freePer seat or per plan, monthly or annual
    Key risk for the providerAbuse, cost spikes, data misuseLosing control of copies of the codeChurn and support load
    Who usually signsDevelopers, product teams, resellersApp makers, device makers, OEM partnersEnd-user businesses

    The 12 clauses every API license agreement needs

    1. Grant and scope

    State exactly what is licensed: which endpoints, for which products, in which territories, and whether the licence is exclusive or non-exclusive (almost always non-exclusive for APIs; see exclusive vs non-exclusive licences). Name the permitted use, such as "inside the licensee's scheduling application", rather than leaving it at "internal business purposes".

    2. Restrictions

    List what the licensee may not do: resell or sublicense raw access, build a competing API, scrape or cache beyond stated limits, share keys, probe security, or use the API for unlawful purposes. If a partner is allowed to pass access on to its own customers, say so and set the conditions, as you would in a software sublicense agreement.

    3. Keys, authentication and security

    Keys identify the licensee, so the agreement should make them responsible for every call made with their keys, require them to keep keys secret, and let you rotate or revoke keys that leak. Add the security standard you expect from partners who store your data.

    4. Rate limits and usage caps

    Write down the limits for each plan (requests per second, per day or per month) and what happens at the limit: throttling, overage fees or a forced upgrade. Unpriced overage is one of the most common sources of disputes and surprise costs on both sides.

    5. Fees, billing and taxes

    Set the pricing model, the billing metric, when invoices are issued and paid, late-payment terms and who pays which taxes. If price changes are allowed, say how much notice the licensee gets.

    6. Data and privacy

    Say who owns the data the licensee sends you, what you may do with it (for example, to run and improve the service, or not at all), how long you keep it, and which data protection terms apply. Personal data usually needs a separate data processing agreement.

    7. Rights in API output

    The responses your API returns are often the valuable part. Decide whether the licensee may store them, display them, combine them with other data, or pass them on, and for how long after the licence ends. Data-heavy APIs should borrow terms from a data licensing agreement, including any rule on using output to train AI models.

    8. Branding and attribution

    Some providers require "powered by" attribution; white-label partners want the opposite. Spell out which marks may be used, how, and whether the end customer may see your name at all.

    9. Versioning, changes and deprecation

    APIs change. Promise notice before breaking changes (many providers give months, not days), keep old versions running for a stated period, and describe how deprecations are announced. Without this clause, a licensee who builds a product on your API carries all the risk of your roadmap.

    10. Service levels and support

    For paid tiers, state the uptime target, how it is measured, what counts as downtime, the support response times, and the remedy (usually service credits) when you miss them.

    11. Warranties, liability and indemnities

    Most API licences disclaim warranties beyond those stated, cap liability (often at fees paid over a recent period) and include indemnities: you cover intellectual property claims about the API, and the licensee covers claims caused by their own products and misuse.

    12. Term, suspension and termination

    Say how long the licence runs, how it renews, when you may suspend access (security risks, unpaid invoices, abuse) and what happens on exit: keys revoked, cached data deleted or returned, fees settled, and a wind-down period for partners whose own customers depend on the API.

    How an SDK license agreement differs

    An SDK licence gives the licensee a copy of your code: libraries, tools or a mobile component they ship inside their own product. Once copies are in the wild you cannot simply revoke a key, so the contract has to do more work:

    • Distribution: may the licensee redistribute the SDK only as part of their compiled app, or also as source? To how many devices or apps?
    • No reverse engineering: a standard restriction, subject to whatever the local law allows.
    • Open-source components: list them and their licences, because some impose conditions on the licensee's own code.
    • Attribution and notices: what must appear in the licensee's app or documentation.
    • Updates and end of life: whether the licensee must update to fixed versions, and what happens to apps already shipped when the licence ends.

    Device makers and app vendors who bundle your SDK at scale are closer to an OEM relationship; our guide to OEM software licensing covers royalties and per-unit terms.

    Pricing an API license

    The contract should match how you charge. Common models:

    • Free tier plus paid plans: a call allowance per month, with overage or an upgrade above it.
    • Pay per call or per record: simple to explain, harder for buyers to budget; see usage-based licensing for how to make metered pricing predictable.
    • Per end customer: a flat fee for each of the licensee's customers who uses a feature built on your API. Common in white-label and reseller deals.
    • Revenue share: a percentage of what the licensee earns from the product that uses your API; see revenue share agreements.
    • Annual commit: a minimum yearly spend in exchange for lower unit prices and higher limits.

    Illustrative example, not market data: an enrichment API might give developers 1,000 free calls a month, charge a plan with 100,000 calls and a per-call overage, and offer agencies a flat monthly fee per client account with white-label rights. Each of those needs its own limits and output terms in the agreement.

    Common mistakes in API deals

    • "Internal use" with no definition: a licensee builds a product for its customers and argues that is still internal use.
    • No rule on output: responses are cached forever, resold, or used to train a model that replaces your API.
    • No deprecation promise: the partner loses customers when you change an endpoint, and blames you.
    • Overage with no price: one runaway integration produces a bill nobody agreed to.
    • Click-through terms for a reseller: developer terms that forbid reselling are used for a deal that is entirely about reselling.

    Read the full licence before relying on it, and have it reviewed: this article is not legal advice. For the wider contract set around a SaaS product, see our SaaS licensing agreement guide and the comparison of EULA vs SaaS agreement.

    Where LicenseSaaS fits

    LicenseSaaS is a marketplace for licensing and white-label deals, including APIs. API owners can list an API for licensing for free and set the terms they offer, and buyers can browse software, APIs and AI tools to license or check API management listings. If you need a specific API that is not listed yet, post it on the buyer requests board. LicenseSaaS does not verify listings, so test the API, read the licence and check references before you build on it. Plans and fees are on the pricing page.

    Frequently asked questions

    What is an API license agreement?

    It is a contract between an API provider and a developer or business that sets how the API may be used: the scope of the licence, keys and security, rate limits, fees, data and output rights, changes to the API, liability and termination.

    What is the difference between an API license and an SDK license?

    An API licence lets you call a service the provider runs, so the code never leaves their servers. An SDK licence lets you copy the provider's code into your own app, so it adds terms on distribution, attribution, reverse engineering and open-source components.

    Can I resell or white-label someone else's API?

    Only if the licence allows it. Most public developer terms forbid reselling raw access or wrapping the API as a competing product. A reseller or white-label deal needs a negotiated licence that names the permitted products, branding and pricing rules.

    How do you charge for API access?

    Common models are free tiers with paid upgrades, monthly plans with a call allowance and overage, pure pay per call, revenue share, and flat fees per end customer for partners. Pick a metric you already measure and state what happens above the limit.

    Do I need a lawyer for an API license agreement?

    For a public click-through licence or a negotiated partner deal, yes, have a lawyer review it. Templates are a useful checklist, but data protection, liability caps and export rules depend on your product and where you and your customers are. This is not legal advice.

    Take the next step

    Discover SaaS products to license, browse by category, or list your own product on LicenseSaaS.