Endpoint is a conference organized by API developers, for API developers. The conference will be held in Amsterdam on September 5, 2014. If you develop APIs for apps, websites or other clients, there’s certainly a session that will interest you.
To give you a feeling of what to expect at the Endpoint conference we’ve talked with Kamyar Mohager, who will be in Amsterdam representing Linkedin. Kamyar will be delivering the opening keynote on September 5 at 9:00 so make sure you don’t miss it.
Please explain what is your current role at Linkedin and how APIs are a part of it.
Kamyar: I’m currently serving as a Senior Partner Engineer on the Developer Relations team at LinkedIn. We work closely with our partners to make sure they successfully integrate with our platform. I lead the the strategic partnership efforts at LinkedIn, which include integrations with Apple OS X and Samsung’s latest Galaxy S5 phone.
I really enjoy these partnerships because we work with high-profile consumer apps/devices with large user bases. Each integration varies in terms of how they leverage our APIs so there’s always a new product to help shape and support. In addition to this, I also spend a significant portion of my time serving as the product owner for our platform framework and the tools we build to support it.
Can you tell us what your presentation at Endpoint 2014 will be about?
Kamyar: I’m really excited to be speaking at Endpoint 2014, especially since this will be the inaugural year. I’ll be covering developer platform best practices in my presentation, focusing on such concepts as API Design, Platform Strategy, and Monitoring/Operability. I’ll showcase some of the lessons learned at LinkedIn as well as from other platforms that have been successful in their endeavors.
Can you share anything about future LinkedIn API features?
Kamyar: Our focus most recently has been on providing an even more secure developer experience. We’re extending our current OAuth 2.0 implementation to support header-based authentication. We will continue to support query-based authentication (passing the user access token as a query parameter), but header-based authentication is our recommended means of making authenticated calls going forward.
In a few weeks all of our APIs will start returning secure URLs over HTTPS. This applies to URLs pointing at LinkedIn sites, such as our APIs, desktop site, and CDN. Of course this won’t include any URLs pointing to non-LinkedIn sites, such as articles posted via our Share API.