The Curious Engineer

API Evangelist

2018–2019

684 posts

← 2016–2017 2020–2026 →

2019 216

December 2019

  1. Pulling your twitter bookmarks via the twitter api
  2. Pulling links from those tweets you have favorited
  3. How my api evangelist research and writing works
  4. Atlassian provides run in postman and openapi by default for jira confluence and bitbucket apis
  5. Applying an apifirst approach to understanding the pacific northwest mushroom industry
  6. Api providers should maintain their own api definitions
  7. Where does the exhaust for your api operations end up being stored
  8. Openapi is the static truth and postman collections are real world derivatives of that truth
  9. How i profile the typeform api
  10. What else has influenced apis over the last 50 years
  11. The 3dcart developer home page is nice and clean
  12. Taming the salesforce api scope
  13. Apis for victoria australia
  14. A portable 23andme api sandbox
  15. Being flexible with authorization when it comes to multiple apis within a single api collection
  16. Api observability is more than just testing and monitoring
  17. Believing the technology startup hype and refusing see anything else
  18. Remember that an application is not just about someone building a web or mobile application with your api
  19. The postman business model is in alignment with enterprise objectives
  20. Focusing on digital api capabilities over just doing apis
  21. Automatically generate openapi for your apis just by using them
  22. We will not convince everyone to go api design first
  23. My thoughts on amazon eventbridge schema registry and discovery
  24. Abstracting away api response complexity with postman visualizer
  25. Validating twitter users using the twitter api without writing code
  26. Twitter api authorization using postman
  27. A postman meetup this tuesday in seattle
  28. We will not discuss apis without a postman collection
  29. Mock aws services using postman collections with examples
  30. Grpcs potentially fatal weakness
  31. I am heading to vegas for aws reinvent

November 2019

  1. I am happy i chose the term evangelism
  2. Bulk updating my postman collections using the postman api
  3. So you wanna build an ipaas solution
  4. Pulling all my postman collections using the postman api
  5. Is it an amazon or aws branded service
  6. Where o where is my api key
  7. Api design consistency across amazon web services
  8. Api copyright directories
  9. Reducing api onboarding friction with api environments
  10. Developing an api environment naming strategy
  11. Api copyright restaurant menu
  12. The missed revenue opportunities for the state of california because they do not have a business registry api
  13. Reference and walkthrough api documentation and collections from shipengine
  14. Attracting the big customers you desire requires a steady stream of api storytelling
  15. Company specific api workspaces
  16. Azure provides sdk governance guidelines
  17. The common building blocks of evangelism
  18. Api copyright blank forms
  19. Subway map visualization postman collection
  20. Organizing ec2 api actions as a postman collection
  21. Api copyright heading to the supreme court
  22. Why is api onboarding and authentication still so hard
  23. What you mean when you say you have an open api not openapi
  24. People are aware of public apis but less aware of mobile apis
  25. How much was the api portal a construct of api management providers
  26. Thinking about data and api governance as well as observability
  27. Getting you up to speed on api definitions
  28. A postman collection as unit of compute for the api lifecycle
  29. What is behind the cli making a comeback
  30. Nobody has api governance figured out
  31. Most api definitions are just fan fiction
  32. Do we deploy provide publish or produce an api
  33. Shitstormingthe latest and previous waves of how apis get planned
  34. Pushing us to think externally is the most important api lesson

October 2019

  1. Profiling the bunq banking api
  2. A diverse api json index example for slack
  3. Why are apis better than direct odbcjdbc connections
  4. Managing your api definitions on github
  5. Api environments are an essential format for our api definition toolboxes
  6. A dedicated open source page for your api platform
  7. The psd2 sandbox from banking api provider bunq
  8. Portable nocode way of sending an sms with nexmo
  9. 20 open source landing pages from leading api providers
  10. The salesforce api could use a little modernization
  11. More information is not always better when onboarding someone with an api
  12. Individual api life cycle stops and operational life cycle stops
  13. Embedding jsonld to power api discovery
  14. Sometimes my desire to automate is more about laziness than innovation
  15. Some api evangelism metrics
  16. It is difficult to know where to begin with apis
  17. Documentation pushes the human readability of your api definitions
  18. Most people just want to deliver the api and will not be interested in the process
  19. Welldefined api workflows are sign of api maturity
  20. Introductory api concepts are timeless
  21. Are you the api librarian within your organization
  22. Most api owners are just focused on issues
  23. Learn to api
  24. Making your api collection the tutorial
  25. Capital g api governance vs lowercase g api governance
  26. Increasing api adoption and consumption
  27. Getting api providers to step up to slosslas
  28. Conducting an api landscape analysis
  29. Api provider onboarding best practices
  30. Personal api tokens for all apis please
  31. Getting started with postman templates
  32. Api first with legacy apis
  33. Api collaboration is the next killer feature
  34. How often do you receive api responses or api definitions in emails from people
  35. Do you have visibility into which teams are developing your apis
  36. Rest and hypermedia and graphql and grpc and eventdriven
  37. Api first is hard to adopt because api deployment is still a manual step for many
  38. Api evangelist api industry guide regions

September 2019

  1. Ensuring we invest in educating and engaging with leadership around our api operations
  2. A robust example of an api json index cataloging public data apis
  3. The developer onboarding use case for postman
  4. I understand that not everyone wants to use the command line
  5. How do we measure the efficiency agility and velocity of an apicentric way of doing things
  6. Simple or complex api collections for different levels of api consumers
  7. I did not fully understand what a postman collection was all about
  8. Attacking cumbersome api queries with a more organized and coherent api collection
  9. Making an api request to update examples in my api documentation and power my api mocks
  10. Enabler mock data apis alongside other apis within my collections
  11. Api industry guide api definitions
  12. Adding twilios referral program as an api building block
  13. Making an api request to update examples in my api documentation and power my api mocks
  14. Looking for apis by industry
  15. An open source sitemap api for every domain
  16. Publishing your early canary beta apis in their own api workspace
  17. Going outside the api echo chamber with your api services and tooling
  18. Some questions to ask when quantifying your organizational api maturity
  19. Publishing my fhir api collection as documentation and making available in the postman network
  20. Json schema examples and postman collections for 600 schema org objects
  21. Postman has documentation and executable collection for their own api
  22. Is this the offer api you were needing
  23. Creating a postman collection for the fast healthcare interoperability resources fhir specification
  24. Business users do not search for api solutions they just search for solutions
  25. Being the source of api truth at your organization
  26. What are you doing with postman
  27. It is hard to not just get to work coding my api
  28. I will be at the api specifications conference in vancouver next month
  29. Apifirst development
  30. The stops along the api lifecycle that postman services
  31. She asked what now after seeing me put together my nasa api collection
  32. I preemptively apologize for the flood of postman storytelling you are about to endure
  33. Giving a postman collection to your sales team
  34. Creating a nasa api postman collection and environment
  35. Api workspace and environment management
  36. I am joining postman as their chief evangelist
  37. Asyncapi version 2 0 is ready for use
  38. Api management for an eventdriven api landscape
  39. The api reality in our heads versus the reality on the ground
  40. Discovering the confluent schema registry
  41. Continue pushing the api documentation conversation forward
  42. Bridging grand visions of an api lifecycle with people on the ground being successful in their work
  43. Where do you like your api complexity
  44. Api management should not just limit me it should allow me to scale
  45. Api evangelist does not run on github anymore
  46. The different ways api providers use the openapi servers collection
  47. Controlling the conversation around your mobile application apis

August 2019

  1. Benefits of treaing my infrastructure as api first
  2. Benefits of treating my api infrastructure as apifirst
  3. Doing a diff between available web mobile and public apis
  4. An api policy domain specialist at twitter
  5. Multiple overlapping api life cycles
  6. The api conferences i am tracking on for the fall
  7. Human empathy is one of my most important api outreach tools
  8. Postman collection as a single quantifiable shareable executable unit of representation for any digital capability
  9. A second wave of api manageent is going on
  10. A second wave of api management is going on
  11. Seeing api consumers as just the other ones
  12. Four phases of internal api evangelism
  13. An observable regulatory provider or industry api management gaeway
  14. An api platform reliability engineer at stripe
  15. An observable regulatory provider or industry api management gateway
  16. Some of the api gateway building blocks
  17. A look at behavioral api patents
  18. Reverse engineering mobile apis to show a company their public apis
  19. Didnt we already do that
  20. The future of apis will be in the browser
  21. Giving away api knowledge for free
  22. About giving away api knowledge for free

July 2019

  1. The challenges of api discovery conversations being purely technical
  2. Differences between api observability over monitoring testing reliability and performance
  3. Peer api design review sessions
  4. Api for processing common logging formats and generating openapi definitions
  5. Api storytelling within the enterprise
  6. Apis and browser bookmarklets
  7. Absolutism around api tools increases friction and failure
  8. The higher level business poitics that i am not good at seeing in the api space
  9. Api provider and consumer developer portals
  10. The higher level business politics that i am not good at seeing in the api space
  11. The role having awareness of your api traffic plays in api security
  12. Happy path api testing bias
  13. What is an appication
  14. What makes you think your graphql consumers will want to do the work
  15. What is an application
  16. The many ways in which apis are taken away
  17. Paying for api access
  18. Imperative declarative and workflow apis
  19. Hoping for more investment in api design tooling
  20. What is an api contract
  21. My primary api search engines
  22. Taking a fresh look at the nuance of api search
  23. Navigating api rate limit diffs between platforms
  24. The json schema tooling in my life
  25. Navigating api rate limit differences between platforms
  26. The details of my api rating formula
  27. Thinking differently when approaching openapi diffs and considering how to layer each potential change
  28. Why the open data movement has not delivered as expected
  29. Api interoperatibility is a myth
  30. Api interoperability is a myth
  31. Your api and schame is that complex because you have not done the hard work to simplify
  32. Your api and schema is that complex because you have not done the hard work to simplify
  33. The basics of my api ratings formula
  34. The complexity of api discovery
  35. The basics of my api rating formula

June 2019

  1. Why schema org does not see more adoption across the api landscape
  2. Avoiding complexity and ust deploying yaml json csv apis using github or gitlab
  3. Avoiding complexity and just deploying yaml json and csv apis using github or gitlab
  4. Organizing my apis using openapi tags
  5. Doing the hard work to define apis
  6. There is no single right way to do apis
  7. Api definitions are important
  8. Api evangelist is open for business

January 2019

  1. Stepping back from api evangelist

2018 468

November 2018

  1. Asking the honest questions when it comes to your api journey
  2. A diverse api design toolbox driving hybrid integrations in an event driven landscape
  3. A diverse api toolbox driving hybrid integrations across an eventdriven landscape
  4. The api journey
  5. Api management yaml artifacts from aws api gateway
  6. Yaml api management artifacts from aws api gateway
  7. What does the next chapter of storyteling look like for api evangelist
  8. What does the next chapter of storytelling look like for api evangelist
  9. The ability to link to api service provider features in my workshops and storytelling
  10. The ability to link to api service provider features in my workshops and
  11. Flickr and reconciling my history of api storytelling
  12. Flickr and reconciling my history of apis storytelling
  13. The impact of travel on being the api evangelist

October 2018

  1. What are your enterprise api capabilities
  2. Join me for a fireside chat at the paris api meetup this week
  3. I particiated in an api workshop with the european commission last week
  4. Join me for a fireside chat at the paris api meetup this wednesday
  5. I participated in an api workshop with the european commission last week
  6. Api evangelist api lifecycle workshop on api discovery
  7. Api evangelist api lifecycle workshop on api design
  8. The layers of completeness for an openapi definition
  9. A quick manual way to create openapi from a get api request
  10. A quick manual way to create an openapi from a get api request
  11. Api evangelist and streamdata io api lifecycle workshops

September 2018

  1. Api developer outreach research for the department of veterans affairs
  2. Having the dedication to lead an api effort forward within a large enterprise organization
  3. Having the dedication to lead an api effort forward within a large enterprise
  4. Understanding the event driven api infrastructure opportunity that exists across the api landscape
  5. Talking healthcare apis with the cms blue blutton api team at apistrat in nashville next week
  6. Understanding the eventdriven api infrastructure opportunity that exists
  7. Talking healthcare apis with the cms blue button api team at apistrat in
  8. Sadly stack exchange blocks api calls being made from any of amazons aws ip block
  9. Justifying my existence in your api funnel
  10. I am needng some evidence of how apis can make an impact in government
  11. Being open is more about being open so someone can extract vaue than open being about shared value
  12. Sadly stack exchange blocks api calls being made from any of amazons ip block
  13. Justifying my existence in your api sales and marketing funnel
  14. I am needing some evidence of how apis can make an impact in government
  15. Being open is more about being open so someone can extract value than open
  16. Providing minimum viable api documentation blueprints to help guide your api developers
  17. Please refer the engineer from your api team to this story
  18. Providing minimum viable api documentation blueprints to help guide your api
  19. Stack exchange has an api that returns the details for all of your access tokens
  20. Some ideas for api discovery collections that students can use
  21. Stack exchange has an api that returns the details for all of your access
  22. The path to production for va api applications
  23. An api value generation funnel with metrics
  24. The path to production for department of veteran affairs va api applications
  25. My api storytelling depends on the momentum from regular execise and practice
  26. Allowing users to get their own oauth tokens for accessing the api without the need for an application
  27. My api storytelling depends on the momentum from regular exercise and practice
  28. Allowing users to get their own oauth tokens for accessing an api without the
  29. What have you done for me lately api partner edition
  30. The federal agencies who use their developer domain gov subdomain
  31. The basics of the va api feedback loop
  32. Remembering that api are used to reduce everything down to a transaction
  33. What have you done for us lately api partner edition
  34. Remembering that apis are used to reduce everything down to a transaction

August 2018

  1. Why i feel the department of veterans affairs api effort is so significant
  2. Understanding where folks are coming from when they say api management is irrelevant
  3. Api portals designed for api provider and api consumer
  4. Understanding where folks are coming from when they say api management is
  5. Api portals designed for api provider and api consumers
  6. Trying to define an algorithm for aws api cost calculations across api gateway lambda and rds
  7. Reviewing the department of veterans affairs va new developer portal
  8. Not all companies are interested in the interoperability that apis bring
  9. Helping the federal government get in tune with their api uptime and availability
  10. Trying to define an algorithm for my aws api cost calculations across api
  11. Reviewing the department of veterans affairs new developer portal
  12. Helping the federal government get in tune with their api uptime and
  13. Provide your api developers with a forkable example of api documentation in action
  14. How do we get developers to follow the minimum viable api documentation guidance
  15. Do not miss internal developer portals developer engagement behind the firewall by kristof va tomme prvonix at apistrat in nahsville tn this september 24th 26th
  16. Provide your api developers with a forkable example of api documentation in
  17. How do we get api developers to follow the minimum viable api documentation
  18. Do not miss internal developer portals developer engagement behind the
  19. May contain nuts the case for api labeling by erik wilde api academy
  20. Living in a post facebook twitter and instagram api world
  21. How should teams be documenting their are new and legacy apis
  22. May contain nuts the case for api labeling by erik wilde dret api academy
  23. How should teams be documenting their apis when you have both legacy and new apis
  24. The importance of postman environment files
  25. Getting email updates from api providers i have signed up for is one way to stay in tune
  26. Any way you want it extending swagger ui for fun and profile kyle shcokey of smartbear software at apistrat in nashville
  27. The importance of postman api environment files
  28. Getting email updates from the api providers i care about is one way to stay
  29. Any way you want it extending swagger ui for fun and profit by kyle shockey
  30. Testing and meaningful mocks in a microservice system by laura medalia of care of at apistrat in nashville
  31. Searching for apis that possess relevant company information
  32. It is hard to go api define first
  33. Testing and meaningful mocks in a microservice system by laura medalia
  34. Identifying the different types of apis
  35. Describing your api with openapi 30 by anthony eden dnsimple at apistrat in nashville
  36. Algolia kindly provides a hacker news search api
  37. Describing your api with openapi 3 0 by anthony eden aeden dnsimple
  38. We need you api developers until we have grown to a certain size
  39. The redirect url to confirm selling your api in aws marketplace provides us with a template
  40. Microservicing like a unicorn with envoy istio kubernets with christian post of red hat at apistrat in nashville
  41. Having an api deprecation page like evrythng does
  42. The redirect url to confirm selling your api in aws marketplace provides us with a positive
  43. Microserviceing like a unicorn with envoy istio kubernetes with christian
  44. It isnt just because you have pdf api docs it is that it demonstrates you do not use other apis
  45. Bringing discovery within data api marketplaces out
  46. It isnt just that you have a pdf for your api docs it is because it demonstrates that you do not use other apis
  47. Bringing discovery within data api marketplaces out into the open
  48. Working with my openapi definitions in an api editor helps stabilize them
  49. Twice the does of vanick digital at apistrat in nashville tn next month
  50. I am speaking in washington dc at the blue button 20 developer conference on the api lifecycle this monday
  51. Twice the dose of vanick digital at apistrat in nashville tn next month
  52. I am speaking in washington d c at the blue button 2 0 developer conference
  53. Making sure my api dependencies include data provenance
  54. Sap and being late to the api game
  55. Automating inequality and apis

July 2018

  1. We need your help moving the asyncapi specification forward
  2. Practical secdevops for apis from 42crunch at apistrat in nashville this fall
  3. A service level agreement sla definition for the openapi specification
  4. The service level agreement sla definition for the openapi specification
  5. Thinking deeply about other people using your api is most valuable less with api design
  6. Monolithic serverless wtf
  7. Kicking the tires on the sap api business hub
  8. Avoid being captain obvious when documenting your api
  9. Thinking deeply about other people using your api is the most valuable lesson
  10. Discover profile quanity rank and publish new apis to the streamdata api gallery
  11. Api governance models in the public and private sector
  12. Discover profile quantify rank and publish new apis to the streamdata io
  13. Tvmaze uses hal
  14. If search for swagger or openapi does not work i try postman collection
  15. For every competitor you keep out of your api docs you are keeping twenty new customers out
  16. Concern around working with may github repositories
  17. Tvmaze uses hal for their api media type
  18. If a search for swagger or openapi doesnt yield results i try for a postman
  19. For every competitor you keep out of your api docs you are keeping twenty new
  20. Concern around working with many github repositories
  21. My api lifecycle checklist and scorecard
  22. Ping identity acquires elasticbeam to establish new api security solution
  23. Monetizing your device location data with lotadata
  24. I am sorry but your company is too big for me to talk to
  25. People do not use tags in their openapi definitions
  26. My moving towards a modern api lifecycle at post con 2018
  27. Long running api requests and differential api responses
  28. Json patch to articulate change for your api roadmap
  29. Using openapi and json patch to articulate changes for your api road map
  30. My moving towards a modern api lifecycle from postcon 2018
  31. Use plain language in api paths
  32. Operating your api in the cloud kill zone
  33. Love the api enthusiasm predix but publish an api style guide for your teams
  34. Concerns around managing many microservice repositories and going with a mono repo
  35. Using plain language in your api paths
  36. I love the api enthusiasm predix but please publish an api style guide for
  37. Concerns around managing many microservice repositories and going with a mono

June 2018

  1. Looking for sponsors for apistrat 2018 in nashville tennessee
  2. Rest api and graphql burger king
  3. Mayors and governors tech companies are getting rich mining your cities and consituents data
  4. Mayors governors and lawmakers tech companies are getting rich mining your constituents data
  5. Looking for sponsors for apistrat 2018 in nashville tn this september
  6. Graphql and rest differences explained with burgers
  7. Why is api versioning in the path still the dominant pattern
  8. Not liking openapi fka swagger when you have no idea what it does
  9. A public api platform as a competitive advantage
  10. A public selfservice api platform as a competitive advantage
  11. Staying informed of api changes using streamdata io
  12. Do not try to service all the stops along the api lifecycle as an api service provider
  13. Working to keep programming language dogma at edges of the api conversation
  14. Do not try to service all the stops along the api lifecycle as an api service
  15. Adding a lead to the salesforce rest api
  16. Adding a lead to salesforce using the rest api
  17. Va lighthouse landscape analysis and roadmapping project report
  18. The importance of openapi tooling
  19. Va api landscape analysis and roadmapping project report
  20. People still think apis are about giving away your data for free
  21. The rockstar commitees we have assembled to make apistrat nashville rock
  22. I will be discussing the government api lifecycle at devnationfederal in dc tuesday afternoon
  23. Catch me at dc api meetup in washington dc tuesday evening
  24. Making connections at the api management layer
  25. The rockstar committees we have assembled to make apistrat nashville rock
  26. I will be discussing the government api lifecycle at devnation federal in dc
  27. Catch me at the dc api user group in washington dc this tuesday evening

May 2018

  1. When the right api solutions is not always the sensible one
  2. How should we be organizing all of our microservices
  3. When the right api solution is not always the sensible one
  4. Apistrat nashville call for papers closes at the end of next weekk
  5. Apistrat nashville call for papers closes at the end of next week
  6. Micro procurement package for api monitoring and testing
  7. Api coordination and communication across federal government agencies
  8. A microprocurement package for api monitoring and testing
  9. Every moment is potentially an api story
  10. Api evangelist is partnering with bridge software to tell more api integration stories
  11. Api evangelist is partnering with bridge software to tell more api integration
  12. Cautiously aware of how apis can be used to fee government privatization machinations
  13. General services administration gsa needs help testing their fedbizopps api
  14. Opportunity for openapi driven open source testing performance security and other modules
  15. Api lifecycle seminars in new york city
  16. Opportunity for openapidriven open source testing performance security and
  17. Cautiously aware of how apis can be used to feed government privatization
  18. Nfl official api v2 simulations
  19. Using jekyll to look at microservice api definitions in aggregate
  20. Measuring value exchange in government using apis
  21. Looking at 20 microservices in concert
  22. Sports data api simulations from sportradar
  23. Measuring value exchange around government data using api management
  24. Api discovery is for internal or external services
  25. Api gateway as a node and moving beyond backend and frontend
  26. 1000 lb gorilla monolith and microservices
  27. Please do not make people afraid of the api contract
  28. Constraints introduced by standardizing api definitions
  29. Api design either provider does the work or the consumer does the work
  30. Making the openapi contract friendlier for developers and business
  31. Constraints introduced by supporting standardized api definitions and schema
  32. Api design either the provider does the work or the consumer will have to
  33. Turning the stack exchange questions api into 25 separate tech topic streaming apis
  34. Doing away with social logins due to a lack of trust
  35. Graphql just get out of my way and give me what i want
  36. Api management in real time as opposed to after the media shitstorm
  37. Turning the stack exchange questions api into 25 separate tech topic streaming
  38. Api management in realtime instead of after the media shitstorm
  39. Synthetic healthcare records for your api using synthea

April 2018

  1. Facebook and twitter only now beginning to police their applications
  2. A readme for your microservice github repository
  3. Facebook and twitter only now beginning to police their api applications
  4. Venture capital obfuscating the opportunities for value exchange at the api management level
  5. Existing processes and culture grinding down new api efforts
  6. Balancing virtual api evangelism with in person
  7. Venture capital obfuscating the opportunities for value exchange at the api
  8. Balancing virtual api evangelism with inperson api evangelism
  9. Delivering large api responses as efficiently as possible
  10. Machine readable api regions for use at discovery and runtime
  11. Rest and grpc side by side in new google endpoints documentation
  12. Openapi makes me feel like i have a handle on what an api does
  13. My response to the va microconsulting work statemtn on api outreach
  14. My response to the va microconsulting work statement on api landscape analysis and near term roadmap
  15. My response to the va microconsulting work statement on api outreach
  16. My response to the va microconsulting work statement on api landscape analysis
  17. If github pages could be turned on by default i could provide a run on github button
  18. Graphql thoughts after almost two years
  19. My graphql thoughts after almost two years
  20. Sharing api definition patterns across teams by default
  21. The closed api specification
  22. I will be speaking at the api conference in london this week
  23. Details of the api evangelist partner program
  24. Creating a productive api industry partner program
  25. Crafting a productive api industry partner program
  26. Nest branding and marketing guidelines
  27. Seamless api lifecycle integration with github gitlab and bitbucket
  28. Helping stoplight io get the word out about version 30
  29. Openapi is the contract for your microservice
  30. Github is you asynchronous microservice showroom
  31. Github is your asynchronous microservice showroom
  32. Openapi dependencies vendor extension
  33. The api stack checklist
  34. My api stack profiling process
  35. The api stack profiling checklist
  36. An openapi service dependency vendor extension

March 2018

  1. The openapi 30.gui
  2. Obtaining a scalable api definition driven api design workflow on github complete with api governance
  3. Using postman to explore the triathalon api
  4. Using postman to explore the triathlon api
  5. Obtaining a scalable api definition driven api design workflow on github
  6. The impact of availability zones regions and api deployment around the globe
  7. Sharing the apis json vision again
  8. A decade later twitters api plan slowly bgins to take shape
  9. Data driven apps at scale using github and jekyll
  10. A decade later twitters api plan slowly begins to take shape
  11. Oauth has many flaws but it is the best we have at the moment
  12. Sharing your api first principles
  13. Government has benefitted from lack of oversight at social api management layers as well
  14. Acknowledging why i do apis is very different than why others do apis
  15. Government has benefitted from lack of oversight at the social api management
  16. Acknowledging that why i do apis is very different than why others are doing
  17. Nexmo manages their openapi 30 definition using github
  18. A regulatory framework for facebook and other platforms is already in place
  19. Investment in api security will continue to fall short while there is no breach accountability
  20. Facebooks business model is out of alignment with their api management layer
  21. Investment in api security will continue to fall short while there is no
  22. Sendgrid managing their openapi using github
  23. Breaking down your postman api collections into meaningful units of compute
  24. Gdpr forcing us to ask questions about our data
  25. Facebook cambridge analytica and knowing what api consumers are doing with our data
  26. General data protection regulation gdpr forcing us to ask questions about
  27. Stops in a comprehensive api strategy transit map
  28. 68 stops in a comprehensive api strategy transit map
  29. A visual view of api responses within our documentation
  30. Linkedin account validation for new api consumers
  31. An openapi vendor extension for defining your api audience
  32. Rules for extending your api with each version
  33. Seeing messy api design practices as an opportunity
  34. Google releases a protocol buffer implementation of the fast healthcare interoperability resources fhir standard
  35. Multi lingual machine learning api deployments
  36. Api as a product principles at zalando
  37. Google releases a protocol buffer implementation of the fast healthcare
  38. Api as a product principles from zalando
  39. The importance of tags in openapi definitions for machine learning apis
  40. Some common api data types to put to use
  41. Thinking about delete and destroyting entities
  42. A machine readable baseline for api providers in my api stack work
  43. Thinking about api status codes for destroying entities using delete
  44. Defining the smallest unit possible for use at api runtime
  45. The postman api network
  46. Keeping track of federal government open source projects using the code.gov api
  47. Keeping track of federal government open source projects using the code gov
  48. A mock only api development reality
  49. Your obbsessive focus on the api resource is hindering meaningful events from happening
  50. Axway asking for an openapi of a streamdata io api so they can screenshot it
  51. Your obsessive focus on the api resource is hindering meaningful events from
  52. Imagine a mock only api development reality
  53. Axway asking for an openapi of the streamdata io api so they can screenshot it
  54. Where do we start the api conversation at our large organization
  55. Us companies getting ahead of eu regulations
  56. Explaining api security to organizational leadership
  57. Capital one devexchange provides an important banking api blueprint
  58. Serverless like microservices is about understanding our dependencies and constraints
  59. An openapi rules engine
  60. People seem to want lego kits and not a bucket of lego blocks
  61. The need for standardized api plans and pricing to compete with cloud providers
  62. The need for standardized api plans and pricing to compete with cloud
  63. Serverless like microservices is about understanding our dependencies and
  64. People seem to want lego kits and not a bucket of lego blocks when it comes to
  65. An openapidriven api governance rules engine
  66. Thoughts on the schema org webapi type extension
  67. An observable industry level directory of api providers and consumers

February 2018

  1. An open banking blueprint api portal
  2. What we need to be machine readable at api run time
  3. The business of running government as a microservices platform
  4. An open banking api portal blueprint
  5. What it the streamdata io api gallery
  6. Three areas i would like to cover when we sit down for an api consulting session
  7. Mapping out the api landscape
  8. What is the streamdata io api gallery
  9. Three areas i would like to cover when we sit down for an api consulting
  10. One of the best api getting started i have come across
  11. The banking api actors in the uk
  12. Department of veterans affairs lighthouse platform rfi round two
  13. Round two of the department of veterans affairs lighthouse platform rfi
  14. Aws iam like policies for aws api gateway and marketplace billing
  15. Provisioning a default app and keys for your api consumers on signup
  16. Open banking in the uk openapi template
  17. An opportunity around providing a common openapi enum catalog
  18. What is open banking in the uk
  19. An open banking in the uk openapi template
  20. Relationship between openapi path summary tags and asyncapi topics
  21. People who provide enum for their openapi definitions are good people
  22. Relationship between openapi path summary tags and aysncapi topics
  23. Insecurity around providing algorithmic transparency and observability using apis
  24. Using jekyll and openapi to evolve api documentation and storytelling
  25. Using jekyll and openapi to evolve my api documentation and storytelling
  26. Insecurity around providing algorithmic transparency and observability using
  27. The importance of the api path summary description and tags in an openapi definition
  28. A really nice api application showcase over at the intrinio market data api
  29. How big or small is an api
  30. Some common features of an api application review process
  31. The importance of the api path summary description and tags in an openapi
  32. Code generating openapi still prevailing approach
  33. The growing importance of github topics for your api seo
  34. Summary of aws api gateway as an api deployment and management solution
  35. Your microservices effort will fail because you will never decouple your business
  36. Your microservices effort will fail because you will never decouple your
  37. Code generation of openapi fka swagger still the prevailing approach
  38. A summary of aws api gateway as an api deployment and management solution
  39. Summary of kong as an api management solution
  40. Aggregating multiple github account rss feeds into single json api feed
  41. Having a developer yourdomain is clear differentiator in the api game
  42. Streaming and event driven architecture represents maturity in your api journey
  43. Streaming and eventdriven architecture represents maturity in the api journey
  44. A summary of kong as an api management solution
  45. More outputs are better when it comes to establishing an api observability ranking
  46. Labeling your high usage apis and externalizing api metrics within your api documentation
  47. Be clear about your api pricing
  48. A dedicated guest blogger program for your api
  49. More outputs are better when it comes to establishing an api observability
  50. Labeling your high usage apis and externalizing api metrics within your api
  51. You have to know where all your apis are before you can deliver on api governance
  52. Riot games regional endpoints
  53. Consistentency and branding across api portals
  54. Keeping api schema simple for wider adoption
  55. Riot games regional api endpoints
  56. Consistency in branding across api portals
  57. Api quota api webhooks and server sent events sse
  58. The more we know about you the more api acces you get
  59. Headers used for grpc over http2
  60. I appreciate you wanting to jump on the phone but i have other apis to test drive
  61. The more we know about you the more api access you get
  62. Learning about the headers used for grpc over http2
  63. I appreciate the request to jump on phone but i have other apis to test drive
  64. Api is not just rest
  65. A regulatory subway map for psd2

January 2018

  1. Shifting gears between the technology and politics of apis
  2. Where am i in the sales funnel for your api
  3. Helping understand that stream line data io is more than just real time streaming
  4. I want to be able to post and put and receive credits on my api bill
  5. Helping define streamlinedata io as more than just real time streaming
  6. The role of european banking authority eba in regards to psd2
  7. The role of european banking authority eba when it comes to psd2
  8. Key points from the payment services directive 2 psd2
  9. Aws api gateway openapi vendor extensions
  10. A health check response format for http apis
  11. Developing a microservice to orchestrate long running background server sent events
  12. Developing a microservice to orchestrate long running background serversent
  13. Docker engine api has openapi download at top of their api docs
  14. Five apis to guide you on your way to the data dark side
  15. Api management and the measurement of value exchange
  16. Api transit basics deprecation
  17. Breaking down the value of real time apis
  18. Api management and the measurement of value exchanged
  19. Api transit basics training
  20. Transit authorities need to understand that api management means more control and revenue
  21. The value of historical transit data when it comes to machine learning
  22. Moving beyond a single api developer portal
  23. Api transit basics support
  24. Providing a guest api key
  25. Transit authorities need to understand that api management means more control
  26. Api transit basics communication
  27. Can i resell your api
  28. Api transit basics security
  29. An organized approach to openapi vendor extensions across api teams
  30. Orchestrating api integration consumption and collaboration with the postman api
  31. Api life cycle basics testing
  32. Api life cycle basics sdks
  33. Aws has head start helping navigate regulatory compliance in the cloud
  34. Orchestrating api integration consumption and collaboration with the postman
  35. Api transit basics sdkst
  36. Api life cycle basics clients
  37. The metropolitan transportation authority bus time api supports service interface for real time information siri
  38. Api life cycle basics documentation
  39. Working with general transit feed specification gtfs realtime data
  40. Openapi will help you get your api house in order
  41. The metropolitan transportation authority mta bus time api supports service
  42. How do we keep teams from hoarding their data when doing apis
  43. Building an api partner program for streamdat io
  44. Api life cycle bsics portal
  45. Api life cycle basics dns
  46. Some of the thinking behind the protocols used by kafka
  47. We are not supporting open api fk swagger as we already published our docs
  48. We are not supporting openapi fka swagger as we already published our docs
  49. How do we keep teams from being defensive with resources when doing apis
  50. Building an api partner program for streamdata io
  51. Api life cycle basics portal
  52. Api life cycle basics api logging
  53. A blueprint for an augmented transit api
  54. Api life cycle basics api management
  55. The data behind the washington post story on police shootings in 2017
  56. Generating revenue from the support of public data using apis
  57. The child welfare digital services certification approval and licensing services api
  58. The child welfare digital services cwds certification approval and
  59. Seeing reflections from the past rippling in the api pool when translated wsdl to openapi
  60. Api life cycle basics gateway
  61. Looking for the answer instead of developing an understanding of good api design
  62. Api life cycle basics deployment
  63. I created an openapi for the hashicorp consul api
  64. Understanding events across your api platform in real time
  65. Seeing reflections from the past rippling in the api pool when i translated
  66. Looking for the answer instead of developing an understanding of good api
  67. Api discovery can just be about you sharing stories about the apis you depend on
  68. Api life cycle basics mocking
  69. Keeping things in the club by drowning api complexity
  70. Keeping things in the club by drowning everyone in api complexity
  71. Api transit basics mocking
  72. Api discovery is mostly about you sharing stories about the apis you use
  73. Api life cycle basics database
  74. Api life cycle basics api design
  75. The transit feed api is a nice blueprint for your home grown api project
  76. Alexa voice skills is the poster child for your enterprise api efforts
  77. The api transit basics api definitions
  78. Api transit basics api design
  79. Api transit basics api definitions
  80. Alexa voice skills are the poster child for your enterprise api efforts
  81. My evolving definition of a robust and diverse api toolbox
  82. Treating all apis like they are public
  83. The national transit database ntd needs to be an api
  84. Api transit the basics

← 2016–2017 2020–2026 →