API Factory

Show & Tell 3

27th March 2019

Why are we doing this?

  • Hackney have produced 8 APIs so far which are using service specific dataset
  • We do not have data driven microservice architecture in place.
  • The 8 APIs were completed before we had published our API standards
  • We now want our APIs to meet our playbook standards and follow our API first strategy.

In other words, we’re better organised than ever and we want to bring our open APIs up to our new standards


What’s our vision?

We want to build open APIs so good that people prefer to use them. This means our work has to result in secure, reusable, uniform and scalable code. The services we provide will be resilient and have a knowledgeable, enthusiastic team maintaining and improving them. Along with our partners, we will provide our users with the most effective, efficient service possible.


Who are we doing this with?














What does the long term look like?

  • Three clear areas to investigate and define:
    • Best tools and database for the new platform
    • Reliable and resilient sync process to bring relevant data from UH (and in the future other sources) into new platform
    • Understanding source data to form a new schema which enables better scalability and support of new platform
  • Overall aims remain the same - to get our APIs ship shape and to be the primary source of housing data


What are we tackling now?

Mastering housing data

  • What will it do?
    • Will provide a means to ‘master’ housing data
    • Be as up to date as possible
  • What have we done?
    • Fixed a pretty big bug which prevented us from getting data in the correct format
  • What’s next?
    • Understanding current UH data and flows so that we can progress a new schema design with appropriate data mapping in place.


What are we tackling now?

Property information API

The Uh simulator now based on ‘uhlive’ schema instead of staging.

      • +500 new tables not in staging
      • Hundreds of new columns


    • Get Property info endpoints

ie. “property/{property-ref}”


What are we tackling now?

Transactions API

  • What will it do?
    • Provide transaction data for leasehold and tenant accounts to services
    • Can be consumed by other APIs
  • What have we done?
    • Worked out exactly what the most used transaction data in UH is
    • Established which fields need to be calculated
    • Set up Swagger
    • Shared our findings and agreed solution with the rest of the team
  • What’s next?
    • Finish implementing the agreed solution


What’s next?

  • Kick off the next API (Customer information).
  • Produce our first bits of documentation around how we will implement the first stage of mastering housing data.
  • Identify key competencies to upskill dev team members on.
  • Create baseline and assess skills.
  • Upskill dev team members on how to architect
  • Upskill dev team in setting up APIs from scratch.




API Factory - Show & Tell 3 - Google Slides