Have you ever met any complexities with designing REST APIs? I believe yes, because of the set of factors you have to take into account: – consumer needs – number of consumers – application restrictions – future API usage etc. This list might be extended endless.
In my presentation, I would like to dive into some practical cases of how the API could be modelled in different circumstances by applying REST principles and some standards applicable to specific business areas (like TM Forum standards widely used in Telecommunication). Let me emphasize the key points I consider in my presentation: 1. REST API principles and best practices for API development (KISS approach, etc.) 2. TM Forum standards – what is it? How they might be used? 3. Case studies: 3.1. Generic query – GET for everything 3.2. Product Catalog Management API/ ShoppingCart API – one standard API for multiple frontend (DRY principle)
High impact blog posts and eBooks on API business models, and tech advice
Connect with market leading platform creators at our events
Join a helpful community of API practitioners
Can't make it to the event? Signup to the Nordic APIs newsletter for quality content. High impact blog posts on API business models and tech advice.
Nordic APIs will use the information you provide on this form to provide updates and news.
You can change your mind at any time by unsubscribing from any email you receive from us or by contacting us at info@nordicapis.com. We will treat your information with respect. By clicking below, you agree that we process your information per the terms in our Privacy Policy.
We use Mailchimp as our marketing platform. By clicking below to subscribe, you acknowledge that your information will be transferred to Mailchimp for processing. Learn more about Mailchimp's privacy practices.
Become a part of our global community of API practitioners and enthusiasts. Share your insights on the blog, speak at an event or exhibit at our conferences and create new business relationships with decision makers and top influencers responsible for API solutions.
