Skip to main content
You connect one RoutIT or KPN API interface per Neo workspace. Neo then reaches every customer card of that account.

​
1. Get your API interface

1

Open the Grexx portal

Sign in to the Grexx portal of your RoutIT or KPN account. If you have no API access yet, ask your RoutIT or KPN account manager for an API user.
2

Copy the webservice URL

Open the API Toolbox and the interface’s API gegevens. Copy the webservice URL, such as https://service.grexx.today/interfaces/routit/<name>/<id>. A URL that ends in /realtime is fine: Neo removes it.
3

Copy the API user

Copy the API user name. Grexx emails the password, or your account manager gives it to you.

​
2. Whitelist Neo

Grexx answers only addresses that are whitelisted for the interface. Add all of Neo’s IP addresses to the interface in the Grexx portal, or ask Grexx to add them. Neo’s customer mapping and seat changes need the customer and order messages on the interface: ask RoutIT or KPN to allow them if they are not.

​
3. Add the login in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations and find the RoutIT / KPN card, under Cloud Marketplace.
2

Save the login

Paste the webservice URL, pick the sign-in method, enter the API user name and password, and click Save settings. Grexx interfaces take either Basic authentication or an OAuth 2.0 token. If you are not sure which yours takes, pick one: Neo reads one customer card before saving, and when the method you picked is refused and the other works, the message tells you to pick the other.
If the API user’s password changes in Grexx, Neo loses access until you save the new one here.

​
4. Check the customer mapping

Neo matches each customer card to a PSA company by name. Open the RoutIT / KPN card’s Organization Mapping tab to correct a match, confirm a suggested one, or map a company by hand.

​
5. Turn on seat changes

Add Change License Seats and List License Subscriptions to your onboarding and offboarding agents. In Change License Seats, turn on Require technician approval if a technician should confirm each seat change. Ask your Neo Support Agent to set this up: for example, “When someone joins, ask the technician which licence to add and add the seat on RoutIT; when someone leaves, remove the seat.” A seat change on RoutIT / KPN applies now. To lower seats at a licence’s renewal, schedule the agent to run on the renewal day.

​
6. Turn the RoutIT / KPN API on per agent

For everything beyond seat counts, open the agent, go to its Tools & Settings tab, click Cloud Marketplace, and expand the RoutIT / KPN block. Pick one of its Presets, or set each area yourself: Always asks, whatever the preset: ending an order or a customer, a customer card update, SIM and number swaps, a port-out agreement and contract end dates, the Microsoft agreement attestation, and every write that sets a password, PIN, PUK, security or porting code. See RoutIT / KPN API for what the agent can read and change.