---
title: "Suggest current places for stale location targeting"
type: reference
method: GET
path: /rest-api/targeting/stale-locations/suggestions.do
tag: "Targeting Rules"
---

# Suggest current places for stale location targeting

`GET https://YOUR-NETWORK-DOMAIN/rest-api/targeting/stale-locations/suggestions.do`

For every stale place the list would show, what it is called now, from names and the answers the server already holds: this never calls the AI model (POST to the same path for that). Rules naming the same stale place with the same include or exclude form one group, with its 'targetIds', how many rules of each kind and how many entities of each level carry them. 'suggestion.action' is REPLACE (apply with POST replace.do: targetIds, countryCode, regionName, cityName as the suggestion gives them), REMOVE (no current place matches, and removing the rules changes nothing: POST remove.do) or KEEP (nothing is proposed: removing the rules would change delivery, or the geo service did not answer for the place; the user decides). A city whose region is gone is looked for under up to 80 of the country's regions; where the country has more, not finding it there is a NO_SUCCESSOR of LOW confidence. 'reason' is SPELLING, SUFFIX (an administrative word such as "County" or "Stationsby" dropped), REGION_RENAMED, RENAMED, MERGED, NO_SUCCESSOR, NOT_MATCHED, COUNTRY_RULE or GEO_UNANSWERED, with 'reasonParams' (old name, new name) and 'reasonText' in the user's language; 'confidence' is HIGH, MEDIUM or LOW; 'source' says whether names (DETERMINISTIC) or the AI assistant's model (AI) matched it. 'ai' is NOT_NEEDED when every place was answered, otherwise SKIPPED, and the places left open read NOT_MATCHED. Nothing is changed. Requires MANAGE_DEMAND_TARGETING or MANAGE_SUPPLY_PRE_TARGETING.

## Responses

- `200` — {success, status: OK|GEO_UNAVAILABLE, unavailable, message, ai, aiMessage, groups:[{type, value, place, rule, targetIds, kinds:{SAFE, OPENS_ALL, STARTS_DELIVERY}, entities:{ADVERTISER, CAMPAIGN, BANNER, SITE, ZONE, PLACEMENT}, suggestion:{action, countryCode, regionName, cityName, newPlace, reason, reasonParams, reasonText, confidence, source}}]}
- `400` — Bad request — invalid or missing parameters
- `401` — Authentication error
- `403` — The role lacks both MANAGE_DEMAND_TARGETING and MANAGE_SUPPLY_PRE_TARGETING

## Example request

```bash
curl --request GET \
  --url 'https://YOUR-NETWORK-DOMAIN/rest-api/targeting/stale-locations/suggestions.do' \
  --header 'X-Api-Key: YOUR_API_KEY'
```

Source: https://epom.com/ad-server/docs/api/targeting-rules/get-targeting-stale-locations-suggestions