API changelog

Dated changes to the Tapper REST API that your API keys call, newest first, so an integration can see what changed and when.

This page lists changes to the REST API that API keys call (https://api.tapper.ai/v1/links), newest first.

15 October 2026: an unknown location is refused

When you create or update a link (POST /v1/links and PUT /v1/links/:id), every locations[].id in every rule must match a country or a continent. An id that matches nothing is refused with a 400, and nothing is saved.

Before this change, an unknown id was skipped silently, so the rule was saved without the location filter you asked for and matched every visitor.
The error has the code LOCATION_NOT_FOUND and names the field, for example rules[0].locations[1].id.
A country id is an ISO 3166-1 alpha-3 code, such as USA. A continent id is one of Africa, Antarctica, Asia, Australia, Europe, North America, Oceania or South America.

15 October 2026: UPPER values for device types, operating systems and location types

When you create or update a link (POST /v1/links and PUT /v1/links/:id), three lists in each rule take UPPER values, the spelling Tapper uses everywhere else:

Field	UPPER values
`device_types`	`DESKTOP`, `MOBILE`, `TABLET`, `OTHER`
`oses`	`WINDOWS`, `MACOS`, `LINUX`, `IOS`, `ANDROID`, `OTHER`
`locations[].type`	`COUNTRY`, `CONTINENT`

The lowercase values (mobile, ios, country and so on) keep working and give the same result as their UPPER twins. You can mix both in one request.
Use UPPER in new code.
Any other spelling, such as Mobile or tv, is refused with a 400.
No response from the API returns these values, so there is nothing to change on the reading side.
week_days was already UPPER (MONDAY to SUNDAY).