top of page
  • Writer's pictureNick Lansley

100% Martini / Affiliates Scheme Starts / API Unscheduled Outage

This morning I sent this message out to our 800+ registered Tesco Grocery API developers.

Dear API Developer

We did it (finally!) – 100% of customers are now on our new ‘Project Martini’ grocery development platform. That means that 100% of customers can use your applications that use the Tesco Grocery API at It also means that we are can switch on the affiliates “percentage contribution to checked-out order” pot for T-JAM attendees on 1st August 2010 – we’re just making sure all the logging is working correctly first.

We’ve been working madly to make sure the API is stabilised on Martini and we’ve been tuning up the performance of the service, particularly dealing with customers with very large baskets that was slowing down such API commands such as Login.

The RESTful API endpoint is already up to v1.0.0.15 and there will be updated documentation for that latest version being published this coming weekend. The latest API updates include a ‘FAST” mode which speeds up API responses for getting Basket information if you don’t need all the basket information that normal response returns.

Hands-up: we’re sorry – our developer portal database ran out of log space during maintenance late yesterday and stopped the API from authorising access. Regrettably the API health page did not detect this (as it bypasses authorisation) and it was only uncovered by emails from some pretty annoyed developers when I woke up this morning.

I’ve fixed the problem by: 1) Emptying the log and 2) Removing size restriction on it. The disk on which the database log is saved has acres of space and the restriction was placed on it over 18 months ago when it existed on an earlier smaller server.

I will change the API Health page today so that it tests using a developer key that requires authorisation for each test. That way we’ll also monitor if the forum database is in error. I will also put on our change list a code change to give developers the benefit of the doubt and always authorise access to the API if that database goes on error again. The Health page sends out alerts every time a test yields a ‘red’ or ‘black’ result (serious error or timeout). This all means that it shouldn’t happen again without us knowing pretty quickly.

From Monday 26 August we will be ‘living’ in the Innovation Support Forum answering questions and listening to any concerns. I really want to energise the forum again – you’ve been more than patient while we’ve got Martini to 100% and tuned up the API, so it’s about time we spent some time with you.

After all – on 5th August it will have been a year since T-JAM. Wow!

Best regards Nick Lansley

3 views0 comments

Recent Posts

See All

OpenAI's poetry writing shows the power of GPT-3 models

AI is getting good! I have joined OpenAI's beta programme with access to their GPT-3 AI service, and I asked it to write me a poem. My exact brief: "Write a poem the explores our love of our home in t


Post: Blog2_Post
bottom of page