Skip to main content

API Keys: Allowed Networks and Key Checks

Level: Beginner · Category: API reference

Tags: API keys · Allowed networks · Security

Anyone who has your API key can use it as you. This page covers the settings on the Keys tab in the Voyager portal that limit the damage if a key is copied: where a key may be used from, and where it was last used. It also explains what Research Computing staff check on their side. To create a key, see How to Request an API Key.

What a key looks like​

Keys from the current gateway start with obl_. Keys marked Legacy on the Keys tab come from the older gateway; they can't use allowed networks, so click Rotate to get a current key first. Rotating keeps the old key's allowed networks.

Allowed networks​

Each key can have a list of allowed networks: the IP addresses or address ranges it may be used from. A request with the key from anywhere else is refused, so a copied key is no use outside the places you listed. An empty list means the key works from any network, which is the default.

Set them on a new key​

  1. On the Keys tab, click Create API key.
  2. In the Create an API key dialog, fill in Allowed networks, or leave it empty to allow any network.
  3. Click Create key.

Change them on an existing key​

Under each key, Voyager shows Allowed from any network or Allowed only from followed by the list (or the number of networks, when there are more than two). Legacy keys don't show this line. Click Edit next to it. In the Allowed networks for dialog, change the list and click Save. To remove the limit, empty the list and save; the key then shows Allowed from any network again.

What to type​

Put one network or IP address per line (commas work too), for example:

10.20.0.0/16
203.0.113.7
  • A network is written as an address and a prefix length, such as 10.20.0.0/16. A single address, such as 203.0.113.7, means only that address.
  • IPv6 works the same way, for example 2001:db8::/32.
  • A key can have at most 64 entries.
  • Voyager checks each line as you type and won't save a line that isn't an address or network.

Only our institution's networks​

The Only our institution's networks button fills the list with ASU's networks: the private campus network, the ASU VPN, and ASU's public internet addresses. It replaces whatever is already in the box. This covers machines on campus, Research Computing clusters, and laptops connected to the VPN. If a request from somewhere you expect is still refused, the error names the address to add.

Choosing a setting​

  • One key per place. Give each script, server, or app its own key, named for where it runs (for example "Lab server" or "Laptop"). Then each key can have the narrowest list that works, and you can rotate one without breaking the others.
  • Campus machines and clusters: use Only our institution's networks.
  • Working from home without the VPN: your requests come from your home internet address, which is not an ASU network, so a key limited to ASU networks is refused. Either connect to the VPN first, or add your home address. Home internet addresses can change without notice, so if a key that used to work starts being refused, check the address named in the error (see below) and update the list.
  • Cloud services such as AWS (Lambda, EC2), Supabase functions, or GitHub Actions send requests from addresses that change from one run to the next, often across many networks. A short list will refuse them at random. For these, leave the key unlimited (an empty list), and keep it in the service's secret store rather than in code.
  • Leave it unlimited when you can't predict where the key will be used from. The key still works everywhere; protect it by keeping it out of code, shell history, and shared files, and rotate it if it may have been exposed.

When a request is refused​

A request from outside a key's allowed networks fails with HTTP 403. The message names the address the request came from:

{"error": {"message": "This API key can't be used from 203.0.113.9. Its owner limited it to certain networks.", "type": "obleth_gateway_error", "param": null, "code": "ip_not_allowed"}}

If the address is one you expect to use, add it (or its network) to the key's list. If the gateway couldn't tell where the request came from, the message says an unknown address instead.

A key that has been deactivated is refused everywhere with 403 api key disabled. Create a new key on the Keys tab. If you didn't deactivate it, your account may be locked; check Voyager or contact us.

Every error the API can return is listed in Limits and Errors.

Where a key was last used​

Under each key, Voyager shows where it was last used, for example:

Last used from 203.0.113.7 (Germany) on Nov 14, 2026
  • Traffic from ASU's private campus network or the VPN usually shows a private address with on campus or unknown in place of a country.
  • Requests made before Nov 14, 2026 may show an internal 10.42.x.x address in place of the real one.
  • No recent use with a known address means the key hasn't been used in the last 90 days, or its recent requests came without an address. Legacy keys always show this.

If the address or country doesn't look like you or your apps, rotate the key and contact us.

Key checks by Research Computing​

Research Computing staff review AI API key use to catch keys that may have leaked or been forgotten. They look at:

  • Unusual use, such as a key used from a new country outside the US, or from many different networks in one day.
  • Keys of people who have left ASU.
  • Keys that are still being tried after they were turned off, which usually means a script or app somewhere still has the old key.

If something needs your attention, a member of staff may contact you. These checks are reviewed by people: they do not send automatic emails or turn keys off on their own.