The Curious Engineer

API Evangelist

2016–2017

1,384 posts

← 2013–2015 2018–2019 →

2017 889

December 2017

  1. Api discovery will be about finding companies who do what yu need and api is assumed
  2. Basic api design guidelines are you first step towards api governance
  3. I am now realizing that streamdata io is not just for api providers
  4. Understanding server sent events sse as part of the api landscape
  5. Basic api design guidelines are your first step towards api governance
  6. Api discovery will be about finding companies who do what you need and api is
  7. Javascript object notation json patch
  8. From ci cd to a continous everything ce workflow
  9. No more scraping of banking data in europe according to psd2
  10. Robust public storytelling around your ap process is sign of maturity
  11. Robust public storytelling around your api process is sign of maturity
  12. No more scraping of banking data in europe according to psd2 only apis
  13. From cicd to a continuous everything ce workflow
  14. Definition driven api lifecycle instead of code driven apis
  15. What you can expect as client from soap to grprc
  16. Reducing polling of your existing api using streamdata io
  17. Streaming data from the google sheet json api and streamdata io
  18. What you can expect as a client from soap to grpc
  19. Definitiondriven api lifecycle instead of codedriven api deployment
  20. Cost savings analysis for washington metropolitan area transit authority wmata data apis
  21. Api evangelist and streamdata io
  22. Warming up api providers we are targeting for using streamdata
  23. Warming up api providers we are targeting for using streamdata io with
  24. Cost saving analysis for washington metropolitan area transit authority
  25. Will apis still be relevant
  26. The shifting api landscape
  27. What is more important having an api or having a well designed api
  28. The picture we pain with each api release
  29. Api deployment templates as part of a wider api governance strategy
  30. The picture we paint with the stories we tell around each api version release
  31. Narrowing in on my api governance using api transit to map out psd2
  32. Being able to see your database in xml json and csv
  33. Facebook quietly deprecates the audience insight api used to automate targeting during the election
  34. Narrowing in on my api governance strategy using api transit to map out psd2
  35. Facebook quietly deprecates the audience insight api used to automate
  36. The conversational interface appetite for data via apis
  37. How do you ask questions of data using apis
  38. How to say you might charge for api access in the future without being a dick
  39. How to say you might charge for api access in the future without being a jerk

November 2017

  1. Sql statement pass through using web apis
  2. The average person will never care about apis until it does something meaningful
  3. Licensing over dc transit data
  4. Troubling terms of service changes from washington metropolitan area transit
  5. The average person will never care about apis until it does something
  6. Sorry your api effort falls a little short of the apis I cover
  7. Asyncapi is a specification format for message driven apis
  8. Api deployment is about publishing them wherever they are needed
  9. Sorry your api effort falls a little short for the apis i cover
  10. Making your api pricing page accessible to everyone
  11. The openapi driven mock api server from stripe
  12. Getting a handle on our database schema using apis
  13. The openapipowered mock api server from stripe
  14. Multi region apis using aws api gateway
  15. Hints of banking api regulations from cfpb with consumer authorized financial data sharing and aggregation rules
  16. Making sure you operate in the cloud marketplaces as an api service provider
  17. The defensive database administrator and the eager blockchain believer
  18. When you believe everything in tech is new and nothing repeats itself
  19. Day 2638 apis are dumb
  20. Generating operational revenue from public data access using api management
  21. The many meanings of do not make the same mistake as twitter did with their api
  22. Api management is about awareness and control over our digital resources
  23. We love what you do in the api space now do it our way
  24. My base yaml for starter api plans
  25. We love what you do in the api space but could you do it our way
  26. The many meanings of do not make the same mistake as twitter did with their
  27. My basic yaml for starter api plans
  28. The three stripe openapi vendor extensions
  29. The information you get when allowing developers to sing up for api using github
  30. You thinking i mean rest when say apis is about your limited views not mine
  31. Stripe elements and how we organize our api embeddables
  32. You thinking i mean rest when i say api is about your limited views not mine
  33. Three stripe openapi vendor extensions
  34. The information you get when allowing developers to sign up for an api using
  35. Form posts as gateway for showing people they can program the web using apis
  36. Deploy low hanging fruit rogue api portals for those who are behind the curve
  37. Headless cms and api evolution beyond wordpress
  38. Twitter finally begins to monetize their apis
  39. Headless cms and the api evolution beyond wordpress
  40. The seo benefits of publishing your api operations to github
  41. Glitch is where you will learn the essential human side of operating your api
  42. Provide me with api discovery using an openapi diff
  43. Added a simple bulk api for my human services data api
  44. I added a simple bulk api for my human services data api
  45. Could i please get an api discovery tool that evaluates an openapi diff
  46. I added a taxonomy api to support the human services data api hsda
  47. Stripes openapi is available on github in version 30
  48. Locking up any taxonomy is short sighted in todays online environment
  49. I finally have a weekly email newsletter roundup of api evangelist posts
  50. Locking up any open data taxonomy is short sighted in todays online
  51. I can keep evangelizing the same api stories for the next decade
  52. Admitting there is so much i do not know makes me better at apis
  53. Are people ready for an online api driven world that is progammable
  54. You can lead a horse to water but you cannot make them drink the api edition
  55. I can keep evangelizing the same api stories for the next decade in government
  56. Are people ready for an online apidriven world that is programmable
  57. Admitting there is so much i do not understand makes be better at apis
  58. The impact of api management on api security
  59. Apis that use apis to manage my apis
  60. Learning to play nicely with others using apis
  61. The open web application security project owasp and api security
  62. Using apis to manage my apis
  63. Apis and other ways to service up machine learning models
  64. The api evangelist api security industry guide
  65. I appreciate this api walk through from fannie mae but give me the api
  66. Additional call pricing info are the press relief valves for api plans
  67. I appreciate this api walk through from fannie mae but just give me the api
  68. Apis and other ways of serving up machine learning models
  69. Additional call pricing info are the pressure relief valves for api plans
  70. When we are told that api security investments will affect profitability
  71. Hiding apis in plain sight
  72. Postman as a live coding environment in presentations at apistrat
  73. Developing your talent pool in your api platform community
  74. Developing a talent pool within your api community
  75. A simple api using aws rds lambda and api gateway
  76. Api security beginning to outweigh my vendor lock in concerns
  77. An example of how every api provider should be using openapi out of the slack platform
  78. An example of how every api provider should be using openapi out of the slack
  79. I like the scope of the aws sdk for javascript

October 2017

  1. My response on the department of veterans affairs rfi for the lighthouse api management platform
  2. My response on the department of veterans affairs va rfi for the lighthouse
  3. We are all using apis
  4. I am talking about jekyll as a hypermedia client at apistrat in portland next week
  5. Helping business users get over perceived technical gaps when it comes to api design
  6. A suite of human services api definitions using openapi
  7. I am talking about jekyll as a hypermedia client at apistrat in portland or
  8. Helping business users get over perceived technical gaps when it comes to api
  9. Some new api evangelist art
  10. The api portal outline for a project i am working on
  11. Aws api gateway export in openapi and postman
  12. Your api road map helps others tell their story about your api
  13. Your api road map helps others tell stories about your api
  14. Aws api gateway export in openapi and postman formats
  15. Apis reduce everything to a transaction
  16. Budget api management using github
  17. A simple api with aws dynamodb lambda and api gateway
  18. Api monetization framework introduced by aws marketplace
  19. Api monetization framework as introduced by aws marketplace
  20. Api management dashboard the provider view
  21. Sell your api gateway api through the aws marketplace
  22. Api manageent dashboard the consumer view
  23. Api developer account usage basics
  24. Api developer account basics
  25. Selling your aws api gateway driven api through the aws marketplace
  26. Api management dashboard the consumer view
  27. The tractor beam of the database in an api world
  28. Adding ping events to my webhooks and api research
  29. Using apis to enrich the data you have in spreadsheets
  30. Importing openapi definition to create api with aws gateway
  31. Importing openapi definition to create an api with aws api gateway
  32. Most api developers will not care as much as you do
  33. Api design maturity at capital one
  34. Adwords api release and sunset schedule for 2018
  35. Operating your api portal using github
  36. The basics of api management
  37. Bots voice and conversational apis are your next generation of api clients
  38. Air an asthma api
  39. Everything is headless in an api world
  40. Obfuscating the evolving code behind my api
  41. Provide an open source database and api and then sell the data
  42. Their security practices are questionable but their communication is unacceptable
  43. A grpc meetup kit
  44. The api coaches at capital one
  45. Their security practices are questionable but their communication is
  46. The grpc meetup kit
  47. Provide an open source threat information database and api then sell premium
  48. Explore download api and share data
  49. Connecting service level agreement to api monitoring
  50. Algorithmic observability should work like machine readable food labels
  51. Offering a guest blogger program to create unique content
  52. Connecting service level agreements to api monitoring
  53. A guest blogger program to create unique content for your api
  54. Treating your apis like they are infrastructure
  55. Api governance in the capital one devexchange
  56. Publishing your api road map using trello
  57. Communicating sections of your api documentation
  58. Learning about api governance from capital one devexchange
  59. Communication strategy filler using sections of your api documentation
  60. Publish share monetize machine learning apis
  61. Thinking about why we rate limit our apis
  62. The api management landscape looks different than i anticipated
  63. A couple more questions for the equifax ceo about their breach
  64. The api management landscape has shifted more than i anticipated
  65. Teaching my client three approaches to modular ui design using their apis
  66. How api evangelist works
  67. Show that api call behind that dashboard visualization
  68. Big data is not abut access using web apis
  69. Show the api call behind each dashboard visualization
  70. Big data is not about access using web apis
  71. Apis used to give access to resources that were out of our reach
  72. Api providers should provide observability into government developer accounts
  73. Letting go in an api world is hard to do
  74. Sharing top sections from your api documentation as part of your communications strategy
  75. Sharing top sections from your api documentation as part of your
  76. Apis used to give us access to resources that were out of our reach
  77. Clearly designate api bot automation accounts
  78. Looking at the 37 apached data projects
  79. Temporal logic of actions for apis
  80. Database to database then api instead of directly to api
  81. Looking at the 37 apache data projects
  82. The waves of api driven bots invading our shores
  83. The ca acquisition of runscope
  84. Learning about api design with resources that matter to you
  85. Open api definitions for entire schema org vocabulary dont reinvent wheel
  86. Openapi definitions for entire schema org vocabulary do not reinvent wheel

September 2017

  1. 2017 the api stack for disrupting the world
  2. Developing an ability to repeat the same api stories over and over you are going to need it
  3. Tyk is conducting api surgery meetups
  4. Api design industry guide graphql a query language for apis
  5. The api stack for disrupting the world
  6. Developing the ability to repeat the same api stories over and over
  7. Api design industry guide grpc open source rpc framework
  8. How do we help folks understand that apis are a journey
  9. Api design industry guide the restlet platform story
  10. Apistrat and the openapi initiative
  11. Moving beyond just distributed api scale towards federated api scale
  12. Api design industry guide application level profile semantics alps
  13. A reminder to always have a plan b for our api related github infrastructure
  14. The value of api driven events
  15. Caching for your api is easier than you think and something you should invest in
  16. Thinking beyond just distributed api scale towards federated api scale
  17. Caching for your api is easier than you think and something you should invest
  18. Api design industry guide api stylebook
  19. Keeping the web layer in kafka with the rest proxy
  20. Why does aws charge by usage and other apis still use plans
  21. Apis arent just about mobile make sure you are considering the bigger picture
  22. Concerns around working with api evangelist at bigcos
  23. Keeping the web api layer in kafka with a rest proxy
  24. Concerns around working with the api evangelist at large organizations
  25. Apis are not just about mobile make sure you are considering the bigger picture
  26. Latest copy of the api evangelist api design industry guide
  27. Considering the future of the openapi initiative
  28. Data streaming in the api landscape
  29. Talking with more federal agencies about api micro consulting
  30. Embeddable api integrations for non developers with zapier
  31. Providing embeddable api integrations for nondevelopers with zapier
  32. Not everyone needs api scale some just need api
  33. I am a professional in my industry where should i begin with apis
  34. That point where api session management becomes api surveillance
  35. The concept of api management has expanded so much the concept should be retired
  36. I am not a card carrying restafarian i just believe in the web
  37. Getting beyond openapi being about api documentation
  38. The concept of api management has expanded so much the concept should be
  39. That point where api session management become api surveillance
  40. Jekyll as a hypermedia client
  41. Looking to 2024 what do apis look like
  42. What were the main api developments in 2017
  43. What are the unsolvd problems in the api space
  44. What are the unsolved problems in the api space
  45. Using jekyll as a hypermedia client
  46. What apis excite you and fuels my research and writing
  47. Who are the most influential people and companies to keep an eye on in api space
  48. What is the biggest challenge for big companies doing apis
  49. What has been the biggest change in the api industry since i started api evangelist
  50. Who are the most influential people and companies to keep an eye on in api
  51. What has been the biggest change in the industry since i started api
  52. What apis excite me and fuels my research and writing
  53. Why did we need the api evangelist
  54. What is the role of an influencer in the api industry
  55. Why was my week of rants so well received
  56. What it was about web apis that first captured my attention
  57. Why was my week of api rants so well received
  58. Regulations creeping in on ai ml cognitive and other fronts
  59. Sensibly thinking about where technology ends and the human part begins with apis
  60. I do not fear ai i fear the people doing ai
  61. I will see you at apistrat in portland in november
  62. Sensibly thinking about where technology ends and the human part begins with
  63. I will see you at apistrat in portland this november
  64. Using 3rd party apis to break you out of your enterprise bubble
  65. Lost in api transit
  66. A sample openapi 30 file to get started
  67. Kubernetes json schema extracted from openapi
  68. Versioneye sdk security notifications
  69. Webhook delivery headers from github api
  70. Exporting definitions for all things apis including bots
  71. Openapi 30 tooling discovery on github and social media
  72. My favorite part of openapi 30 is the components object
  73. The us postal services wakes up to the api management opportunity in new audit
  74. The us postal service wakes up to the api management opportunity in new audit
  75. Machine readable definitions for all things api including your bots
  76. Always being prepared for an api future that may never come
  77. Api education is needed but rarely prioritized in current environment
  78. Making sure definitions in openapi are robust for use in schema validation
  79. Version 1 2 of human services data api
  80. Version 1 2 draft of the human services data api
  81. Api education is needed but rarely prioritized in the current environment
  82. When i see the landscape of api tooling i see future of technical debt
  83. I wish i had time to tell that story
  84. Responding to a webhook
  85. Cloud marketplace becoming the new wholesale api discovery platform
  86. When i look at the landscape of api services tooling i see the future of
  87. I wish i had time to tell that api story
  88. Automatically generating openapi from a yaml dataset using jekyll
  89. Why i like a service mindset over resource focus when it comes to apis
  90. All federal government public apis should begin with a github repo
  91. An openapi contract for the freedom of information
  92. Why i like a service mindset over a resource focus when it comes to apis
  93. All federal government public api projects should begin with a github repo
  94. When to build or depend on an api service provider
  95. Github oauth applications as a blueprint
  96. Azure matching aws with service storytelling
  97. Keeping things one dimensional to form api to spreadsheet in one step
  98. Keeping things one dimensional to go from api to spreadsheet in one step
  99. Azure matching aws when it comes to serverless storytelling
  100. Just waiting the graphql assault out
  101. A new minimumviable documentation jekyll template for apis
  102. Api evangelist is a performance
  103. Acknowledging the good in the api space
  104. A new minimum viable documentationmvd jekyll template for apis
  105. The why of the unhinged decoupled api evangelist rant week
  106. The fact that you dont know who i am shows you live in a silo
  107. You think you are so smart you didnt do any due diligence before launching your api
  108. You have no api imagation creativity or sensibility
  109. You think you are so smart you did not conduct any due diligence before launching
  110. You have no api imagination creativity or sensibility
  111. The why and end of the unhinged decoupled api evangelist rant week
  112. The fact that you do not know who i am shows you live in a silo

August 2017

  1. Your lack of investment in api education will be the end of your api service
  2. Admit you do not respect your api consumers and end users
  3. The api space is in the tractor beam of the cloud giants now
  4. Apis will just get more unreliable as funding becomes more volatile
  5. Admit it you do not respect your api consumers and end users
  6. Your apis are an invasive species
  7. You like what i do as api evangelist sure ill do more work for free
  8. Sorry the stock options for your api startup do me more harm than good
  9. I realize that is a hit on your api budget but that is my rent for this month
  10. Holding little guys more accountable than you do vcs and bigcos
  11. You like what i do as the api evangelist sure i will do more work for free
  12. I realize that this is a hit on your api budget but it is my rent for this
  13. Holding little guys more accountable than we do vcs and bigcos
  14. Your microservices effort will fail just like your api and soa initiatives
  15. The reasons for your api security breach you did nothing
  16. Extract as much value as you can from your api community and give nothing back
  17. The reason your api sucks is ther are no women and people of color on your team
  18. The reason your api sucks is there are no women and people of color on your
  19. The reason for your api security breach you did nothing
  20. Your internal dysfunction is not my api problem
  21. Api rant vs api research
  22. Disaster api rate limits
  23. This weeks troubling api patent
  24. Disaster api rate limit considerations
  25. Api rants vs api research
  26. County level marijuana regulation in california using apis
  27. Looking at facebook blueprint as i study api training programs
  28. Considering how machine learning apis might violate privacy and security
  29. Thank you tony
  30. The first question when starting an api is always should we be doing this
  31. Making sense of api activity with webhook events
  32. Api foraging and wildcraft
  33. Api deployment comes in many shapes and sizes
  34. Http status codes and the politics of apis
  35. The patent application information retrieval bulk data api
  36. Testing out the concept of api transit instead of api lifecycle
  37. Why arent there more api focus agencies
  38. Where are all the api focused agencies
  39. The 85 stops along the api lifecycle i track on
  40. Wildcard webhook events
  41. The importance of api stories
  42. Api kindergarten
  43. The 85 stops along the api lifecycle that i track on
  44. Api kindergarten for business and it leaders
  45. Which platforms have control over the conversations around their bots
  46. Elastic search security apis
  47. Where to begin with webhooks for the human services data api
  48. Addressing bulk api operations as separate set of services
  49. Which platforms have control over the conversation around their bots
  50. The elasticsearch security apis
  51. Some microservice thoughts around my human services api work
  52. Decoupling the business of my human services microservice
  53. Platform qa responsibility
  54. Investing time to learn api best practices so you do not reinvent the wheel
  55. Investing the time to learn api best practices so you do not reinvent the
  56. Api platform faq and qa responsibility
  57. Link relation types for apis
  58. About api data gov
  59. Embeddable api tooling discovery with json home
  60. A hack day event to help the link sf app speak human services data specification
  61. A hack day event to help the linksf app speak human services data
  62. Image logging with amazon s3 api
  63. Patent number 9325732 computer security threat sharing
  64. My focus on public apis applies internally as well
  65. Observability in botnet takedown by government on private infrastructure
  66. My focus on public apis also applies internally
  67. Continous integration and deployment for government procurement
  68. An open source api security intelligence gathering processing and distribution framework
  69. Open sourcing your api like version eye
  70. A fresh look at the embeddable tools built on the twitter api
  71. Continuous integration and deployment for government procurement
  72. An open source api security intelligence gathering processing and
  73. Patent web of trust management in a distributed system
  74. Http as substrate
  75. Api message integry with json web token jwt
  76. Reducing developers to a transaction with apis microservices serverless devops and the blockchain
  77. My url shortner is just an api with postman as my client
  78. Reducing developers to a transaction with apis microservices serverless
  79. Patent 9397835 web of trust management in a distributed system
  80. My url shortener is just an api with postman as my client
  81. Http as a substrate
  82. Api message integrity with json web token jwt
  83. The subtle ways in which power asserts itself in face of api engagements
  84. Slow moving ransomware is the new business model
  85. Api industry standards negotiation by media type
  86. Providing code citations in machine learning apis
  87. Slow moving ransomware as the new business model
  88. When you see api rate limiting as security
  89. Including api dependencies within api definition
  90. The words we use to describe our api technology
  91. Understanding the words we use to describe machine learning apis
  92. Including api dependencies within your api definition
  93. Plugin infrastructure for every stop along the api lifecycle
  94. When describing your machine learning apis work extra hard keep things simple
  95. Api discovery using json home
  96. Different search engines for api discovery
  97. Microservice discovery using pivio
  98. When describing your machine learning apis work extra hard to keep things
  99. Understanding global api performance at the multi cloud level
  100. Learning about real time advertising bidding transparency using ads txt
  101. When cities use a common api definition to report non emergency issues
  102. Making sure your api service connects to other stops along lifecycle
  103. Making sure your api service connects to other stops along the api lifecycle
  104. Craft an openapi for an existing threat intelligence sharing api specification
  105. Us energy information administration excel add in and google add on
  106. Api sdk licensing notifications using versioneye
  107. The trusted automated exchange of intelligence information
  108. The trusted automated exchange of intelligence information taxii

July 2017

  1. Professional api deployment templates
  2. Making the business of apis more modular before you do the tech
  3. You see duplicate work while i see common patterns
  4. Balancing domain expertise with the disruptive power of upstarts doing apis
  5. Balancing domain expertise with the disruptive power of upstarts who do apis
  6. State of apis in the federal government
  7. We have a hostile ceo which requires a shift in our api strategy
  8. A lack of communication around federal government apis
  9. Api management across all government agencies
  10. Adding vulnerability disclosure to my api building block recommendations
  11. I am speaking on state of apis in federal government thursday in dc
  12. Federal government apis in a trump administration
  13. The hack education gates foundation grant data has an api
  14. Finding things i want to write about when apis are dumb
  15. First handful of lessons using my google sheet github approach
  16. Structured threat information expression language
  17. Requiring all platform partners use the API so there is an application defined
  18. Misconceptions about what openapi is still slowing conversations
  19. Structured threat information expression stix
  20. Requiring all platform partners use the api so there is a registered
  21. Misconceptions about what openapi isnt still slowing conversations
  22. Charles proxy generated har to openapi using api transformer
  23. 100k view of bot space from the api evangelist perspective
  24. Managing platform terms of service in a site policy repository
  25. The plivo support portal knowledge base
  26. The plivo support portal and knowledge base
  27. More investment in api security
  28. The most imortant aspect of the api discussions is leaning to think outside our boxes
  29. Does your platform have an integrations page
  30. Containerized microservices monitoring driving api infrastructure visualizations
  31. The most important aspect of the api discussion is learning to think outside
  32. Containerized microservices monitoring driving api infrastructure
  33. One api development partner every api provider should have
  34. Specialized collections of machine learning apis could be interesting
  35. Diagramming the components of api observability
  36. Http status codes are an essential part of api design and deployment
  37. Writing api stories that speak to my audience but also influences their view of technology
  38. Bot observability for every platform
  39. Making all sub resources available within the core set of human service apis
  40. Writing api stories that speak to but also influences their view of technology
  41. Learning more about amazon alexas approach to apis and skills development
  42. Quantifying the difference between human services data specification hsds and its api
  43. Moving the human services api specification from version 11 to 12
  44. Quantifying the difference between human services data specification hsds
  45. Challenges when aggregating data from across the years
  46. 20k 40k 60k and 80k foot levels of industry api design guidance
  47. Providing solid examples that api consumers can learn from like slack app blueprints
  48. A zapier advocate and dedicated api resources page for your company
  49. Providing solid examples that api consumers can learn from like slack app
  50. Challenges when aggregating data published across many years
  51. Each airtable datastore comes with complete api and developer portal
  52. When you publish a google sheet to the web it als becomes an api
  53. Either you own the conversation around your apis or someone else will
  54. Locking down drones and iot devices by manufacturers
  55. When you publish a google sheet to the web it also becomes an api
  56. Github serverless
  57. Having the right commications pipeline for your api platform
  58. Being first with any technology trend is hard
  59. Opportunity to develop a threat intelligence apis json
  60. Opportunity to develop a threat intelligence aggregation api
  61. Having the right communications pipeline for your api platform
  62. When json schema is seen as power
  63. The essential api elements in my world
  64. Openapi leading the open banking api conversations
  65. Does your api sandbox have malicious users
  66. Standardizing and templatizing api design editor validation tips
  67. Openapi leading the open banking api conversation
  68. Enhancing your api seo
  69. A bot that does useful things for me
  70. An api change log and road map visualization
  71. Bringing the api deployment landscape into focus
  72. A bot that actually does useful things for me

June 2017

  1. The growing importance of geographic regions in the api economy
  2. Electronic submission of injury and illness records to osha using api
  3. Electronic submission of injury and illness records to osha using api. markdown
  4. Making an account activity api the default
  5. Shared publishing to github org
  6. Shared publishing to github org. markdown
  7. The growing importance of geographic regions in api operations
  8. Algorithmic transparency in policing
  9. Continue to explore restaurant menu as an analogy for api copyright and patents
  10. Api preparation at the bureau for the 2020 census
  11. I have two interesting apis and i am not a developer what do i do
  12. I have two apis i am interested in and i am not a developerwhat do i do
  13. Continue to explore restaurant menu as an analogy for api copyright and
  14. Algorithmic observability in predictive policing
  15. The open service broker api
  16. Api environment portabiity
  17. Patent number us 20170153932 adapting legacy endpoints to modern apis
  18. I published 60k patents to github as part of my api patent research
  19. Patent us 20170153932 adapting legacy endpoints to modern apis
  20. Api environment portability
  21. Three new api industry groups on the horizon
  22. Healthcare api interoperability at hl7 fhir dev days in amsterdam
  23. Budget transparency at the county level with open data and apis
  24. The competitive advantage of api agility over any secret saurce
  25. The competitive advantage of api agility over any secret sauce
  26. I would love to reference github data across repos with org data object
  27. Api plans arent sustainable for my small business
  28. Api plans are not sustainable for my small business
  29. Patent api matchmaking using feature models
  30. Validating api schema as part of security process
  31. Making machine learning acessible to spreadsheet power users
  32. I am working with elastic beam to help define api security
  33. Validating my api schema as part of my api security practices
  34. Patent us9639404 api matchmaking using feature models
  35. Making machine learning accessible to spreadsheet power users
  36. Internet as example of markets working things out
  37. Tensor flow object recognition
  38. Tight coupling to our mobile phones
  39. Unknown unknown with api security
  40. The general services administration api strategy considers how to generate revenue
  41. Idks are always first step in api integration
  42. Tightly coupled to our mobile phones
  43. The unknown unknowns of api security
  44. Api wrappers to help bring machine learning into focus
  45. The six dimensions of api patents I dwell on
  46. Three rules of my api communication strategy
  47. I would like to see more api test drives
  48. Unknown unknown with api security
  49. Idks are always first step in api integration
  50. Idk is always the first step to api integration
  51. Data access and api strategy in the european union
  52. Making your api available in marketplaces
  53. Serverless blueprints for your api
  54. Github helping set the bar for your api community code standards
  55. Publishing your api in the aws marketplace
  56. Zooming out to the 100k level then back to api sea level with openapi and apis dot json
  57. A community approval dimension when adding updating and deleting via api
  58. My api communication stack for the human services api specification
  59. Zooming out to the 100k level then back to api sea level with openapi and apis json
  60. Gsa api standards with working prototype api and portal
  61. The yes i would like to talk button signing up for api platform
  62. The successes and mostly failures of a developer evangelist
  63. Proprietary views of your taxonomy
  64. The yes i would like to talk button when signing up for an api platform
  65. The gsa api standards with a working prototype api and portal
  66. Weekly roundups vs short stories
  67. Setting the rules for api automation
  68. I wish usa facts had embeddable and sharing strategy
  69. More evangelism and less sales is needed to move forward banking api conversation
  70. More evangelism will be needed to move banking api conversation forward
  71. I wish usa facts had a more sophisticated api embeddable and sharing strategy
  72. Revisiting graphql as part of my api toolbox
  73. Recent api paths
  74. Tweeting out api forum conversations
  75. If oracle wants to be taken seriously with apis it needs to drop api copyright case
  76. Tweeting out your api forum conversations
  77. If oracle wants to be taken seriously with its api campaign it needs to drop
  78. I like apicurios road map
  79. Trade dot gov
  80. The apis json for trade gov
  81. I like the apicurio road map
  82. Temporary interaction limits
  83. Kdl a graphical notation for kubernetes api objects
  84. Patents as a measure of individual success
  85. The support elements of your api service level agreement
  86. Patent automated assessment of terms of service in an api marketplace
  87. Patent us 8954988 automated assessment of terms of service in an api marketplace
  88. Apis for monitoring the performance of your apis
  89. A conference focused on machine learning apis
  90. Transparency around every company who has access to our social data via an api
  91. Openapi in gov
  92. Examples of the openapi specification used for government apis
  93. Documentation research
  94. Patent api descriptions
  95. Expanding on api acronym
  96. Apis are how our digital selves are learning to speak with each other
  97. The effect of visual design and information content on readers assessments
  98. Patent us 8997069 api descriptions
  99. Expanding on the api acronym
  100. Extending your apps using embeddable serverless webhooks
  101. Algorithmia invests more resources into machine learning apis for working with video
  102. Patent determining trustworthiness of api requests
  103. The number one api example you should be following
  104. Patent us9462011 determining trustworthiness of api requests
  105. An api you should consider emulating when crafting your saas api business
  106. Algorithmia invests more resources into machine learning apis for working with
  107. The depth and dimensions of monitoring api operations
  108. Api documention width sdk bridge
  109. The github repo stripe users to manage their openapi
  110. Centers for medicare and medicaid services api for quality payment program measures
  111. The github repo stripe uses to manage their openapi
  112. Centers for medicare medicaid services api for quality payment program measures
  113. When you praise good people in government
  114. Data visualization and storytelling around museum collections using apis
  115. Heavier investment in api training will be necessary
  116. Managing your postman collection using github

May 2017

  1. Adding three apimatic openapi extensions to the openapi toolbox
  2. An example of api ethics out of cambridge university
  3. A perception of patent and copyright overlapping when it comes to apis
  4. Api providers localizing compute for developers using serverless
  5. Exploring the possibilities with my drone prototype api
  6. Apicurio is the open source api editor i was looking for
  7. Apicurio is the open source visual api design editor i was looking for
  8. Every api should begin with a github repository
  9. Craft your api design guide so you can move to other areas of lifecycle
  10. Craft your api design guide so you can move to other areas of the lifecycle
  11. Spreadsheet to github for sample data ci
  12. How twitter handles sorting for their api
  13. Considering http prefer header instead of field filtering for my api
  14. My api design checklist for this version of the human services data api
  15. Considering using http prefer header instead of field filtering for this api
  16. Thinking about privacy and security of public data
  17. Avoid moving too fast for my api audience
  18. Thoughts on openapi not being the solution
  19. Thinking about the privacy and security of public data using api management
  20. Some thoughts on openapi not being the solution
  21. Keen pushing forward schema conversation
  22. Box goes all in on openapi
  23. Keen io pushing forward the data schema conversation
  24. Evolving api sdks at google with storage logging and analytics
  25. It is not the technology api monitoring means you care
  26. On device machine learning api stack
  27. Its not just the technology api monitoring means you care
  28. My google sheet driven product api and web page
  29. Convince people that the api economy is the future
  30. The parrot sequoia api is nice and simple for iot
  31. 15 topics to help folks see the business potential of apis
  32. Focusing on what you do best while leveraging apis to not reinvent the wheel
  33. Studying how providers are supporting batch api requests
  34. Json schema for openapi version 3 dot 0
  35. Json schema for openapi version 3 0
  36. Key factors determining who succeeds in the api and ml marketplace game
  37. Schema defines storage and api defines access
  38. An openapi generator for publishing to github
  39. The human services schema defines the storage and the api defines access
  40. Google spanner is a database with an api core
  41. Generating revenue from the remarketing tags on api evangelist
  42. One layer of api ranking will be domain scoring
  43. One layer of an api ranking system will need to be domain scoring
  44. My new cms for manging my network of github sites
  45. My new cms for manging my network of github site
  46. Helping standardize how we communicate about the api integration possibilities
  47. Api integration service providers
  48. A new look for api evangelist
  49. Using public lands as an analogy when talking about public data apis
  50. My challenges when taking money from startups as the api evangelist
  51. A handful of microsoft flow openapi extensions
  52. Simple apis with jekyll and github with data managed via google spreadsheets
  53. In search of some funding for my machine learning api research
  54. Adding an extensions category to the openapi toolbox
  55. The list of api signals i track on in my api stack research
  56. Public and private sector hybrid data marketplaces
  57. Pricing tiers works for saas but not really for apis
  58. Regional availability when it comes to api access
  59. Participating in the openapi feedback loop
  60. Openapidriven documentation for your api with redoc
  61. The value of operational level api exhaust systems
  62. Taxation on public data via the api management layer
  63. Quantifying the data a company possesses using apis
  64. I pushed 1173 api definitions to the api stack
  65. Open discussions about funding api startups
  66. My new api vendor evaluation checklist
  67. Defining the surface area of the facebook api
  68. Quantifying the api landscape across amazon google and microsoft
  69. Expressing what an api does as well as what is possible using openapi
  70. Communication with consumers through the design of our apis

April 2017

  1. Where do i start with apis your website
  2. Where do i start with apis your existing software usage
  3. A view of the api lifecycle from james higginbotham
  4. Wearing my tech vendor hat when it comes to public data
  5. Sdk generation api validation and transformation using the apimatic cli
  6. Api definitions should be done by the api provider
  7. Zapier was pretty savvy in their approach to launching their partner api
  8. Simple api design interface features
  9. My concerns as a public data steward
  10. Your wholesale api for sale in the major api marketplaces
  11. Google and aws apis available in visual studio and eclipse ides
  12. Api rate limiting at the dns layer
  13. The concern around availability and reliability of government apis
  14. Separating the licensing layers of your valuable data using apis
  15. A ranking score to determine if your api was sla compliant
  16. The sla is becoming standard across google apis
  17. How i can help make sure your api is ready for use
  18. Developing internal api curriculum and workshops for your organization
  19. Continuous integration conversational interfaces
  20. Stories are the best way to keep the door open
  21. Human service apis on aws azure google and heroku
  22. Continous integration platform as a service at the command line
  23. Protecting our valuable data with apis
  24. Google partner api as a blueprint for other apis
  25. Google needs to get their api icon set in order
  26. Yaml templates for api operations
  27. Log files are only for when things go wrong
  28. Ibm has a nice api explorer
  29. Your api should reflect a business objective not a backend system
  30. More api evangelists and storytellers please
  31. Add an api to the web for sharing text urls and images
  32. The evolution of the api strategy and practice conference
  33. Gearing up for enterprise sales with an api service level agreement
  34. From crud to an api design conversation with human services
  35. Tooling for converting your openapi definitions from 20 to 30
  36. Tooling for converting your openapi definitions from 2 0 to 3 0
  37. Playing with different views for an openapi diff tool
  38. Six api embeddables to consider for your api
  39. Open source drag and drop api lifecycle design tooling
  40. Exploring github curated galleries
  41. What questions would you ask across 50k api definitions
  42. Openapi as an api literacy tool
  43. Getting feedback from your api community when developing apis
  44. The paradox of api evangelist
  45. My oxford dictionaries talk about the world of apis
  46. An introduction to github for api providers

March 2017

  1. Taking a look at the stoplight api spec editor
  2. Rest linked data hypermedia graphql and grpc
  3. Using google sheet templates for defining api tests
  4. Complimentary apis for the oxford dictionaries api
  5. An opportunity to emulate slack buttons
  6. Learning to use our words better when defining our apis
  7. Helping your customers operate throughout the api life cycle
  8. All api startups should be more like glitch
  9. I think the parse twitter page sums it up pretty well
  10. Being able see an api request in browser is important
  11. Api definition api transformer
  12. I predict a future flooded with google prediction galleries
  13. Api definition us data federation
  14. Api definition u sdata federation
  15. A looser more evolvable api contract with hypermedia
  16. Uber is painting bigger picture of their drivers with driver api partnerships
  17. Moving apis out of the partner realm and making them more public
  18. Api definition webconceptsinfo
  19. Api definition webconcepts info
  20. Sharing api data validation examples
  21. Deploying your apis exactly where you need them
  22. Api definition open api specification 300rc0
  23. Api definition open api specification 3 0 0rc0
  24. Opportunity for push button api deployment with google cloud launcher
  25. Api icon vocabulary
  26. Api definition human services api specification
  27. With each api we increase the attack surface area
  28. Reminding myself of why i do api evangelist
  29. Considering standards in our api design over being a special snowflake
  30. The openapi toolbox and my api definition research
  31. The api evangelist api definitions guide
  32. Google support buttons
  33. Api evangelist industry guide to api definitions
  34. A community strategy for my api definition guide
  35. What will it take to evolve openapi tooling to version 30
  36. What will it take to evolve openapi tooling to version 3 0
  37. The ability to deploy apis in aws google or microsoft clouds
  38. Api environment variable autocomplete and tooltips in postman
  39. Tracking on licensing for the solutions in my openapi toolbox
  40. Thinking about schemaorgs relationship to api discovery
  41. Thinking about schema org039s relationship to api discovery
  42. The relationship between dev relations and support
  43. Getting our schema in order with postmans new data editor
  44. Azure and office apis in visual studio
  45. A tighter api contract with grpc
  46. Thinking about schemaorgs relationship to api discovery
  47. Getting our schema in order with postmans new data editor
  48. Getting our schema in order with postman039s new data editor
  49. A tighter api contract with grpc
  50. Lots of talk about machine learning marketplaces
  51. Greyballing is embedded in apis dna
  52. Greyballing is embedded in api039s dna
  53. Airmaps api enabled digital notice and awareness system
  54. Airmap039s api enabled digital notice and awareness system
  55. Telling a more complete story with hypermedia
  56. Focus on having a robust and diverse api toolbox
  57. Api definitions covering both rest and grpc apis
  58. The three layers of api hype
  59. Guidance on versioning your api from google
  60. From awareness observability to api ratings
  61. People doing interesting things with apis
  62. A framework for our all day api discussion
  63. There is more to this than just having an api
  64. The tyk wordpress api portal
  65. I am learning about grpc apis from google
  66. Thinking about openapi provenance
  67. Please develop an embeddable open source visual api editor
  68. Do you have an api design guide for your operations
  69. I want to just post information directly to your api platform
  70. Google shares their api design guide
  71. Deploy a grape doorkeeper driven api to heroku with a click of a button
  72. My developer portal checklist for a human services api
  73. Getting back to work on my openapi toolbox
  74. Dreaming of a more modular event driven api monetization
  75. New york times manages their openapi using github
  76. Mapping github topics to my api evangelist research
  77. A machine readable definition for your aws api plan

February 2017

  1. Will the experian api focus on the people being ranked
  2. The aws serverless api portal
  3. A checklist for api observability
  4. The api definition for the tyk api gateway
  5. I need your help with my api definition industry guide
  6. An example of an api service provider using hypermedia
  7. A well thought out api platform
  8. Api definitions influencing api design
  9. Trying to define api awareness
  10. Api lifecycle service providers instead of walled gardens
  11. Boxs seamless approach to api documentation
  12. Box039s seamless approach to api documentation
  13. Api lifemiddlewarecycle api
  14. A ckan openapi spec
  15. Using github as an api index and data store
  16. The reasons why we pull back the curtain on technology
  17. Where are the interesting api bookmarklet examples
  18. What do you get when you search for the schemaorg logo
  19. What do you get when you search for the schema org logo
  20. Having a program for researchers baked into your api operations
  21. Api management is getting more modular and composable
  22. Api evangelist joins the open api initiative oai
  23. The unlimited possibilities when you become api definition fluent
  24. Sharing compute costs for open data and api consumers using the cloud
  25. Api embeddables in a conversational interface world
  26. Maintaining on premise capacity as well as cloud expertise
  27. Helping carry the load when it comes to public data and apis
  28. Dedicated space for telling the stories of your api consumers
  29. What i would like to see from api providers when it comes to public analytics
  30. Application the action of putting something into operation
  31. Api definitions documentation and hypermedia
  32. The amazon console came after the api and cli
  33. Preparing for conversations about schema definitions and scopes
  34. Including end users in the conversation about their bits being sold
  35. Amazon dash ok ideadumb implementations
  36. Amazon dash ok idea dumb implementations
  37. A limited medium api means i do not always curate what is published there

January 2017

  1. The importance of apis in journalism right now
  2. If you are doing interesting things with apis please tell the story
  3. I got a response regarding my facebook threat api access
  4. Funding the development of an api ranking solution
  5. What is at stake with api definitions at the moment
  6. The openapi specification version 30 highlights
  7. The openapi specification version 3 0 highlights
  8. Pull the social media accounts for gov using the us digital registry api
  9. Making your api portal speak to the widest possible audience
  10. Loss of primary and foreign keys translating from data package to openapi spec
  11. Amazon alexa uses http2
  12. No database behind an api and just using files stored on github
  13. Considering the logging and observability layer for amazon alexa enablement
  14. Adding the webhoseio search api to stack of apis i depend on
  15. Reducing our hard work to a transaction with apis and serverless
  16. The state of california drinking water program repository
  17. Oracle acquiring apiary
  18. Focusing on common api definitions schema scopes and specifications
  19. When we lose trust in the reporting numbers our providers feed us
  20. Patent 20150363171 generating virtualized api from narrative api documentation
  21. What are the goals behind launching an api portal
  22. Profiling facebook threatexchange api
  23. No innovation around terms of service reveals true motives
  24. Requiring ssl for api all calls
  25. Ifttt vs zapier vs datafire
  26. A missed opportunity with the medium api
  27. Why i still believe in apisthe 2017 edition
  28. Using an openapi spec as central truth in stakeholder discussions
  29. The google baseline for a user account area
  30. Your state issued id is required to signup for this online service
  31. Intercom providing docker images of their sdks
  32. Evernote reaffirming our commitment to your privacy
  33. The design process helping me think through my data and content
  34. Patent us9300759 b1 api calls with dependencies
  35. Hoping schema becomes just as important as api definitions in 2017
  36. The api driven marketplace that is my digital self
  37. Service level agreements for researchers who depend on apis
  38. Evaluating a new channel for publishing my bits
  39. Algorithmias multiplatform data storage solution for machine learning workflows
  40. Algorithmia039s multiplatform data storage solution for machine learning workflows
  41. What i learned crafting api definitions for 66 of the amazon web services
  42. Explaining to normals why every api is different
  43. Api calls as opposed to api traffic
  44. A glimpse at minimum bar for business api operations in 2017
  45. Thinking about the monetization layer for public data
  46. Learning about machine learning apis with my algorithmic rotoscope work
  47. Exploring the economics of wholesale and retail algorithmic apis

2016 495

November 2016

  1. Pandora vs target when considering how public to be with your api operations
  2. Focusing on a single example of what an api is when onboarding folks
  3. The taiwanese government posts an apis json index
  4. The api evangelist mission continues
  5. Daisy chaining multiple api paths using stoplight scenarios
  6. Maintaining the api community at scale apistrat
  7. How do you work towards a more diverse inclusive tech conference
  8. Drone recovery in the attention economy

October 2016

  1. We will need machine readable transparency report info via apis
  2. A drone law api for use in planning and at flight time
  3. Why upgrade to a paid plan
  4. Tooling to help aggregate dns across multiple service providers
  5. Allowing for relationships between api developers at the app level
  6. Transparent data transfer control apis at the iot device level
  7. Potential for apis to target us online by adding more context
  8. Learning the dimensions of the dji drone sdks and apis
  9. Asynchonous conversational interfaces for us anti social folks
  10. Apis helping drones generate alpha used in high frequency trading
  11. With mobile we are the productwith iot lets get a piece of the action
  12. Thinking about an api observability stack
  13. Looking at the latest api related certification stories
  14. Api technology does not have to mindlessly march forward
  15. Adding new dimension by including patents in my dns api research
  16. The api behind every feature in the user interface
  17. Prototype api design guide builder developed on top of api stylebook
  18. Preserving the twitter api field guide
  19. Amazon groups should share more api design patterns
  20. Icons to describe each of your api resources like aws
  21. Does your business model reflect where your api deployment is going
  22. An api discovery api for your api with tyk
  23. What is more important helping new users be aware of apis or pushing concept forward
  24. What are your intentions with my api
  25. The potential of the openapi spec parameters object
  26. The open guide to amazon web services
  27. Reducing friction for api developers with enums in api definitions
  28. We want to do apisyou already are it is just not in an organized way
  29. Openapi spec google spreadsheet to github jekyll hosted yaml
  30. How do we keep the fire alive in api space
  31. The twitter branding page provides minimum bar for api providers
  32. Learning about apis has to be relevant and interesting
  33. Are api docsdefinition formats a single thing or separate
  34. Are api docs amp definition formats a single thing or separate
  35. All the right channel icons in support of your api platform
  36. A more honest and flexible api contract using hypermedia
  37. Thinking more about api driven conversational interfaces
  38. People do not know what your api does if you do not showcase it
  39. Discovering new apis through security alerts
  40. Defining oauth scope inline within the api documentation
  41. Convert openapi spec to slateshins markdown api docs
  42. Transparency in police access to social platforms using oauth and apis
  43. The monitoring layer of the devops aggregation api platform
  44. Taking a fresh look at the twitter api
  45. Slack shares their view on bot advertising
  46. Including the twitter object nest api as a file upload api example
  47. The open skills api from dept of laboruniversity of chicago
  48. The open skills api from dept of labor amp university of chicago
  49. Saving and versioning api definitions in editor using github gists
  50. Preservng the sunlight on github
  51. Preserving the sunlight on github
  52. Keeping api communications in shape with workbench blogging
  53. Drones and other devices having their own software defined networks
  54. We understimated the time it would take for hypermedia to be absorbed
  55. The white house wants our thoughts on data portability
  56. Some key iot security considerations
  57. Do you have agencies ready to develop with your api
  58. Apis driving augmented reality for drones
  59. Some api embeddable best practices out of yelp
  60. Ipaas in your browser with push by zapier
  61. I am stuck on the datadog integration page
  62. Expanding on the 3rd party analysis of security threats
  63. Api embeddables with skills and intent
  64. The internet of things shows us how regulatory beasts are created
  65. Opportunity for someone to help organize auto industry data
  66. Google shares insight on how to improve upon the api experience
  67. Embrace extend and exterminate in the world of apis
  68. The anatomy of api call failure
  69. Regulatory api monitoring for validating algorithmic assertions
  70. Harmonizing api definitions across government with the us data federation
  71. Harmonizing api definitions across government with the u sdata federation
  72. Hacking on amazon alexa with aws lambda and apis at apistrat
  73. Amazon launches their own qa solution called aws answers
  74. Your southwest airlines flight has an api
  75. Providing inline api documentation within your saas user interface
  76. An auditing api for checking in on api client activity
  77. Adding behaviordriven development assertions to my api research
  78. A machine readable jekyll jig for each area of my api research
  79. Where is the wordpress for apis
  80. The web evolved under different environment than web apis are
  81. Github as the api life cycle engine
  82. Evolving the api sdk with apimatic dx kits
  83. Considering a web api ecosystem through featurebased reuse
  84. Please share your openapi specs so i can use across the api life cycle
  85. Making data serve humans through api design
  86. Increased analytics at the api client and sdk level
  87. An integrations page for your api solution
  88. Amazon alexa as an example when it comes to api communications
  89. The different reasons behind why we craft api definitions
  90. Running synthetic data and content through your apis
  91. Apis can give an honest view of what a company does
  92. A service level agreement api for api service providers
  93. A dedicated security page for your api portal

September 2016

  1. You cant say ai benefits outweigh risk without some algorithmic transparency
  2. You can039t say ai benefits outweigh risk without some algorithmic transparency
  3. If you have an api for your platform you are a stage for cybersecuritytheater
  4. If you have an api for your platform you are a stage for cybersecurity theater
  5. Defining a conversational layer on top of apis
  6. Api sdks getting more specialized
  7. A plan b api switch
  8. Schemahub39s usage of github to launch their api service is a nice approach
  9. Schemahub039s usage of github to launch their api service is a nice approach
  10. Flow abstraction and intent layer on top of apis to feed the bots
  11. Code resiliency lessons in how twitter deploys their embeddables
  12. Beyond mobile api ready for ipaas voice and bots
  13. An opportunity for a restful api layer on top of new tensorflow models
  14. We focus on interacting with the api developer community where they live
  15. Thinking about how i can build change resilience into my api integrations
  16. The bot platform that operates like alexa will win
  17. Learning about opc the interoperability standard for industrial automation
  18. Every government agency should have an faq api like the dol
  19. Thanks for reaching out about your api
  20. Github needs client oauth proxy for more complete clientside apps on pages
  21. Every government agency should have a forms api like dol does
  22. Api design is not requirement for all devs but a little empathy should be
  23. Api access to your account by default but requires permission to see others
  24. Taking another look at the department of labor api efforts
  25. My api definitions are incomplete but you do not want to contribute
  26. Helping validate data and algorithmic sovereignty at the api layer
  27. Doing away with selfservice api access without approval like soundcloud
  28. Api service providers please have a logos page like dreamfactory
  29. The sharing of data via apis will be key to viability of every industry
  30. Learning from the sunlight foundation situation and baking transparency into projects
  31. Identifying the important work from the sunlightfoundation i would like to see live on
  32. How to discover no name and description twitter accounts for folks in the enterprise
  33. Decoupling the solution provided from the product in your storytelling
  34. The why behind the github graphql api
  35. Syndicating api evangelist posts to medium using their api
  36. Providing branding and attribution assets with each api response
  37. Google spreadsheets as an engine for api goodness
  38. Api branding embeddables that can boost my api rate limits
  39. What i mean when i say api
  40. The psa peugeot citrons apis
  41. Be part of your community do not just sell to it
  42. A new api programming language sdk icon set
  43. Why would you build a business on apis they are unreliable
  44. Standards evangelism
  45. I am feeling the same about yaml as i did with json a decade ago
  46. D3js visualizations using yaml and jekyll
  47. D3 js visualizations using yaml and jekyll
  48. A trusted github authentication layer for api management
  49. Putting the concept of the public api to rest as a dominant narrative
  50. Providing yaml driven xml json and atom using jekyll and github
  51. My forkable minimum api portal definition
  52. My dream api sketchbook and portfolio
  53. A twilio process to emulate within your own api operations
  54. Standardizing api documentation for use across the api lifecycle
  55. Learning from the success of swagger ui
  56. A look at the state of api documentation solutions
  57. The next api lifecycle opportunity will be in design and definitions
  58. Now keeping an eye on 66 areas of the api lifecycle
  59. If you have an online product catalog you should have an api
  60. Tracking on where the politics of apis intersects with the business of apis
  61. Sharing some basic numbers for api evangelist
  62. Harvesting companies who are doing apis from press releases
  63. Building the case for redefining the mortgage industry using apis
  64. An api data retention policy and paying for longer storage
  65. The general bikeshare feed specification
  66. If an algorithm impacts our life it should be opened up with an api for auditing
  67. Considering how apis are influencing the fundamentals of software engineering
  68. Api providers partnering to provide a developer business incubator
  69. Api infrastructure to help your 3rd party developers be more efficient
  70. Adding to the available branding resources for api developers
  71. Where is the deploy to aws and google button
  72. The new api design and deployment solution materia is pretty slick
  73. Google acquired apigee
  74. Considering the hypothesis api approach when expanding the api life cycle discussion
  75. Api stylebook a collections of resources for api designers
  76. We better get to work on evolving an open emergency response api stack
  77. Regex suggestion discovery for web concepts and specs during api design time
  78. Providing video walk throughs on youtube for your api or api provider services
  79. Prepare for the more boring and very business age of apis
  80. Everything is fragile in the world of apis
  81. When working with our api make sure you build faultresistance into your code
  82. When the latest tech bullshit has me down i will work on water apis
  83. Defining api surface area by converting html forms to open api specs
  84. Are you being transparent with your api infrastructure to attract top talent like netflix is
  85. A dictionary to lookup web concepts and specs for the javascript tooltip
  86. Using the phrase open api in patents shows how broken patents are in a digital world
  87. Using the phrase open api in patents shows how broken patents are a digital world
  88. The netflix public api was the most successful api failure ever
  89. The burden on api providers when it comes to web literacy
  90. Just because the enterprise will never get apis does not mean you should not try
  91. A web concepts and specifications javascript library for api providers
  92. Working tips and tricks into your regular api evangelism efforts
  93. Stoplight displays api definitions by default with their api doc service
  94. Imagine if tim berners lee or roy fielding had patented their work
  95. Connecting my api logging with my api dns using cloudflare page rules api
  96. A json feed of critical web concepts to integrate into api design service and tooling
  97. I am keeping my mind open and looking forward to learning more about graphql
  98. Be straight up about internal challenges when hiring your api talent
  99. Api patent search as way to discover companies who are doing apis
  100. After looking through 23414 api patents i think it will just come down to who litigates
  101. 23k patent applications with api references since 2005
  102. Why do companies who ask me to update their logo never have branding page
  103. The sustained api storytelling assault on the banking industry
  104. Mapping your social media footprint as part of your api security strategy
  105. Making web concepts and specs present as real time help in api design tooling
  106. Api design skills required for cyber intelligence and counter intelligence

August 2016

  1. Why apis are just the next step of the web and not the latest trend
  2. Treating new api startups like the companies they will become
  3. The internet of things is an opportunity for api deployment as well as consumption
  4. Enterprise does not know care how big and destructive it is to apis
  5. Company xs competitive advantage is that they have an api
  6. Company x039s competitive advantage is that they have an api
  7. Why i added cybersecurity to my api monitoring research
  8. The ways that api providers are using twitter
  9. Taking a moment to catch up with apis before moving to next big thing
  10. Keep publishing your api definitions to github so we can find them
  11. Graphql seems like we do not want to do the hard work of api design
  12. The api lightbulb went on for me when amazon ec2 launched a decade ago
  13. Github is quickly becoming my most important discovery source for api space
  14. Beyond just api discovery the technical businesspolitical decisions needed at runtime
  15. Beyond just api discovery the technical business amp political decisions needed at runtime
  16. Apis are not just meant for killer apps they can also be a lifeline for users
  17. Add a prominent icon link to your api definition on your documentation page
  18. Using anchors in your faq and other api support pages
  19. Is your sales deal size just too big to be reading api evangelist
  20. I am digging stripes new interactive api documentation walkthrough
  21. Going the distance to help api consumers find their api keys and tokens
  22. Watching out for your api keystokens on open internet
  23. Watching out for your api keys amp tokens on open internet
  24. Providing a dedicated mobile sdk page for your api
  25. More considerations when providing an anonymous app for your api service
  26. Managing the apps across all my api accounts
  27. Adding an atom feed for the api evangelist blog
  28. You can make money while also doing important work for the api space
  29. If you use api definitions there is no excuse for not having an api sandbox
  30. Crx extractor wins for the best customer quote ever
  31. An openapi spec for a building permits api
  32. A wicked good open source api deployment and management stack
  33. Who is going to do the devops aggregation api platform
  34. The expanding api layers that overlap our physical and virtual worlds
  35. Sharing your api platform road map and telling the story like readmeio
  36. Sharing your api platform road map and telling the story like readme io
  37. Prioritizing commonly requested information with your api deployment
  38. Api providers could add a page to showcase their bots
  39. What is a restful api and why does it matter to iot
  40. Thinking in terms of api skills and moving beyond just api resources
  41. The racial bias being baked into our algorithms
  42. The expanding world of technology evangelism
  43. Delivering api docs using openapi spec driven templates for angular
  44. When your api consumption influences the acquisition of your startup
  45. Providing multiple types of api sandboxes to develop against
  46. Providing an anonymous layer to your api provider service like stoplightio
  47. Providing an anonymous layer to your api provider service like stoplight io
  48. I know it is hard when you are just getting started but please make your pricing page public
  49. Tweeting out the ipaas opportunities that are available for your api
  50. The historic newspaper api from the library of congress
  51. Providing additional support options for your api in your twitter bio
  52. Maybe a save as json option for excel wasnt forward thinking enough
  53. Maybe a save as json option for excel wasn039t forward thinking enough
  54. Expanding my awareness of how apis are being used at the network level
  55. Continuing my struggle for reciprocity as etl evolves into the cloud as ipaas
  56. Zapier and the excel api
  57. The support flow over at the microsoft excel api
  58. Not having rss for your blog and just relying on tweeting
  59. Not all apis are created equal so make sure you set expectations properly
  60. Instead of just discussing via phone you should publish your api goings on to your blog
  61. Defining the industrial programmable automation controller pac strategy using an api
  62. Api definitions are slowly becoming more important than having sdks
  63. Putting the industrial into iot with programmable automation controllers pac apis
  64. Introducing vendorless apis and microservices
  65. Api service composition baked into the cloud with usage plans for amazon api gateway
  66. Constant contact provides good blueprint for an api getting started page
  67. The release of the microsoft excel api is a pretty significant milestone
  68. Investing in your api community like amazon and slack
  69. Google for api code examples just like your new developers will
  70. Will your approach to technology be more like siri or alexa
  71. Where is the ethical line when defining and securing the api landscape
  72. Fascinated with the algorithm
  73. Doing more to invest in web literacy across the api community
  74. Overlay api data on satellite imagery then make available again via api
  75. Access to satellite imagery via a web api
  76. Reconciling how reliable apis are while also embracing tone set by vc investment
  77. I see a number of incomplete api efforts that come out of connected device providers
  78. Diff tooling for json yaml and markdown versions of api definitions
  79. Airmap is positioning itself to be a critical api broker for the drone industry
  80. Thinking about the better business bureau api in context of the overall api economy
  81. Shaming people for not being or understanding rest is why we have so much inconsistency in api design
  82. Pushing for more algorithmic transparency using apis
  83. Iot extends software terms of service and licensing to our every day objects
  84. Uses and disclosures of protected health information 45 cfr 164502
  85. Uses and disclosures of protected health information 45 cfr 164 502
  86. Making scientific research more real time and collaborative using apis
  87. Certifying the network and storage is in country before we adopt internet connected devices
  88. All facts and statistics should have an interactive experience like us census bureaus quick facts
  89. The opportunity for apidriven algorithmic transparency at the mobile data plan level
  90. Direct government connection into internet of things devices like we are seeing with drones
  91. Getting back to api evangelist

May 2016

  1. The community has spoken api evangelist will stay as it is
  2. Api evangelist is up for saleget your bids in by friday
  3. The api evangelist api management guide
  4. The api evangelist api design guide
  5. Oracle vs google apis are kind of hard to understand
  6. Enabling a patients hippa right to access their personal health information phi with apis
  7. Twitter collection of sarahjeong xorswiftstories oracle vs google coverage
  8. Twitter collection of sarahjeong xor amp swiftstories oracle vs google coverage
  9. The concept of patientdirected apis
  10. The api evangelist api definition guide
  11. Cutting through the smokemirrors of it discussions using api definitions
  12. Cutting through the smoke amp mirrors of it discussions using api definitions
  13. A healthy stance on privacy and security when it comes to healthcare apis
  14. Providing a set of api keys for developers to test out different api outcomes
  15. Apis will wither on the vine and never reach their full potential
  16. Quality of service api endpoint for your api platform
  17. An acceptable business model page for your api platform
  18. Serverless approaches to deploying code will help unwind some of the technical debt we have
  19. Twilio provides test api credentials with magic phone numbers
  20. I am seeing significant returns from investing in definitions over code when it comes to my api strategy
  21. The api evangelist api deployment guide
  22. Apis at brigham young university
  23. Working to establish a complete openapi spec for leading apis
  24. Thinking about an api proxy to add link header to each api response
  25. The json schema is proving to be as valuable as the openapi spec
  26. Http header awareness using the link header for pagination

April 2016

  1. The month at a glance road map support and the recent posts for your api platform
  2. What are the most relevant api topics to discuss at apistrat in boston this fall
  3. More patents turning apis into an invasive royalty generating virus
  4. A regular reminder that storytelling is the most important tool in your api toolbox
  5. The wikimedia unique devices data api
  6. Content that lives on when you invest in the right api stories training and guides
  7. Api providersconsumers keeping in touch is how you can set the right tone for an api community
  8. Api providers amp consumers keeping in touch is how you can set the right tone for an api community
  9. Vital resources like the court listener api depend on our donations to operate
  10. Slack meets the minimum viable api platform requirements
  11. Openapi specifications for 642 of the schemaorg types
  12. Openapi specifications for 642 of the schema org types
  13. Using my apisjson annotation tool to drive an api design conversation via github issues
  14. Using my apis json annotation tool to drive an api design conversation via github issues
  15. I like working with json on github because cors is never an issue
  16. I am working with hitchhq team to help api providers build up their communities
  17. I am working with hitchhq team to help api providers build their communities
  18. Helping folks leave their platform and language baggage at home using api definition formats
  19. Empowering you to make informed decisions around your information is what the personal api is about
  20. Sizing up the imaterialise 3d printing api with my minimum viable api operations definition
  21. Sizing up the i materialise 3d printing api with my minimum viable api operations definition
  22. Api rss and the ability to look at your company through an external lens
  23. The average person will never care about their digital stuff enough for personal apis to be a thing
  24. Competing views around the value and ownership of digital resources impacting api security
  25. The pricingplans for 250 api platforms
  26. The pricing amp plans for 250 api platforms
  27. Providing an approved developer catalog for your api
  28. Making the right first impression with your api developer signup email
  29. Staying true to my api core and seeing bots as just one more design constraint
  30. Using forms as an introduction to world of apis for normals
  31. Some of the common building blocks of api deprecation
  32. Formalizing my approach to identifying the low hanging api fruit
  33. The api purgatory museum
  34. Developing api tooling for the average business user over at formio
  35. Developing api tooling for the average business user over at form io
  36. Api deprecation art
  37. Do you have all the links to pricing tos and other critical info for the apis you depend on
  38. Using apis to provide building blocks for still and motion uav imagery media applications
  39. Providing specialized views of an api surface area dynamically with openapi spec and liquid
  40. Playing with one possible openapi spec for the human services data specification hsds
  41. We are all responsible for freemium not working
  42. The api assertions we make believe in and require for our business contracts
  43. My api life cycle research from design to deprecation
  44. Example of api service providers making onboarding with services easier using api definitions
  45. A rogue embeddable button for snapchat
  46. Slack nails the reasons why you open up and share your api road map
  47. That thing you all are doing with slack integrations blockspring is doing it with spreadsheets
  48. Some very different views of what api are and what apis can do
  49. I have an api now i need some help to identify what is needed to manage my api presence
  50. I have an api deployed and a base presence established what can i do to help me get the word out
  51. If your api is worthy of mentioning in your press release it should also be linked on your website
  52. Apis needs to augment my world with a tangible benefit in order to achieve relevance
  53. Who is working on the twitter cards for slack messages unfurl and attachments
  54. The api integration providers who have api access to actions will be successful in bot environments
  55. Api integration service providers should have an api so that their actions are embeddable

March 2016

  1. Hello pinboard customers from linden tibbets the ceo of ifttt
  2. Gathering my thoughts about open referral and the human services api
  3. Where do i start with apis the independent liberal arts college edition
  4. Managing your api terms of service and privacy policies on github like medium does
  5. I am seeing more api platforms manage their blog presence using medium
  6. Best buy will not issue api keys to free email accounts and wants to get to know your company
  7. The annotated code walkthroughs and tutorials over at twilio
  8. The lack of an api and healthy partner integrations is an early warning system for service providers
  9. Exploring a new way to fund api life cycle tooling by open sourcing the api garage
  10. This is how apis will deliver the change we need
  11. Some milestones from the last 15 years of web api history
  12. The unintended consequences of api patents
  13. The more i gather openapi specs the more i realize how we obsess over the unecessary
  14. Fullcontact but for openapi specifications
  15. Deploying the api service providers that i depend on within my own infrastructure
  16. Exposing the meaningful skills our apis possess for use in the next gen messaging and voice apps
  17. Your microservices effort will fail if you only focus on the technical details
  18. What i am seeing as a minimum viable bot presence
  19. Savvy api providers submit pull requests to update their openapi specs in my github repo
  20. I am hearing a lot more talk about restricting free and freemium tiers of api access
  21. Sucked into the world of bots and apis
  22. Further simplifying my api docs and providing api samples
  23. Personal apis are not just a local destination they are a journey
  24. Personal api are not just a local destination they are a journey
  25. Do my apis have the skills they need to compete in a voice and bot enabled world
  26. Api definition driven ui elements path verb and tag autocomplete
  27. Api definition driven visualizations verb tag clouds
  28. When the products we own use apis to order their own replacement parts or service
  29. Datensparsamkeit data minimization
  30. An imbalance in investment priorities that will continue to slow api growth and adoption
  31. Adding a dead pool page to each api research area so we remember the past
  32. Four buckets to organize my api deployment research into
  33. While it does suck parse went away i wish every service that shutdown left behind the same page
  34. Playing with concepts around simplifying the api docs that are generated using api definitions
  35. New icons for helping me communicate how open or closed an api is
  36. Thinking through the design of your pricing api would help you think through your api plan
  37. The 70 platforms with job postings for a developer evangelist or advocate currently
  38. My one piece of advice to next generation of api evangelists is to take care of yourself
  39. It would be nice to have some simpler interactive api documentation in addition to what we have now
  40. Numerous challenges when it comes to comparing even similar api plans
  41. Scraping static docs is often better than proxy for generating machine readable api definitions
  42. Are 1000lb gorillas buying startups to look pretty or just so that nobody else buys them first
  43. A more distilled version of an api getting started page on the home page of a developer portal
  44. My api is not the business driver i hoped it would be
  45. Making api terms of service and privacy policy easy to read and understand

February 2016

  1. A small business api strategy
  2. A simple needs assessment to kick off an api integration and automation journey
  3. Extracting as much value from your api developers as you can then screwing them over in the end
  4. What is apisjson and what is next for the api discovery format
  5. What is apis json and what is next for the api discovery format
  6. Adoptaagency clinicaltrialsgov data and api
  7. Adopta agency clinicaltrials gov data and api
  8. My hangout with wade foster of zapier its about the process
  9. Exploring my thoughts around api injection into messaging voice and other online experiences
  10. The api transparency discussion is not exclusively about being public or private
  11. Some of the micro api evangelist tasks that i get asked to help with regularly
  12. I wish everyone broke their api pricing page down like sendgrid does
  13. I am liking the modular services that are delivering in specific areas of api life cycle like apidocsio
  14. I am liking the modular services that are delivering in specific areas of api life cycle like apidocs io
  15. Generating openapi specs for the mobile apps you depend on just by using them
  16. Concern around mapping and discussing shadow mobile apis shows signs of an imbalance
  17. Automagically defining your api infrastructure as you work using stoplightio
  18. Automagically defining your api infrastructure as you work using stoplight io
  19. As an api service provider should i craft my own api definition format or just reuse what is already available
  20. The essential building blocks for integration automation and reciprocity
  21. The bit size resources we will need for the bot and voice evolution in the api space
  22. All this information is great but where do i start with my api strategy
  23. My tooling and api for gathering and organizing the details of the plans and pricing for apis
  24. Considering the obvious and subtle differences between similar api providers
  25. Looking for partners at every turn when planning your api evangelism
  26. Api evangelist assistant and broker
  27. Importance of thinking externally when writing the description for your api
  28. It is all about no limitations with the enterprise api plans
  29. An embeddable run in postman button for your api
  30. Different api rate limits for verified and unverified free tiers of access
  31. Automated mapping of the api universe with charles proxy dropbox openapi spec and some custom apis
  32. Offering a monthly to annual toggle for your api pricing page

January 2016

  1. If you are proud of your api patents publish your portfolio and showcase them
  2. Parse shutting down maybe we should lower our expectations of tech just a little bit
  3. My vision for one possible future of the api life cycle present in a realtime subway map for helsinki
  4. Breaking out api support into a separate research area
  5. My stance on apis and patents
  6. Embedding your language sdks in your apiary documentation using apimatic
  7. Api definitions are the contract for doing business with apis
  8. Reverse engineering apis from the common apis models we know
  9. Moving towards a meaningful set of icons for the api community
  10. Join 3scale apiary and i for a hangout on api definitions this wednesday
  11. A new open source interactive api documentation from folks over at lucybot
  12. The new api definition abstraction layer over at apiary
  13. Taking a snapshot of just the essential api building blocks across my research
  14. The four categories of dwolla api consumers
  15. The api feedback loop your feedback powers everything we do
  16. Just the best parts of the api documentation please
  17. I just cannot get behind api patents especially when they apply to http and hypermedia
  18. How do i provide a list of certified applications to my api ecosystem partners
  19. Helping the average business user with more information on how to put apis to work
  20. Api aggregation reciprocity and orchestration
  21. Api stack apisio and apisguru need you to create and share your api definitions
  22. Api stack apis io and apis guru need you to create and share your api definitions
  23. Public gets in concert with private post put and delete for your apis
  24. Are we stepping back and considering the potential for abuse with our apis
  25. Using apis to address regulatory uncertainty involved in crossborder data flows
  26. I loaded that csv into a database now let me expose an api so i can get some help
  27. We need an api for the chronology of data breaches database
  28. Providing a dedicated test user api as part of your api virtualization strategy
  29. Your api access replicated into multiple regions around the globe for additional charge
  30. Security will increasingly be used as component of tiered api planning
  31. Aws has a blog that is dedicated to the command line
  32. All companies who have an online product catalog should look at what octopart does with their api
  33. Microsoft increases the visibility of their api driven platform with a new road map
  34. The openapi specification fka the swagger specification
  35. Look across my api monitoring api methods by grouping them using tag
  36. Diff and merging of api definition formats
  37. Api definition origin validation and attribution
  38. Api blueprint has been evolving in two critical areas where openapi spec aka swagger falls significantly short
  39. Thinking about the monetization layer for public data

← 2013–2015 2018–2019 →