Skip to main content
Neo normally holds your vendor keys and calls the vendor directly. With an API proxy route, Neo sends one integration’s calls to a reverse proxy you run, such as a Cloudflare Worker. The proxy holds the real keys and Neo stores only placeholders. If Neo were ever breached, the attacker would find no key that works anywhere else, and you can log, filter and stop every Neo call at your proxy. The emergency stop stops Neo from inside Neo. A proxy route is the switch you hold outside it.

How a routed call travels

When you route an integration, Neo changes only where its calls go:
The vendor’s host becomes the first part of the path after your proxy URL, so one proxy serves every vendor. Each call carries the authentication headers your proxy checks, and the vendor’s keys travel exactly as they always do, but as placeholders. Your proxy checks the headers, swaps the placeholders for the real keys and sends the call on. For example, a Huntress call. Huntress authenticates with Authorization: Basic, the base64 of <API Key>:<API Secret>. Neo stores the placeholder neoproxy_huntress_api_secret in place of the API Secret, so it sends:
Your proxy checks and removes X-Neo-Proxy-Key, decodes the Basic value, replaces the placeholder with the real API Secret, encodes it again, and sends:
Each integration’s Setup tab shows the same example for that integration, with your proxy URL filled in. Links the vendor returns, such as the next page of a list, come back through the same route.

Integrations you can route

The integration’s Setup tab shows the same facts for that integration, with its entries for the reference Worker ready to copy. Keep each vendor’s own URL in its Setup fields (the Datto RMM URL, the IT Glue API URL, the Ingram Micro API URL). Neo routes calls by the vendor’s host, so a URL on another host is not routed.

Set it up

1

Deploy your proxy

Deploy the reference Worker below, or your own proxy that follows the same contract. Give it your real vendor keys as secrets, a recipe for each vendor you route, and the check of Neo’s authentication headers.
2

Turn on the proxy in Neo

Open the integration in Integrations. On its Setup tab, turn on Send … calls through your own API proxy. Enter your Proxy URL, pick how your proxy checks it is Neo, and enter the header values. Only an Owner or Admin can do this.The vendor’s secret fields leave the form while the switch is on: Neo stores the placeholders there itself. The other fields, such as the Huntress API Key or the Datto RMM URL, stay.
3

Save

Neo first checks the connection through your proxy, with the placeholders, before it stores anything. If the check passes, Neo replaces the stored keys with the placeholders and turns the route on. If it fails, for example because your proxy is unreachable, refuses Neo’s headers, or the vendor rejects the key after the swap, nothing changes: the integration keeps working directly, and the error says which step failed.
Every owner and admin gets an email when someone sets, changes or removes a route, and the change goes on that person’s Activity History. New header values on the same proxy URL keep the placeholders. A new proxy URL deletes the keys again. To stop routing, turn the switch off, type the vendor’s real keys in the fields that come back, and save. Neo checks the real keys directly first; only when that passes does it store them and remove the route. Neo also refuses to send a call to your proxy that would carry a real key of that integration, so a real key never reaches a proxy, even for a moment during a change.

How Neo authenticates to your proxy

Proxies check different headers, so you name them: one to three headers, each a name and a secret value. One value must be at least 24 characters with no spaces. Neo never sends a name the vendor’s own calls use, such as Authorization, and refuses one when you save. An IP allowlist alone does not protect your proxy: every Neo customer sends from the same IP addresses, so another Neo account could name your proxy URL. Use it beside a header, as the reference Worker’s NEO_IPS does. The public API lists the routes at GET /public-api/integrations/api-proxy. Only a signed-in admin or owner changes a route, so that the change goes on their Activity History: use the switch on the integration’s Setup tab. An API key cannot set or remove a route. The Neo Support Agent can show your routes and remove one after you approve, and it never sets a route, because the header values would pass through the chat.

Reference Cloudflare Worker

This Worker:
  • refuses every call while KILL_SWITCH is on, so one setting cuts Neo off from every routed vendor
  • checks the X-Neo-Proxy-Key header against your secret
  • optionally accepts calls only from Neo’s IP addresses
  • serves only the vendor hosts in its recipes, so it is no open proxy
  • swaps a placeholder only where the recipe says, so a ticket note that quotes a placeholder never receives a real key
  • keeps a vendor’s redirect on the proxy when it points at a host the Worker serves, and passes any other redirect back unchanged
  • logs each call’s method, vendor host, path and status
Set these in the Worker’s Settings → Variables and Secrets: A recipe names, per vendor host, the placeholders it swaps and where: headers (header names), basic (inside Authorization: Basic), query (query parameter names) and bodyPaths (paths of token or login calls whose form or JSON body holds a placeholder).
RECIPES
neo-proxy.js

What a route protects, and what it does not

  • A breach of Neo yields no working vendor key. It still yields your proxy URL, your authentication header values and the placeholders, so an attacker who controls Neo could call your vendors through your proxy until you switch it off. The NEO_IPS check limits such calls to Neo’s own addresses, and your proxy’s log shows each one.
  • A token Neo gets through the proxy is real. For Datto RMM and Ingram Micro, the token call goes through your proxy, and the vendor answers with a short-lived access token that Neo then holds until it expires.
  • Vendors that allowlist Neo’s IP addresses see your proxy’s address instead. A Cloudflare Worker calls vendors from Cloudflare’s shared addresses. If a vendor accepts only listed addresses, run your proxy where it has fixed outbound addresses and list those at the vendor, or keep that vendor off the proxy.
  • A customer’s own key goes to the vendor directly. The route carries your own connection to the vendor. Neo stores a customer’s own key and checks it as it always did.
  • A route change reaches new runs within about 10 seconds. A run already going keeps the route it started with.

Integrations a proxy cannot cover

Some integrations hold no key you type in Neo, or send it to a host other integrations share. Cut those at the vendor:
  • Microsoft 365, Microsoft Graph and Exchange Online: Neo calls Microsoft with its own app and your consent. Remove or disable the Neo app in Microsoft Entra to cut it.
  • NinjaOne, Xero and QuickBooks Online: Neo holds a token from the sign-in you approved. Revoke Neo’s access in the vendor’s app settings.
  • Autotask: every Autotask call carries Neo’s own Autotask integration code, which your proxy would see, so Neo does not route Autotask. Cut it at Autotask: set Neo’s API user to inactive.
  • CIPP: its client secret goes to Microsoft’s sign-in service, which Neo cannot route per integration. Rotate or remove the CIPP app’s client secret in your own Entra to cut it. Its API URL field already accepts a proxy address for the API calls themselves.