About
GraphQL Day is a one-day community event hosted at FOST (Future of Software Technologies, think federation of conferences!).
It is an opportunity to connect with other API ecosystems, meet new and seasoned GraphQL users, educate about GraphQL, share best practices, and have fun!
The event is open to everyone — whether you run GraphQL in production or are evaluating it for your next project.
Schedule
All times in Eastern Daylight Time (EDT, UTC−4)
Built to Evolve: 13 Years of GraphQL
In 2015, we promised GraphQL would be “easy to learn and use.” Ten years, and hundreds of billions of daily API calls later, we’ve learned that not all our hopes and promises turned out to be true.
Teach yourself GraphQL in 2026: an anti-blueprint
After eleven years as an open source technology, GraphQL has never had a more favorable learning curve. Clearer mental models, better educational materials, and a deeper collective understanding of best practices have transformed the “wild west” of 2015 to a much more manageable landscape today.
GraphQL as the Execution Layer for AI Agents
Closing the Loop: How GraphQL Gives Coding Agents Eyes on What Actually Matters
Coding agents are reshaping how we build software. Implementing features, refactoring systems, and shipping changes at a pace unthinkable 6 months ago. But to be successful with agents you need the right feedback loop. One that guides your agent to success, not into the spiral of death.
Voice AI for the Patients AI Left Behind: How GraphQL Federation Became Our Trust Layer
Healthcare AI has a coverage problem. The 78-year-old Spanish-speaking grandmother with early dementia isn't downloading an app, typing into a chatbot, or navigating a patient portal. But she can answer a phone call, and she can have a conversation, if the system on the other end knows how to have one with her.

David Sarabia
ClinicaMind, CEO

David Sarabia
ClinicaMind, CEO
Server Assisted Accessibility (Part 2): Enforcing Consistent Semantics via GraphQL + CI
In my apidays Paris session last year, I introduced a “shift left” pattern for accessibility: attach accessibility metadata to GraphQL fields using lightweight directives, expose it through code generation, and let Android (Jetpack Compose), iOS (SwiftUI), and web clients map it into native accessibility semantics for consistent defaults.
































