> ## Documentation Index
> Fetch the complete documentation index at: https://docs.invoca.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot UK local promo number order rejections

> Match a rejected UK local promo number order to the HTTP status and message the Network Integration API returns.

**Network users who order UK local promo numbers with the Network Integration API can match a rejected call to the HTTP status and message Invoca returns.**

Send the order with [Order UK local promo numbers via API](https://docs.invoca.com/s/article/order-uk-local-promo-numbers-via-api.md). Invoca returns the first failing check only. Field tables and the check order are in [UK local number orders](https://docs.invoca.com/en/latest/api_documentation/network_integration/promo_numbers/index.md#uk-local-number-orders).

## Before you begin

* You have the HTTP status and the error body from the failed UK local order.
* You use the same API credentials as that order call.

## Fix an HTTP 401 or HTTP 404 on a UK local order

* **HTTP 401.** Invoca did not accept the credentials. This is the shared Network Integration API challenge (HTTP Basic), not the `errors` object used by 403, 404, and 422. Send the API token the same way as your other Network Integration calls. [Manage API Credentials](https://docs.invoca.com/en/latest/api_documentation/manage_api_credentials.md) documents the `Authorization` header.
* **HTTP 404.** The advertiser or advertiser campaign in the URL does not exist. The body is `{"errors":{"class":"RecordNotFound","invalid_data":"<message>"}}`. `id_from_network` is the identifier your network assigned. The URL uses that value, not Invoca's internal id.

## Fix an HTTP 403 on a UK local order

Invoca runs this check after authentication and before the affiliate and locale errors. A paused, not-live, suspended, or otherwise unauthorized campaign returns HTTP 403 even when the country is not the UK or the body includes `affiliate_id_from_network`.

`errors.invalid_data` is one of these strings. `<name>` is the advertiser or advertiser campaign name.

* `Promo Numbers cannot be assigned to syndicated campaigns`. A syndicated campaign gives your publishers access to a campaign that runs on another network. Order on an advertiser campaign that is not syndicated.
* `This advertiser campaign, <name>, is paused and you can no longer add promo numbers`. Unpause the campaign, then order again.
* `This advertiser campaign, <name>, is not live yet. Please go live with this campaign before requesting promo numbers.` Set the campaign live, then order again.
* `This advertiser, <name>, is suspended and you can no longer add promo numbers`. Contact Invoca to restore the advertiser.
* `Promo numbers are not allowed for this advertiser`. Contact Invoca if this advertiser should have promo numbers.

## Fix an HTTP 422 on a UK local order

HTTP 422 uses `{ "errors": { "<key>": ["<message>"] } }`.

| Key | Message | What to do |
| - | - | - |
| `affiliate_id_from_network` | `promo number orders are only available for the advertiser campaign` | Order on the advertiser campaign. Remove `affiliate_id_from_network`. |
| `locale` | `promo number orders are only available for UK campaigns` | Use a UK campaign. Invoca does not look up the city or area code. |
| `city` | `city must be a string` | Send `city` as a string. |
| `area_code` | `area_code must be an integer or a numeric string` | Send digits only. A whitespace-only value fails this check. An empty string counts as missing, not invalid. |
| `city` | `Specify exactly one of 'city' or 'area_code', not both` | Remove either `city` or `area_code`. |
| `city` | `Specify exactly one of 'city' or 'area_code'` | Send one of `city` or `area_code`. |
| `count` | `Total requested count (N) exceeds maximum of 100` | An integer over 100. Invoca returns this before lookup. Send 100 or fewer in this call. |
| `count` | `count must be between 1 and 100` | Use an integer from 1 to 100. A numeric string such as `"5"` is valid. |
| `city` | `City '<city>' not found in UK area code database` | Use a city name from the UK area-code data. |
| `area_code` | `Area code '<area_code>' not found in UK area code database` | The message quotes the value you sent. Use a known UK dialing code. |
| `city` or `area_code` | `Your network has reached its promo number limit based on its current allocation. To request more promo numbers, please contact us.` | The last words are your network's contact-support text, or a link to it. Contact [Invoca](https://support.invoca.com/s/) to request a higher limit. |
| `city` or `area_code` | `Number allocation failed` | Invoca could not save the order. Contact Invoca if this repeats. |
| `city` or `area_code` | `Number allocation did not produce an allocation request` | Invoca saved no allocation request for this call. Contact Invoca if this repeats. |

> **Note:** Invoca returns the promo number limit on `city` when the request has no area code, and on `area_code` otherwise. That check runs before the Google Call Extension checks.

These rows are AdWords (Google Ads) account checks. An omitted `media_type` counts as not `Google Call Extension`. The message contains the text in the Message column.

| Key | Message | What to do |
| - | - | - |
| `adwords_account_id` | `must exist as an account in your AdWords integration` | Send an AdWords (Google Ads) account that is in the campaign owner's integration. |
| `media_type` | `requires a Google Ads account be set` | You sent `Google Call Extension` and no account was sent or defaulted. Include `adwords_account_id`. |
| `media_type` | `cannot be Google Call Extension unless you are integrated with AdWords` | The campaign owner is not integrated with AdWords (Google Ads). Do not send `Google Call Extension` or `adwords_account_id`. |
| `adwords_account_id` | `can only be set when media type is 'Google Call Extension'` | Send `adwords_account_id` only with media type `Google Call Extension`. |

If a rejection persists, contact [Invoca](https://support.invoca.com/s/).


## Related topics

- [Order UK local promo numbers via API](https://docs.invoca.com/s/article/order-uk-local-promo-numbers-via-api.md)
- [Promo Numbers](https://docs.invoca.com/developers/2026-02-01/api_documentation/network_integration/promo_numbers/index.md)
- [International Number Support](https://docs.invoca.com/s/article/international-number-support.md)
- [How to Create Static Promo Numbers via API](https://docs.invoca.com/s/article/create-static-promo-numbers-via-api.md)
