APIdays Paris 2012
2012-12-03..2012-12-04
Paris, France
[APIdays Paris 2012, apidays Paris 2020, apidays Paris 2021, apidays Paris 2024, apidays Paris 2025]
who it's for
api product managers, backend engineers, integration architects, mobile developers, startup founders, enterprise architects, ux designers
topics
RESTful web services; hypermedia as engine of state; OAuth and OAuth2; API monetization strategies; developer portals and sandboxes; mobile API optimization; service chaining for mobile; api governance and internal-first strategy; RPC to REST migration; media-type versioning; Behavior Trees for APIs; API-driven business models
| title | author | length |
|---|---|---|
| 6 Reasons Why APIs are Reshaping your Business | Cyril Vart | 30m |
Study by faberNovel with Webshell and Novacodex argues APIs become core business strategy, not just tech. Public APIs drive huge scale: Facebook Like reaches… | ||
| Want your API to stick? Try Story Telling | Pat Cappelaere | 21m |
Argues for a concrete REST Level 5 that publishes user goals as activities and returns executable behaviors (behavior trees) so clients can assemble and run… | ||
| Designing RESTful Web Services | David Zuelke | 33m |
Explains why REST’s value is hypermedia as the engine of application state and shows concrete techniques: define a custom media type like… | ||
| SOA and APIs : Fearless Lessons From The Field | Mike Amundsen | 28m |
Three field lessons: pick models and tools that fit how much of the stack is controlled (REST suits loosely controlled, distributed systems; SOAP exposes… | ||
| Strategies to Deliver Contextual API Experience | Paul Fremantle | 27m |
Argues that APIs must adapt to concrete contexts and gives specific patterns and examples: use service chaining or eBay’s Coolio DSL to consolidate mobile… | ||
| What the last 50+ years of modern computing history tell us about future interfaces | Mike Amundsen | 32m |
Survey of fifty years argues that interfaces evolve from linking ideas to run time systems: concrete inventions include the Memex concept to hypermedia… | ||
| The Secret to a Successful API is Internal | Kin Lane | 22m |
Argues that success starts internal-first with inventorying content, owners and business rules, not with a sexy public launch; cites Amazon mandating web… | ||
| Open API Application Contest, Feedback from AXA Bank Experience | Emmanuel Tardieu | 11m |
AXA Bank publishes a public REST API exposing accounts, cards, balances and transaction history and secures access with OAuth while offering a sandbox and… | ||
| Why Open? | Steve Klabnik | 30m |
Argues that APIs break company borders, turning organizations from closed organisms into interoperating assemblages where control shifts and emergent behavior… | ||
| Business models for your API as startup | Kin Lane | 24m |
A practical roadmap for monetizing a startup API: launch with freemium + pay-as-you-go tiers, expose data and storage as billable items, and add developer… | ||
| Creating API for Mobile App | Romain Goyet | 19m |
Recommendation: use HTTP for mobile APIs (HLS and other services run over HTTP), prefer REST, gzip responses, and emit cache-control headers so proxies and… | ||
| RPC to REST : Concrete Case on Payment APIs | Andrei Neculau | 24m |
Klarna moves from XML‑RPC to a hypermedia REST stack to reduce coupling and library churn, shrinking an RPC surface that once neared ~100 methods down to about… | ||
| nothing matches | ||