Action camera maker GoPro has shuttered its developer program. A statement posted on the developer program website reads, "GoPro has discontinued the Developer Program. We are grateful to the GoPro Developer Community for your interest in the program." The program was launched in April 2016.
Developer Relations Articles
The following is a list of ProgrammableWeb articles that matched your search term. On an nearly 24/7 basis, ProgrammableWeb publishes new articles ranging from news to opinion to tutorials for both developers and API providers. All of our articles are categorized in such a way that you can find your way to related articles, APIs, SDKs, Libraries, Frameworks, Tutorials and Sample Source Code. If you have an interest in contributing any of the aforementioned content to ProgrammableWeb, be sure to read our guidelines for such contributions.
Edmunds is ending open access to its suite of APIs. The company recently announced that open API keys will soon be disabled (February 15, 2018). Moving forward, the company will work with a select group of strategic partners to fulfill its new API strategy. The company will not offer paid access.
How to Create a Quick and Dirty Example of The Proposed Standard for In-Band API Service Warnings API University
As a best practice, API providers often go to a lot of trouble to notify developers of upcoming disruptions or changes to their APIs. All of this happens out-of-band like in a ChangeLog or an email. But how about the idea of in-band notifications, especially when developers are impossible to reach?
An API marketplace is more than an API developer portal where potential consumers discover and subscribe to APIs. It provides the means for a diverse group of people to design and publish APIs, along with tools, documentation, and incentives to participate, such as monetization and evangelism.
Deciding what metrics matter depends on the overall strategy goals and business model that aligns with your APIs. This is why defining the business model was one of the first steps in your decision series. Now we need to make sure our evaluation framework matches back up to what we set out to do.
Our series on getting the most ROI out of your API has looked at the business and technical decisions to make when building your API strategy. We've also made decisions around how to engage with developers and build a developer community. A key aspect to this involves creating a developer portal.
Now that your API has been published and external developers are beginning to consume it, our focus shifts again towards a balance between business and technical issues. In this part of the series we take a look at how a business can leverage the technical API to grow a developer community?
Congratulations, your API is now production ready. Next you will need to provide documentation to consumers so they can integrate the data and services you have exposed via API quickly. This part covers API documentation including the role of API specs and a number of available tools.
Lego is not the first thing product owners would think of when looking for a model onboarding process. But they should. At least that is Cristiano Betta’s theory over at his blog, who will tell you the lessons you can learn for your API from the Lego onboarding experience.