API Deprecation Building Blocks

As I study the API space, and profile the companies, services, and tooling I come across I'm always looking for the common building blocks in use across API operations. These are derived the features, and valuable elements of API operations, and the companies who are servicing this particular area of the API space.

  • Types
    • Individual API Endpoints -
    • Individual API Tooling -
    • Entire Platform Shutdown -
    • Enter Platform Safe Mode -
  • Runway
    • Initial Expectation Set -
    • Legal Department -
    • First Decision -
    • First Notice -
    • Lock-down New Signups -
    • Lock-down New Writes -
    • Light Switch Flicking -
    • Other Milestones -
    • Final Date -
  • Communication
    • Key Players -
    • Public Players -
    • Schedule (Runway) -
    • Historical -
    • Be Real -
    • Be Friendly -
    • Be Transparent -
    • Be Respectful -
    • PR Campaign -
    • Communicate Often -
  • Tooling
    • Data Migration -
    • Settings Migration -
    • Data Sync -
    • Data Portability -
  • Licensing
    • Data License -
    • Server Code -
    • Client Code -
    • API License -
  • Virtualization
    • AWS AMI -
    • Heroku Deploy -
    • Docker Image -
  • Management
    • Github Repo -
    • Github Issues -
    • API Purgatory -
    • X-API-Warn -
  • Support
    • Contact Person -
    • Migration Partners -
    • Migration Locations -

These building blocks are constantly being added to and reorganized. If there is something you think should be here feel free to let me know. Remember that this represents my living research, and will evolve, expand and actually seed new research areas as I find the time to pay attention to API testing.