rst approach at Apiary.io → Oracle • Founder of API consulting Good API • Helped several Fortune 100 companies with their API strategy and execution • Founder and CTO of Superface.ai Zdeněk “Z” Němec superface.ai
the API domain model and language 2. Answering the question “Can this API ful fi ll my use-case?” 3. The need to understand the entire ecosystem and documentation of API vendor in order to integrate even a small functionality 4. Ambiguity of my own product requirements 5. Quality of documentation, outdated API specs 6. Access hurdles, certi fi cation, API provider terms superface.ai
limits, regulations, certi fi cation, SLAs How to connect, API calls, JSONs, API Spec what API o ff ers, what capabilities, what use-cases it carters to superface.ai
often, API docs focus on the technical aspects • The least important one, and the one that changes the most often • API docs are not focusing enough on the product’s capabilities and domain • Business side is usually under-documented Implemenation Product Business superface.ai
Improving the API documentation • Document the business and product aspects in addition to technical reference • SDKs, cURL, Postman collections, examples • Standardization & harmonization • Uni fi ed APIs • “APIs in front of APIs” • Nylas, Hyperswitch, Metapack, Merge superface.ai
non-commodities) NLP-based augmented human operator Employing LLM/AI to assist in the proces of analyzing and integrating API NLP – Natural Language Processing LLM - Large Language Model Self-integrating apps machine-to-machine communication Enabling applications to autonomously discover & connect APIs superface.ai