Credly API Terms of Service

Revised: February, 2021
Version 1.2

These API Terms of Service (the "API Terms") describe your rights and responsibilities when accessing Credly’s publicly available application programming interfaces (the "Credly APIs") and related API documentation. By accessing or using the Credly APIs, you are agreeing to the terms below for the entire duration of your use of the Credly APIs (the “Duration”). Please read them carefully. We are grateful you're here.

1. About Us and These API Terms of Use

You agree that by developing on the Credly platform, you are agreeing to enter into a legally binding contract with Credly Inc., A Delaware corporation with offices at 368 9th Ave, 6th Floor, New York, NY 10001 (“we,” “us,” “our,” and “Credly”).

We use the term “Designated Countries” to refer to countries in the European Union (EU), European Economic Area (EEA) as well as Switzerland and the United Kingdom.

By obtaining Access Tokens to the Credly APIs or using the Credly APIs, you acknowledge that you currently have an organization account on the Credly System in good standing and have understood and agree to be bound by these Credly API Terms of Use (the “Terms”).

If you are developing on the Credly platform on behalf of a company or other entity, you represent and warrant that you have full legal authority to access the API on behalf of that entity and to bind it to these API Terms. If you are not authorized, you may not accept the Terms or access the API for someone else and you may not access the Credly APIs.

2. Earners and Digital Credentials

The Credly platform helps the world speak a common language about people’s knowledge, skills, and abilities by offering an end-to-end solution for creating, issuing and managing digital credentials. A “Credential” means a digital representation of an achievement issued to an Earner by an Issuer. Credentials include an image and metadata describing the achievement and may include supporting evidence and related information. An “Earner” is an individual or organization who is issued a Credential by Issuer. 

3. Developer Documentation

Your use of the Credly APIs and display of Credly content in your software application, website, or product or service you offer (collectively, your “Application”) must comply with the technical documentation, usage guidelines, call volume limits, and other documentation maintained at the Developer Site or otherwise made available to you (together, the “Developer Documentation”, which are expressly incorporated into these API Terms by reference).  “Content” means any data or content from our Services or accessed via the APIs.  “Services” means Credly.com, Youracclaim.com, Credly-branded applications and services, and other Credly-related sites, apps, communications and services and technology related thereto.

In the event of any conflict between the Developer Documentation and the API Terms, the API Terms shall control. 

4. Access Tokens

To begin using the APIs, you must first obtain Access Tokens from Credly. “Access Tokens” means the necessary security keys, secrets, tokens, and other credentials to access the applicable APIs. The Access Tokens enable us to associate your API activity with your Application and the Earners using it. All activities that occur using your Access Tokens are your responsibility. Keep your Access Tokens secret. You may not sell, share, transfer, or sublicense them to any other party other than your employees or independent contractors in accordance with Section [##] below. Do not try to circumvent the Access Tokens and do not require your users to obtain their own Access Tokens to use your Application (for example, in an attempt to circumvent call limits).

You agree that Credly may use, store, and share information submitted by you to Credly in connection with your Application to contact you, for attribution purposes, handling inquiries from Earners or potential Earners about your Application, for other purposes under these API Terms (for example, we may email you with updates regarding the developer program), and as otherwise permitted in our Privacy Policy.   

5. Credly’s Sandbox Environment

For testing of integrations, you may only use Credly’s Sandbox Environment. You may not use the Credly production environment for any kind of testing, nor may you introduce any fictitious or “dummy” data into the Credly production environment. 

6. API License

Subject to your compliance with these API Terms, we grant you a limited, non-exclusive, non-sublicensable (except to independent contractors so they may host, develop, test, operate, modify or support your Application in accordance with Section 7), non-transferable, non-assignable license under Credly’s intellectual property rights during the Duration (a) to use the APIs to develop, test, operate and support your Application; (b) to distribute or allow access to your integration of the APIs within your Application to end users of your Application; and (c) to display the Content accessed through the APIs within your Application.

You have no right to distribute or allow access to the stand-alone APIs.

7. Use of APIs and Credly Content

a. General Restrictions. In addition to the other terms and conditions in these API Terms, except as expressly set forth herein, you agree not to do the following:
 
i. Use APIs in a way that could impair, harm or damage Credly, the Credly APIs, any Credly online service (“Credly Offerings”), or any third-party’s use of the Credly APIs or any Credly Offerings; 
 
ii. Use the APIs to disrupt, interfere with, or attempt to gain unauthorized access to services, servers, devices, or networks connected to or which can be accessed via the APIs; 
 
iii. Use the APIs, or any information accessed or obtained using the APIs, for the purpose of migrating Earners or other Credly customers away from a Credly Offering, except in connection with use of the APIs by your Application or unless expressly permitted by Credly pursuant to a duly executed written agreement;
 
iv. Use an unreasonable amount of bandwidth, or adversely impact the stability of the APIs or the behavior of other apps using the APIs;
 
v. Attempt to circumvent the limitations Credly sets on your use of the APIs. Credly sets and enforces limits on your use of the APIs (e.g., limiting the number of API requests that you may make or the number of users you may serve), in its sole discretion;
 
vi. Use the APIs, or any data obtained using the APIs, to conduct performance testing of a Credly Offering unless expressly permitted by Credly pursuant to a duly executed written agreement;
 
vii. Use the APIs, or any data obtained using the APIs, to identify, exploit or publicly disclose any potential security vulnerabilities;
 
viii. Request, use or make available any Content outside any permissions expressly granted by Earners in connection with using your Application;
 
ix. Falsify or alter any unique referral identifier in, or assigned to an Application, or otherwise obscure or alter the source of queries coming from an Application to hide a violation of this agreement;
 
x. Use any API in any manner that, as determined by Credly in its reasonable discretion, constitutes abusive usage;
 
xi. Attempt to decode, circumvent, re-identify, de-anonymize, unscramble, unencrypt, or reverse hash, or reverse-engineer Content that is provided to you.
 
xii. Implement features or business practices, or use the APIs or Content in a way that may harm the professional reputation or relationships of Earner;
 
xiii. Disclose or provide the APIs or Access Tokens to any person or entity other than to your employees or independent contractors, provided (1) such employees or independent contractors enter into an agreement with you at least as protective of Credly’s rights as this Agreement, and (2) you hereby agree to be responsible for, and liable to Credly for, any breaches of such agreements by such employees or independent contractors;
 
xiv. Request or publish information impersonating an Earner or Issuer, misrepresent any Earner, Issuer or other third party in requesting information or allow any third party, including other Earners, to see information obtained from another Earner’s network or through another Earner’s view of the Services or Content;  
 
xv. Use the APIs or Content for any illegal purposes, or in any manner which would violate these API Terms, or breach any laws or regulations regarding privacy or data protection, or violate the rights of third parties or expose Credly or any Issuer or Earner to legal liability;
 
xvi. Remove any legal, copyright, trademark or other proprietary rights notices contained in or on materials you receive or access pursuant to these API Terms, including, but not limited to, the APIs, the Developer Documentation, and the Content;
 
xvii. Obtain, display or use more Content than is minimally required by the Application;
 
xviii. Sell, lease, share (with the exception of making the Content available to users through the Application), transfer, sublicense or otherwise make available any Content, directly or indirectly, to any third party (e.g. you may not sell access to an aggregated collection of Earner profiles or the most relevant Earners for a position), including, but not limited to, any data broker, ad network, ad exchange, or other advertising monetization-related party;
 
xix. Process or Use Content to discriminate or encourage discrimination against people based on personal attributes including race, ethnicity, color, national origin, religion, age, sex, sexual orientation, gender identity, family status, disability, medical or genetic condition, or any other categories prohibited by applicable law, regulation, or Credly policy;
 
xx. Process or use Content to perform, facilitate, or provide tools for surveillance. Surveillance includes the Processing of Content about people, groups, or events for law enforcement or national security purposes;
 
xxi. Change your Application’s core functionality or data Processing so that your users would view it as an unfamiliar or different Application, or materially changing the scope of Processing or Use of previously collected Content, unless expressly agreed with Credly pursuant to a written agreement;
 
xxii. Use the Content for any other purpose other than to allow your users to use the Content in your Application;
 
xxiii. Unless otherwise permitted by Credly in writing, use any Content in any advertisements or for purposes of targeting advertisements specifically to any individual user (whether such advertisements appear in the Application or elsewhere), or to generate mass messages, promotions or offers;
 
xxiv. Interfere with or disrupt the Services or servers or networks connected to the Services, or disobey any requirements, procedures, policies or regulations of networks connected to the Services, or transmit any viruses, worms, defects, Trojan horses, or any items of a destructive nature through your use of any API
 
xxv. Obfuscate or hide your deployment or use of any Credly buttons, sign-in functionality, consent or authorization flows from your users;
 
xxvi. Copy, adapt, reformat, reverse-engineer, disassemble, decompile, decipher, translate or otherwise modify any API, Access Token, Content, Credly Offering or other information or service from Credly, through automated or other means;
 
xxvii. Unless otherwise permitted in writing by Credly, combine any Content with any other Credly content (including content obtained through scraping, crawling, spidering or any other technology or software used to access Credly content). This includes acquiring such Credly content from third parties;
 
xxviii. Attempt to re-identify any de-identified or anonymized data; or
 
xxix. Access, store, display, or facilitate the transfer of any Credly content obtained through the following methods: scraping, crawling, spidering or using any other technology or software to access Credly content outside the APIs (such content, collectively, “Non-Official Content”). This restriction applies (1) whether the Non-Official Content was obtained directly or indirectly through a third party, such as a customer or third party developer, and (2) whether or not the Non-Official Content is stored or displayed in the Application or some other resource, product or service.
 
b. Sharing Content. You may only share Content in compliance with these API Terms, applicable law and regulations, and all other applicable terms and policies, and only in the following circumstances. 
 
i. When required under applicable law or regulation (you must retain proof of the applicable legal or regulatory requirement or request and provide it to us if we ask for it); and
 
ii. With other third parties, when you 1) first contractually prohibit them from using the Content in a way that would violate these API Terms or any other applicable terms or policies (you must retain proof of the contractual prohibition and provide it to us if we ask for it); and 2) you ensure that any such third parties comply with these API Terms and all other applicable terms and policies as if they were in your place, and you are responsible for their acts and omissions, including their noncompliance.
 

8. Storage of Content

a. You must not capture, copy or store any Content or any information expressed by the Content (such as hashed or transformed data), except to the extent permitted by these API Terms. If you are required to keep Content under applicable law or regulation, you must retain proof of the applicable legal or regulatory requirement or request and provide it if we ask for it.
 
b. You must store all Content in a manner which enables you to identify, segregate and selectively delete such Content.  The Content must not be stored in a data repository that would enable any third-party access (other than Service Providers or the Earner to which it relates). 
 
c. If you have received Content in error, you must immediately report this to us, delete that Content, and provide proof of deletion if we ask for it.
 

9. Storage of Tokens. You may store the Application-specific alphanumeric user IDs that we provide to you for identifying users of your Application (“Earner Tokens”) or the authentication tokens that we provide to you when an Earner authenticates your Application to their Credly account (“OAuth Access Tokens”).

10. Caching Content for Performance

a. Solely to improve your Application’s performance, you may cache the Content for up to 30 days from a request for that Content through the APIs before permanent deletion. Unless otherwise set forth in this Section 4 or in any applicable Additional Terms, you do not have any right to store the Content beyond this limited 30-day period.
 
b. You must refresh the Content at least every 30 days.  You must update Content promptly after receiving a request from us or the Earner to do so. You must give Earners an easily accessible and clearly marked way to ask for their Content to be modified or deleted.
 

11. Earner Profile Data

a. You must obtain legally valid consent from an Earner before you may store that Earner's Profile Data (for example, so that an Earner applying for a job at your company can provide you with a copy of their Credly profile).  “Profile Data” means any or all of an Earner’s profile data available through an applicable API, subject to an Earner’s profile visibility and other privacy settings. Profile Data excludes an Earner’s network, network updates, job listings, groups, companies, and any other content. 
 
b. You must immediately delete all Content collected through the APIs about a particular Earner, including the Earner Token and the OAuth Access Token, upon request by that Earner, when the Earner uninstalls your Application or when the Earner closes their account with you.  
 
c. The restrictions of this Section do not apply to data that Earners provide directly to you and that is separately entered or uploaded to you by the user of your Application. 
 

12. Other Deletion. You must immediately delete all Content when: 

a. We terminate your use of the APIs for breach of these API Terms, except when doing so would cause you to violate any law or obligation imposed by a governmental authority; 
 
b. Retaining the Content is no longer necessary for a legitimate business purpose that is consistent with these API Terms and all other applicable terms and policies; 
 
c. You stop operating the product or service through which the Content was acquired;
 
d. required by applicable law or regulations; or
 
e. required by these API Terms. 

 

13. Service Providers. 

a. A “Service Provider” is an entity you use to provide you services in connection with any Content. You will not use a Service Provider in connection with your use or processing of Content unless such Service Provider first agrees in writing to do the following:

i. Use Content solely for you and at your direction in order to provide services you requested in a manner that is consistent with these API Terms, all other applicable terms and policies, and your privacy policy, and for no other individual or entity and for no other purpose, including for the Service Provider’s own purposes; and
 
ii. In the event the Service Provider engages another Service Provider (“Sub-Service Provider”) in order to provide the services requested, ensure the Service Provider requires the Sub-Service Provider in writing to comply with the above requirements.

 

b. Upon our request, you must provide a list of your Service Providers and Sub-Service Providers including up-to-date contact information for each, the types and volume of Content shared, and proof of written agreements with your Service Providers to demonstrate compliance with this Section.

c. We may prohibit your use of any Service Provider or Sub-Service Provider in connection with your use of Content if we believe that (1) they have violated these API Terms or other applicable terms or policies or (2) they are negatively impacting the Credly System, and will provide notice to you if we do. Promptly upon such notice, you must stop using that Service Provider or Sub-Service Provider in connection with your use of Content.

d. We may require that your Service Providers or Sub-Service Providers agree to these API Terms or other applicable terms or policies in order to access Content. 

e. When you cease using a Service Provider or Sub-Service Provider, you must ensure they immediately cease accessing the Credly API and processing Content and promptly delete all Content in their possession or control.

 

14. Your User Agreement and Privacy Policy

a. Your Application must include your own user agreement and privacy policy. Your user agreement and privacy policy must be prominently identified or located where users download or access your Application.  Your privacy practices must meet applicable legal standards and accurately disclose the collection, use, storage and sharing of data.
 
b. You must promptly notify us of any breaches of your user agreement or privacy policy that impact users.  
 
c. Before obtaining information from users, you must obtain their legally valid consent which, at a minimum, shall include: (a) how their data will be used, (b) when it will be collected (e.g., will the Application pull an Earner’s Profile Data more than once); and (c) how a user can withdraw their consent.  The consent must be freely given (in accordance with applicable law) and given by a statement or a clear affirmative action. When a particular Earner’s consent expires, you must obtain that Earner’s consent again in order to continue to collect and store their data.
 

15. Brand Use Guidelines

a. Subject to these API Terms and subject to the Credly Brand Guidelines, available online at https://info.credly.com/trademark-and-brand-use we grant you a limited, non-exclusive, non-assignable, non-sublicensable, and non-transferable license during the Duration to display trade names, trademarks, service marks, logos and domain names that Credly makes available to you (collectively “Brand Features”) within the Application and to accurately promote or advertise your integration of the APIs in your Application.   
b. You agree not to display Credly Brand Features (a) in any way that violates applicable law, including laws regarding libel, slander, obscenity and infringement or (b) in any way that is misleading, implies that your Application is approved, created or endorsed by Credly (or otherwise embellishing your relationship with Credly) or in a way that is otherwise objectionable to Credly in its sole discretion. If you are planning any formal, proactive press outreach, you will submit the content (press release, blog post, etc.) to us for prior written approval (email acceptable), unless expressly allowed in our Branding Guidelines. Any good will in Credly Brand Features resulting from your use will inure solely to Credly.

16. Security Measures

a. Requirement for Security Measures. Your network, operating system and the software of your web servers, databases, and computer systems (collectively, “Systems”) must be properly configured to securely operate your Application and process Content.
 
b. Security Questionnaire. If requested, you must complete Credly’s security questionnaire (which Credly will provide to you).
 
c. Security Breach. You must promptly report any security deficiencies in, or intrusions to, your Systems that you discover (or are reported publicly or to you) to Credly in writing via email to legal@Credly.com or subsequent contact information posted on the Developer Site if such intrusions could reasonably be expected to affect the Content, Credly or its Earners in any way. You will work with Credly to immediately correct any security deficiency, and will immediately disconnect any intrusions or intruders. In the event of any security deficiency or intrusion involving the Application, Credly APIs or Content, you will make no public statements (e.g., press, blogs, social media, bulletin boards, etc.) without prior written and express permission from Credly in each instance.
 

17. Support and Updates

a. We may provide you with support for the Credly APIs in our sole discretion and we may stop providing support to you at any time without notice or liability to you.  We are not obliged to provide any training, support or technical assistance for the Application, the Content, or the APIs directly to your Application users and you agree to communicate to your Application users that you (and not Credly) are responsible for any such support. 
 
b. We may modify or release subsequent versions of the APIs and require that you use those subsequent versions.  Unless we release a new version of the APIs for security or legal reasons, you will have a reasonable amount of notice (as determined by us), to migrate to subsequent versions of the APIs.  You acknowledge that once Credly releases a subsequent version of an API, the prior version of such API may stop working at any time or may no longer work in the same manner. Your continued use of the APIs following a subsequent release will be deemed your acceptance of modifications.
 

18. Independent Development. Each party acknowledges that the other party may be independently creating applications, content and other products or services that may be similar to or competitive with those of the other party and nothing in these API Terms will be construed as restricting or preventing each party from creating and fully exploiting such applications, content and other items, without any obligations to the other party.

 

19. Ownership & Reserved Rights. As between the parties, we own all rights, title, and interest in and to the (a) APIs, and all elements, components, and executables of the APIs, (b) Content; (c) Services; and (d) Our Brand Features (clauses (a)-(d) collectively, the “Credly Materials”), and, subject to the foregoing, you own all rights, title, and interest in and to the Application and Your Brand Features. Except to the limited extent expressly provided in these API Terms, neither party grants, nor shall the other party acquire, any right, title or interest (including any implied license) in or to any property of the first party under these API Terms.  All rights not expressly granted in these API Terms are withheld.

 

20. Feedback. Either party may from time to time elect, in its sole discretion, to provide suggestions, comments, improvements, ideas or other feedback to the other party related to the other party’s products and services (“Feedback”). Feedback is provided on an “as is” basis with no warranties of any kind and the receiving party will have a royalty-free, worldwide, sublicensable, transferable, non-exclusive, perpetual and irrevocable right and license to use Feedback. Each party agrees not to provide Feedback that it knows is subject to any intellectual property claim by a third party or any license terms which would require products or services derived from that Feedback to be licensed to or from, or shared with, any third party.

 

21. Legal Compliance.  You represent and warrant to Credly that: (a) you have the right to use, reproduce, transmit, publicly display, publicly perform, and distribute your Application (excluding Credly Materials); (b) use of your Application by Credly and its Earners in accordance with the Application’s terms of use will not violate the rights of any third party (e.g., copyright, patent, trademark, privacy, publicity or other proprietary right of any person or entity), or any applicable regulation or law, including the Digital Millennium Copyright Act, the laws of any country in which your Application is made available and any applicable export laws; and (c) you will comply with all applicable local, state, federal, and foreign laws, including, without limitation, any laws or regulations relating to privacy and data protection in connection with its performance under these API Terms.

 

22. Compliance with and Amendments to These API Terms. 

a. You must comply with these API Terms in order to use the Credly APIs.  The most current version of these API Terms can be reviewed on the website currently hosted at Youracclaim.com/docs or on any successor URL (the “Developer Site”).
 
b. We reserve the right to modify, supplement, or replace any provisions of these API Terms, effective prospectively upon posting on the Developer Site or otherwise notifying you. For example, we may present a banner on the Developer Site when we have amended these API Terms so that you may access and review the changes prior to your continued use of the APIs and Developer Site. If you do not want to agree to changes to these API Terms, you can terminate these API Terms at any time in accordance with the Terms.
 
23. Severability. If any provision of these API Terms is found to be illegal, void, or unenforceable, the unenforceable provision will be modified so as to render it enforceable to the maximum extent possible in order to effect the intention of the provision; if a term cannot be so modified, it will be severed and the remaining provisions of these API Terms will not be affected in any way.
 

24. Notices and Service of Process. We may notify you via postings on the Developer Site or via the email address associated with your Application or Earner account. Credly accepts service of process at this address: Credly Inc. ATTN: Legal Department, 368 9th Ave, 6th Floor, New York, NY 10001.  Any notices that you provide without compliance with this Section shall have no legal effect.

25. Entire Agreement. These API Terms, including any documents incorporated into these API Terms by reference, constitute the entire agreement between you and Credly regarding the subject matter of these API Terms  and supersedes all prior agreements and understandings, whether written or oral, or whether established by custom, practice, policy or precedent, with respect to the subject matter of these API Terms.

26. No Injunctive Relief. In no event shall you seek or be entitled to rescission, injunctive or other equitable relief, or to enjoin or restrain the operation of the developer platform or any APIs, Content or other material used or displayed through the Credly developer platform.

27. No Third-Party Beneficiaries. There are no third-party beneficiaries under this Agreement.

28. No Assignment or Delegation. You may not, without Credly’s prior written consent, assign or delegate any rights or obligations under these API Terms, including in connection with a change of control. Any purported assignment and delegation shall be ineffective. We may freely assign or delegate all rights and obligations under these API Terms, fully or partially without notice to you.

29. No Partnership. Nothing in these API Terms will be construed as creating a partnership or joint venture of any kind between the parties and neither party will have the authority or power to bind the other party or to contract in the name of or create a liability against the other party in any way or for any purpose.