Connect KPN to Conduit

Paste the client ID and secret from the Grexx portal (API Gegevens). This connection uses KPN’s Grexx test environment (acceptatie).

Before you start

You need:

• A Conduit role that can manage connections — owner or admin on your organization.
• The client ID and client secret from the Grexx portal (API Gegevens).

You do not choose a URL on this form. This connection already points at the Grexx test environment.

Connect KPN in Conduit

1. In Conduit, go to Connections (/org/catalog).
2. Find KPN (under Network, marked Preview) and click Connect.
3. Fill the fields:
   • Client ID (Grexx username)
   • Client secret (Grexx password)
4. Click Connect. A bad pair is rejected here. A good pair shows Connected.

The credential is stored for the organization, so every technician in the org shares this KPN connection.

What you can call

Fourteen lookups that only read data, and one action that changes something.

Address and availability:

• Test connection — checks that the client ID and secret are accepted.
• Zip code check — technology and speeds at a Dutch address.
• Check availability (kpn_grexx_prequalification): see which KPN products can be ordered at a Dutch address, and from which supplier.
• Carrier info (kpn_grexx_carrier_info): connection points, line details, and planned work at a Dutch address.

Customers and orders:

• Find customers (kpn_grexx_customer_data): search your KPN customer cards by ID, name, address, or number.
• List orders (kpn_grexx_order_summary): orders for a customer, filtered by state, product, or date.
• Look up an order (kpn_grexx_order_data): see the customer ID, product code, and quantity for one KPN order.

Internet lines:

• Login history (kpn_grexx_radius_check): how often the customer’s modem has signed in to the line over the last 7 days. Frequent sign-ins usually mean the connection keeps dropping.
• Session check (kpn_grexx_ras_check): whether the customer’s line is currently online, and its IP address.
• Start a line diagnosis (kpn_grexx_start_line_diagnose): starts a KPN test on an internet line (xDSL) that keeps dropping or won’t connect. It makes a change on KPN’s side, so it needs write access.

Mobile:

• SIM card (kpn_grexx_get_sim): the active SIM or eSIM on a mobile order. The SIM unlock code (PUK) and eSIM activation codes are hidden.
• Mobile settings (kpn_grexx_mobile_settings): blocks and limits on a mobile number.
• Mobile usage (kpn_grexx_mobile_usage): current data, call, and SMS use.
• Mobile orders (kpn_grexx_mobile_orders): number, SIM, subscription, and bundles for up to 50 mobile orders.
• Number porting (kpn_grexx_available_portings): which phone numbers can be moved over from another provider for a customer or a phone-system (switchboard) order.

If connect fails

• Grexx rejected the username or password. Copy both values again from API Gegevens.
• KPN isn’t set up on this Conduit yet. Contact WYRE support.