One API for a Website and a Mobile App: Lessons from auto-data.net

One API for a Website and a Mobile App: Lessons from auto-data.net

auto-data.net is a catalogue of technical specifications for more than 57,000 cars. It has a website in many languages, an Android and iOS app, and a paid API that other websites and software use to get the data. All of it runs from one database.

One database, three ways in

  • The website shows the data as pages for makes, models, generations and versions.
  • The app calls API endpoints – menu, search, car data – and receives only the data, without HTML.
  • The paid API gives clients access with keys, limits and usage statistics.

When a new car is added or a value is corrected, the change is visible everywhere at once. There is no second database for the app to keep in sync.

A story about languages

A user in Italy wrote that they had chosen Italian in the app, but it stayed in English. The cause: on the website, the list of regional language codes had been extended – instead of just "it" there was now "it, it-IT, it-CH". The app's API looked for exactly "it" and did not find it.

The fix was to normalise the language code at the entry point: "it", "it-IT", "it_IT" and "it,it-IT" all resolve to the same code, and for languages where the site's code differs from the standard one (for example gr and el for Greek), both are checked.

The lesson: a change on the website can break the app if they share data. The API has to accept input flexibly, and you need tests with real devices in different languages.

App versions

A website updates for everyone at once; an app does not. People use old versions for months. So:

  • the API stays backwards compatible – old versions get data in the old format;
  • the app reports its version, and the server can show an update message;
  • new fields are added without removing or renaming old ones.

When this approach pays off

If you have a website with data – products, listings, schedules, prices – and are thinking about an app, the right first question is what the API will look like. Done well, it serves your website, your app and your partners at the same time. See mobile apps and web-based software, or get in touch.

← All articles

Have an idea for a website, app or system?

Tell us briefly what you need – we will get back to you for a short call and a clear quote.