Canada: Copyright And Application Programming Interfaces In Canada

Last Updated: October 12 2015
Article by Victor Krichker, Catherine Lovrics, Paul Horbal and Andrew Ngo

The legal battle between Google and Oracle concerning copyright in the Java programming language framework will not be going to the United States Supreme Court, for now. The US Supreme Court recently refused to hear Google's appeal of a Federal Circuit decision, which found that copyright can exist in parts of the Java Application Programming Interface (API), and confirmed that Google copied portions of Oracle's Java APIs when creating its Android operating system. The case will now make its way back to the lower courts, for consideration of whether Google can avoid infringement by relying on the "fair use" defense under U.S. copyright law.

How might Oracle and Google have fared in Canadian courts? What legal protections can the creator of an API expect in Canada? Only a few Canadian cases have explored the scope of copyright protection for, and the appropriate approach to infringement of computer programs. It is unclear what balance would be struck in Canada between protecting APIs, on the one hand, and leaving ideas and elements from the public domain free for all to draw upon to create APIs in the future.

Are APIs likely to be protected by copyright in Canada?

If Canadian courts had to consider the copyrightability of the Java APIs at issue in the U.S. litigation between Oracle and Google, our courts would probably grant protection to the APIs. The APIs are likely to be considered "computer programs", created using skill and judgment, and therefore original works.

The Canadian Copyright Act explicitly extends protection to "computer programs", a subset of literary works, which are defined as "a set of instructions or statements, expressed, fixed, embodied or stored in any manner, that is to be used directly or indirectly in a computer in order to bring about a specific result". While Canadian courts have not dealt with the threshold issue, it would appear that most APIs would meet the definition of "computer program", being a set of instructions or statements which are to be used when one computer program interfaces with (or "speaks with") another.

An interesting question is whether or not a Canadian court would refuse to grant copyright protection in certain APIs on the basis that the monopoly would be contrary to the fundamental distinction between ideas and expression. For example, in Delrina Corp. v. Triolet Systems Inc., the Ontario Court of Appeal found that, if there is only one or a very limited number of ways to achieve a particular result in a computer program, to hold that such way or ways are protected by copyright could grant a monopoly on the idea or function itself. In that case, the Court accepted that the "merger" doctrine prevalent in US law is a natural corollary of the idea/expression distinction fundamental to Canadian law (although it did not formally adopt the doctrine). The "merger" doctrine holds that the expression of an idea loses copyright eligibility if it is inextricably linked with its underlying idea.

On the other hand, in 2004, in CCH Canadian Ltd. v. Law Society of Upper Canada, the Supreme Court stated that a work is protected by copyright if it is original, meaning it originates from the author's exercise of skill and judgment in the expression of an idea, requiring "intellectual effort". Creativity is not required to make a computer program original, but the program must be more than a mere copy of another work, or a mechanical exercise. It would appear that after CCH, the subsistence of copyright depends only on whether or not the work is original, and the expression involved the exercise of skill and judgment.

Oracle v. Google also raised another question: whether the elements of a copyrighted work can become unprotectable by becoming commonplace – a concept analogous to the "genericization" of trademarks. The U.S. Court did not accept this argument. It is likely that Canadian courts would agree, since generic elements, ideas, and elements from the public domain may be the subject of original expression that results from the exercise of an author's skill and judgment.

What approach might a Canadian court take to determine if copyright in an API had been infringed?

Canadian copyright law has evolved considerably over the past decade, and today it is unclear what approach a Canadian court would take to copyright infringement involving an API. Canadian courts may apply an abstraction-filtration-comparison type test, similar to that prevalent in the US. Alternately, the Court may adopt a holistic and qualitative approach.

It appears probable that, regardless of the approach, a Canadian court would find that exact (or literal) copying of headings and function names amounts to infringement on the basis they are a substantial part of an API. To quote the U.S. Federal Circuit, the author is not "selecting among preordained names and phrases to create its packages" (Oracle v. Google). Headings and function names are the very parts of an API that programmers need and learn, and so that portion of the API would likely be considered a substantial part. What is less clear is whether or not copying the overall architecture of an API (or its structure, sequence, and organization) would amount to infringement. The latter appears more likely to depend on the approach taken to infringement.

In Delrina, the Ontario Court of Appeal discussed the "abstraction-filtration-comparison" method used in the US to determine the protectable expression in the course of determining infringement. The Court agreed that such a general "weeding-out" approach to remove from copyright protection portions that cannot be protected by copyright was "not wrong" (but did not formally adopt the doctrine). The facts in Delrina involved a computer program that the defendant's company had hired the plaintiff's ex-employee to write. This individual had previously written a program for the plaintiff that performed essentially the same functions. The Court found that, to the extent there were similarities between the two programs, such similarities were not eligible for copyright protection because they were necessitated by the functions the program was required to perform.

However, a more recent Supreme Court decision, Cinar Corporation v. Robinson, affirmed that generally Canadian courts should adopt a holistic and qualitative approach to assessing infringement. The Court found that many works do not lend themselves to a "reductive" analysis, and rejected the "abstraction-filtration-comparison" method in relation to the development of a children's show that took inspiration from Daniel Defoe's Robinson Crusoe. The Court found that a piecemeal approach was inappropriate, and non-protectable elements should not be excluded at the outset of the analysis. Elements that were commonplace, generic and in the public domain were not "weeded out" before determining whether or not a substantial part had been copied. The Court found that all relevant aspects – patent, latent, perceptible, intelligible – should be considered. The Court also affirmed that infringement includes colourable imitation, and covers both literal and non-literal copying. Consequently, the alteration of copied features or their integration into a work that is notably different from the original work does not necessarily preclude a claim that a substantial part of a work has been copied. The Court shifted the focus to considering whether the "cumulative effect" of the features copied from the work amount to a substantial part of the author's skill and judgment expressed in his work as a whole. The focus on "effect" of the copied features is new to Canadian law, and it remains to be seen how this test will be applied to the infringement analysis going forward, including in relation to software APIs.

The Cinar decision did not involve computer software, and notably, the Court left the door open for the abstraction-filtration-comparison method being used with respect to software. Further, the Court acknowledged that it may be necessary to go beyond the perspective of the audience (for example, software user), to call upon an expert to put the judge in the shoes of "someone reasonably versed in the relevant technology". Consequently, the approach in Delrina may still be followed in future cases.

If the abstraction-filtration-comparison method is applied, the "structure, sequence, and organization" of the API may be "weeded out" from copyright protection because, for example, the elements could only be expressed, or programmed, in one or a very limited number of ways. A finding of infringement under this test may also depend largely on whether the structure, sequence, and organization of an allegedly infringing API amounts to a "substantial part" of the plaintiff's skill and judgment in creating the infringed computer program. Unfortunately, there is nothing inherent about APIs that suggests that this question can be answered consistently one way or the other. In a simple API, there may be relatively few ways to organize a list of functions, meaning that the API structure would not form a substantial part of the author's use of skill and judgment in creating the API. An alleged infringer might point out known design patterns in the copyright owner's API specification (e.g. "create, read, update and delete") to argue that the author's skill and judgment was mostly expended elsewhere (e.g. in the writing of the implementation). On the other hand, the author of a more complicated API specification might argue that writing the implementation – once the organization of the API specification had been settled – was a largely mechanical exercise. Therefore, a substantial part of the author's skill and judgment must have gone into devising the structure, sequence, and organization of that API.

Conversely, if a holistic and qualitative approach is applied, a court may find infringement based on the "overall architecture" of the API having been copied. The Court may find that copying of the overall architecture is not a reproduction of an abstract idea, but rather copying of the detailed manner in which the ideas are expressed. Applying a holistic test, infringement could be found based on non-literal copying of a combination of features of the API. The court may regard such combination of features as a substantial part of the API, even if they do not form a discrete part of the API, but are abstracted from the API.


As ever, it is difficult to predict how courts will rule on a novel issue. Judgments from foreign courts can have some predictive value, but are not determinative given varying legal frameworks and traditions. In Canada, it is possible that copying original function naming could form the basis for a finding of copyright infringement. However, whether infringement would be found for copying the structure, sequence and organization, or "overall architecture", of an API will likely depend on the specific facts of each case.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on

Click to Login as an existing user or Register so you can print this article.

Victor Krichker
Catherine Lovrics
Paul Horbal
In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:
  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.
  • Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.
    If you do not want us to provide your name and email address you may opt out by clicking here
    If you do not wish to receive any future announcements of products and services offered by Mondaq you may opt out by clicking here

    Terms & Conditions and Privacy Statement (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

    Use of

    You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


    Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

    The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


    Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

    • To allow you to personalize the Mondaq websites you are visiting.
    • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
    • To produce demographic feedback for our information providers who provide information free for your use.

    Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

    Information Collection and Use

    We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

    We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to with “no disclosure” in the subject heading

    Mondaq News Alerts

    In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


    A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

    Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

    Log Files

    We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


    This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

    Surveys & Contests

    From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


    If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


    From time to time Mondaq may send you emails promoting Mondaq services including new services. You may opt out of receiving such emails by clicking below.

    *** If you do not wish to receive any future announcements of services offered by Mondaq you may opt out by clicking here .


    This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to

    Correcting/Updating Personal Information

    If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to

    Notification of Changes

    If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

    How to contact Mondaq

    You can contact us with comments or queries at

    If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at and we will use commercially reasonable efforts to determine and correct the problem promptly.

    By clicking Register you state you have read and agree to our Terms and Conditions