ipinfo.io Setup

Extendy GeoShield can use IPinfo as a remote API provider for country lookup.

You must bring your own IPinfo account or service access. Extendy GeoShield does not provide IPinfo credits, subscriptions, API tokens, or account access.

What Extendy GeoShield needs

The IPinfo integration requires the following Extendy GeoShield credential field:

IPinfo API Token

The runtime integration sends the token in an HTTPS Authorization: Bearer header. The token is not placed in the request URL.

Extendy GeoShield uses IPinfo Lite country data and maps the provider response as follows:

IPinfo response field	Extendy GeoShield result field
country_code	country_code
country	country_name

Extendy GeoShield does not depend on city, region, coordinates, ASN, privacy, or other non-country fields for this integration.

Before you start

Before configuring IPinfo in Extendy GeoShield:

1. Make sure you have your own IPinfo account or API access.
2. Obtain the API token required for your provider access.
3. Confirm your WHMCS server can make outbound HTTPS requests to the provider.
4. Decide whether you want to test with a real public IPv4 or IPv6 address.

Provider plan names, pricing, quotas, and rate limits are controlled by IPinfo and are not defined by Extendy GeoShield.

Configure IPinfo in Extendy GeoShield

1. Open the Extendy GeoShield addon admin page.
2. Open the Settings tab.
3. Set GeoIP Provider to IPinfo.
4. Enter your IPinfo token in IPinfo API Token.
5. Review the other settings that affect login processing, especially Addon Enabled, Client IP Source, and Alert When Country Detection Fails.
6. Click Save Settings.

After saving, the token field is shown as a masked stored credential. Submitting an empty credential field later keeps the existing stored token. Use the clear/remove option if you intentionally want to remove the stored token.

Test the provider

After saving the provider and token:

1. Stay on the Settings tab.
2. In GeoIP Provider Test Connection, enter a real public IPv4 or IPv6 address.
3. Click Test Connection.

The test uses the currently saved provider and saved credentials. It does not save settings and does not create login events.

On success, the result displays:

• provider;
• status;
• country code;
• country name.

On failure, the result displays a safe error message. It does not display the token, request headers, request URL, raw provider JSON, or raw exception text.

Failure behaviour

If the token is missing, invalid, or the provider rejects the request, Extendy GeoShield returns a controlled failure. During login, the event is still logged and the alert outcome depends on Alert When Country Detection Fails.

If country data is missing from the provider response, Extendy GeoShield treats the country as unknown for the login decision.

Security notes

• Do not share your IPinfo token in tickets, screenshots, logs, email templates, or documentation.
• Extendy GeoShield stores the token encrypted at rest.
• Extendy GeoShield does not intentionally write the token to WHMCS Activity Log, Login Events, provider test output, or customer-facing messages.
• Invalid or private IP addresses are rejected before credentials are retrieved or a provider request is made.

For the general settings reference, see the Configuration Guide.