An API is the gateway of FDI software: partners integrate through it, and rivals can also study its structure to build competing compatible products. The core legal question is not ‘is an API copyrighted’ but which parts are protected creative expression and which parts are mere ideas and functional specifications the law does not monopolise.
The protection boundary around an API
- Programs are protected as expression — Article 22 of the IP Law: computer programs are protected as literary works, covering source code and concrete expressive structure, not the ideas, principles or methods behind them.
- API specifications are mostly functional — endpoint names, parameters and data formats dictated by technical compatibility usually lack minimal originality; copying them to achieve compatibility is hard to frame as copying a work.
- What can be protected — creatively written API documentation, examples, and above all the server-side implementation code are fully protected works; independently reimplementing from a spec is different from stealing source code.
- Layers beyond copyright — API terms bind integration partners contractually; access keys, rate limits and trade-secret protection guard the non-public implementation.
Designing an API protection strategy for FDI software
- Tier the assets: server code and creative documentation — copyright and registration; public specifications — terms of use and access control.
- Issue clear API terms for partners: integration scope, a bar on reverse engineering non-public parts, and key revocation on breach.
- Do not rely on copyright to block compatibility: if the goal is functional exclusivity, assess patent protection for the technical solution instead of expecting API copyright to do it.
An API exists so others can connect — that is its business value. The right strategy for FDI software firms is not locking the API with a copyright that does not cover functional specs, but layering: copyright for code and docs, contracts for partners, and technical controls for access.
Frequently asked questions
Is a software API protected by copyright?
In part: implementation code and creative API documentation are protected under Article 22 of the IP Law; purely functional compatibility specifications are not.
A rival implemented our API — can we sue?
A copyright claim needs copying of source code or creative documentation; independent implementation for compatibility with a public spec is usually not infringement.
What should we watch when designing an API?
Layer protection: register copyright in code and docs, bind partners through API terms, and use technical access controls instead of relying on copyright alone.
This article has been quality-reviewed by the FLAW AI Legal Council