WeAreDevelopers LIVE Aug 28, 2020

API Design - Getting Started

Alen Pokos

Stop reinventing data conventions. Treat your API as a stateless enabler. Learn how standardized JSON frameworks build resilient, maintainable backend ecosystems.

Pause
Mute Enter Fullscreen
#1 about 2 min

Defining web APIs and their primary business purposes

Connecting separate application spaces by defining standardized web interfaces that achieve specific business objectives.

#2 about 4 min

Understanding the core concepts of API design

Navigating disagreements around application systems by defining specific business purposes, usability bounds, and technical constraints.

#3 about 5 min

Balancing the client, API, and backend pillars

Ensuring reliable system architecture by keeping the client, API, and backend functioning cohesively without tight technical coupling.

#4 about 4 min

Leveraging the JSON API standard for data structure

Resolving formatting indecisions by utilizing the JSON API standard to rapidly orient relationships and structure documents.

#5 about 4 min

Designing a user registration process with separate endpoints

Removing complex multi-step state tracking from the server by utilizing separate endpoints that shift validation responsibility to client applications.

#6 about 4 min

Evolving listing resource designs for classified platforms

Adapting to new data requirements by keeping items isolated and associating complex seller profiles through explicit resource relationships.

#7 about 2 min

Implementing user-specific filtering and contextual endpoints

Tackling personal data retrieval challenges by providing standard identifier filters and context-aware URL pathways.

#8 about 4 min

Modeling conversations and messages to reduce resource redundancy

Preventing endpoint overload by generalizing seller and buyer identities into reusable conversation participants and implicit resource bindings.

#9 about 1 min

Managing resource types to prevent API maintenance complexities

Avoiding maintenance nightmares caused by overly specific endpoint types by consolidating participants into a generic system entity.

#10 about 2 min

Designing polymorphic resource endpoints for search functionalities

Returning diverse search matches efficiently by leveraging relationship wrappers that identify unique document varieties in a shared endpoint payload.

#11 about 3 min

Establishing core principles for data focus and naming

Escaping theoretical gridlock by standardizing naming layouts and prioritizing clear data provision over flawless architectural designs.

#12 about 1 min

Clarifying the boundary between requirements and API design

Maintaining scope by viewing API engineering as a direct tool to solve core product requirements instead of inventing new expectations.

#13 about 2 min

Tools for API documentation and relationship visualization

Improving system comprehensibility by employing external tools to test requests and map out complete resource relationship diagrams.

#14 about 2 min

Adopting standard error handling and endpoint testing practices

Guaranteeing reliable client responses by integrating standardized semantic status codes and automated postman testing procedures.

#15 about 1 min

Comparing GraphQL capabilities against the JSON API standard

Evaluating technology trade-offs by choosing between the unconstrained flexibility of GraphQL and the rapid delivery of standardized JSON structures.

#16 about 2 min

Choosing readable enum values over numeric backend identifiers

Preventing system confusion by substituting internal database numeric integers with human-readable string values for public usage.

#17 about 2 min

Optimizing performance across JSON methodologies and backend stacks

Overcoming endpoint slowness by recognizing that performance ultimately relies on targeted caching and specialized backend stack optimizations.

#18 about 2 min

Handling data pagination and endpoint versioning strategies

Structuring large datasets for rapid iteration by implementing systematic document pagination and transparent routing patterns.

#19 about 2 min

Applying business rules and permissions within API standards

Imposing correct boundaries by translating standard business terminology into universally recognized HTTP rules and permission constraints.

Matching moments

1:40 min

Summarizing key engineering lessons for platform API development

Anto Anto · WWC 2024

3:32 min

Designing outstanding APIs with simplicity, safety, and evolvability

Anto Anto · WWC 2024

1:02 min

Designing use-case driven APIs and consolidating broad endpoints

Pratim Bhosale Pratim Bhosale · WWC 2025

3:35 min

Evaluating benefits and drawbacks of common API formats

Alexis Yushin Alexis Yushin · WWC 2024

43 sec

Establishing a concrete vision for REST API development

Wekoslav Stefanovski Wekoslav Stefanovski · WWC Europe 2026

2:46 min

Standardizing design rules using the API Stylebook

Michael Jaeger Michael Jaeger · Europe 2026 Virtual

Upcoming sessions on this topic

Open session

World Congress 2026 North America

API = Some REST and HTTP, right? RIGHT?!

Rustam Mehmandarov

Passionate computer scientist

Rustam Mehmandarov
Open session

World Congress 2026 North America

Designing APIs That Survive AI Agents at Scale

Phani Pendurthi

Mastercard, Principal Software Engineer

Phani Pendurthi
Open session

World Congress 2026 North America

AI-Driven API Design

Mike Amundsen

Author, Adviser, Trainer

Mike Amundsen
Open session

World Congress 2026 North America

Optimizing consumption and cost of AI APIs in the enterprise

Derric Gilling

Vice President and General Manager, API Platform

Derric Gilling
Open session

World Congress 2026 North America

Reinventing Testing Practices in the AI Era

Eric Deandrea

Java Champion & Senior Principal Software Engineer, IBM

Eric Deandrea
Open session

World Congress 2026 North America

Building Pragmatic AI: 10 AI Features Your Users Actually Want

Jonathan "J." Tower

.NET Foundation Board | 12x Microsoft MVP | Founder & Consultant

Jonathan "J." Tower