Private Sector API Codesign PART II – Patrick Amarelis
summary
A national API catalogue (api.gov) standardizes functional and technical descriptions, publishes OpenAPI files into a sandbox and lists ~60 endpoints while FranceConnect records 18 million logins; a public roadmap signals upcoming APIs. An intake Data Pass form: organization, intended use, legal basis, GDPR and security checks collects the exact info providers need. An intermediate page shows an applicant their chances before applying. Security guidance favors OpenID Connect, mutual TLS, strong IAM and auditing, and measured outcomes show ~1 in 10 visitors apply, ~50% complete requests, ~66% of those get access (≈3% granted overall).
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:40Presentation
- 1:30What is the dinum
- 3:48The team
- 7:23Discoverability
- 9:55NonTech
- 12:25Database
- 14:18Accessibility
- 16:56Security
- 20:01Questions
- 27:05API Catalog
related talks
37mOpenID Foundation Strategy
24mIdentification & Authentication for individuals with API
20mAPI data sharing legal practices in the Private Sector
20mEnabling a more integrated government through APIs
01h 01mSharing Health Information Through APIs
21mUnlocking Data Silos Securely: Standards‑Based APIs for Regulated Sectors
18mSecure your Apps and APIs with strong authentication and Adaptive Access.
24mAPI Security in Open Banking Context