Strategic playbook

API copyright after Google v. Oracle

What the Supreme Court actually protected, what it left open, and how to reimplement an interface without treating fair use like a permission slip.

593 U.S. 1 (2021)6 to 2Fair useAPI declaring code

Start here

The 60-second answer

Google copied a limited slice of Java API declaring code, wrote new implementing code, and used the interface in a new smartphone platform. The Court held that use fair as a matter of law.

What traveled

Familiar commands and organization that let programmers call functions.

What did not

Oracle's implementing code, the logic that actually performed those functions.

So what do you actually do?Assume the interface may be protected. Reuse only what interoperability requires, build the implementation independently, and get counsel into the room before code ships.

Part I: first principles

Copyright has an accelerator and brakes

Reward creation

The Constitution authorizes limited exclusive rights to promote progress. Protection is a tool, not the finish line.

Preserve building blocks

Section 102(b) excludes ideas, procedures, systems, and methods of operation. Section 107 keeps room for fair use.

So what do you actually do?Frame the design question in two parts: what is functional, and what expressive material would you actually copy?

The essential distinction

Same doorway, different machinery

Declaring code

Math.max(x, y)

Names the function and tells a programmer how to call it. Functional, constrained, and tied to the interface.

Implementing code

if (x > y) {
  return x;
}
return y;

Performs the task. It contains the authored logic and sits closer to copyright's expressive core.

So what do you actually do?Build a source inventory that labels declarations, implementation, documentation, comments, tests, and organizational structure separately. Never call all of it “the API.”

Case anatomy

A decade of litigation, in four beats

2005 onward

Google builds Android and copies roughly 11,500 lines from 37 Java API packages.

District court

The trial court holds the API material not copyrightable.

Federal Circuit

The appeals court reverses on copyrightability, then rejects fair use.

2021

The Supreme Court assumes copyrightability and decides fair use.

So what do you actually do?Separate the two questions in your risk memo: “Is it protected?” and “If it is, is this use fair?” Google won the second without settling the first.

The holding

6:2

Breyer, J.
April 5, 2021

Fair use, as a matter of law

Google reimplemented a user interface and took only what programmers needed to use their existing skills in a new program.

So what do you actually do?Do not reduce the holding to “APIs are free to copy.” The Court did not say that, and the details of Google's implementation did the legal work.

Part II: fair use

Four factors, one fact-specific judgment

Purpose

Why and how are you using it?

New purpose helps

Nature

How functional or expressive is the material?

Function helps

Amount

Did you take only what the purpose required?

Minimum helps

Market

Does the use substitute for protected markets?

Distance helps

So what do you actually do?Write one page per factor before launch. If the same facts appear in every section, your record is probably too thin.

Factor 1: purpose and character

New context mattered more than commerciality

Android was commercial. That did not end the analysis. The majority focused on the new smartphone platform and the new creative opportunities it gave programmers.

Stronger posture

Interoperability, a new platform, a distinct user context, and independent implementation.

Weaker posture

The same interface, for the same audience, in a direct substitute that does not add a meaningfully different purpose.

So what do you actually do?Write the “new purpose” in product language, not legal adjectives. Name the new users, platform, constraints, and tasks. “Transformative” by itself proves nothing.

Factor 2: nature of the work

Function gets thinner protection

The Court put declaring code farther from copyright's core than most computer programs. Its value came partly from programmers already knowing it, not only from expressive choices.

FUNCTIONAL

EXPRESSIVE

Lower concern

Names, signatures, compatibility constraints.

Needs analysis

Selection, arrangement, and organizational structure.

Higher concern

Algorithms, expressive logic, comments, and prose documentation.

So what do you actually do?For every copied element, record the functional constraint that made it necessary. If you cannot name one, redesign or license it.

Factor 3: amount and substantiality

11,500 lines sounds large. Context changed the number.

0.4%

Approximate share of the 2.86 million lines in the Java SE program, as described by the Court.

The real question

Was the amount reasonable for the interoperability purpose? The majority found Google took the declarations it needed and wrote the implementing code itself.

So what do you actually do?Keep a declaration-level necessity log: copied item, compatibility reason, alternatives tested, and why a smaller set would fail.

Factor 4: market effect

Ask “substitute for what?”

The record allowed the jury to find that Android's smartphone platform was not a market substitute for Java SE, and that Sun had struggled in mobile.

Actual market

Does your product displace sales or licenses now?

Potential market

Is the owner plausibly entitled to develop or license this use?

Public benefit

Does interoperability unlock creation without granting control over a new market?

So what do you actually do?Create a market map with products, customers, license types, and substitution evidence. “Different industry” is not a market analysis.

Part III: the limits

Three things you cannot claim

“APIs are categorically uncopyrightable.” The Court assumed copyrightability and moved to fair use.

“API copying is now generally fair.” The majority described the holding as narrow and tied it to reimplementation facts.

“A new product is automatically transformative.” Purpose, amount, nature, and market still have to be analyzed together.

So what do you actually do?Treat fair use as a litigation defense, not an engineering license. Escalate same-platform substitutes, implementation copying, and unclear market overlap.

The 2023 update

2023MAY 18 · 7 TO 2
SOTOMAYOR, J.

Warhol tightened the “transformative” story

Andy Warhol Foundation v. Goldsmith, 598 U.S. 508 (2023), held that when a commercial secondary use shares the same or a highly similar purpose with the original, factor one can weigh against fair use.

Transformation has to do more than what ordinarily makes a derivative work. In practical terms, the same-purpose objection Oracle pressed is harder to brush aside today than it was in 2021.

So what do you actually do?Re-run factor one for the specific challenged use, not just the work in the abstract. Ask who licenses it, for what purpose, and whether your use competes for that same job.

Part IV: phase 1

Before anyone opens the repository

Inventory assets. Code, APIs, tests, docs, comments, data structures, and third-party licenses.

Classify material. Separate declarations, implementation, organization, and prose.

Define necessity. List the minimum compatibility surface.

Map markets. Identify direct substitutes and plausible licensing markets.

Test alternatives. Document why a new interface, adapter, or license will not work.

Get a legal read. Resolve red flags before architecture hardens.

So what do you actually do?Make the IP review a design gate with named owners and a written exit decision. “Legal knows about it” is not a control.

Phase 2: development

A clean room is a process, not a label

Specification team

Studies the public behavior and authorized materials. Produces a functional specification, necessity record, and test cases.

SPEC ONLY

Implementation team

Does not see the original implementation. Builds new code from the specification and records independent design choices.

So what do you actually do?Control access, preserve review logs, scan for suspicious similarity, and require provenance for every imported snippet. Two teams with a shared chat history are not a clean room.

Phases 3 and 4

Ship the evidence with the software

Release review

Recheck the exact code, purpose, and market at launch. Scope drift can undo an earlier analysis.

Governance

Use a cross-functional review board, an escalation path, and engineering training tied to real examples.

Monitoring

Track legal developments, license changes, new market entry, and product changes that alter the four factors.

✓

Provenance manifest

✓

Necessity log

✓

Independent implementation record

✓

Market analysis

So what do you actually do?Attach the review packet to the release artifact and reopen it when the product changes markets, platforms, copied scope, or monetization.

Interactive triage

Which fact pattern looks like yours?

COUNSEL
REVIEW

New platform, familiar interface

Potentially defensible when declarations enable interoperability, implementation is new, and market substitution is limited. Still fact-specific.

So what do you actually do?Use this only to spot escalation triggers. A dashboard cannot decide fair use, but it can stop a risky project from hiding in a backlog.

The bottom line

Six rules worth putting on the wall

Assume protection may exist.

Copy declarations only when needed.

Write new implementation code.

Document necessity and alternatives.

Analyze the actual licensing market.

Escalate same-purpose uses early.

So what do you actually do?Turn these six rules into a release checklist owned jointly by engineering, product, and IP counsel.

This deck is an educational strategy aid, not legal advice. Fair use turns on the specific facts and governing law.

Validation trail

Primary authorities, checked

Google LLC v. Oracle America, Inc., 593 U.S. 1 (2021)
Opinion text, decided April 5, 2021.

17 U.S.C. §102
Copyrightable subject matter and the idea, process, system, and method-of-operation limit.

17 U.S.C. §107
The statutory four-factor fair use test.

Andy Warhol Foundation for the Visual Arts, Inc. v. Goldsmith, 598 U.S. 508 (2023)
Opinion, decided May 18, 2023.

Validation noteCase names, dates, votes, citations, statutory sections, copied-line count, package count, and the post-2021 Warhol caveat were checked against these authorities.