Premium configuration
Overview
Update premium geolocation settings. Routes use /wp-json/aam/v2 on a standard WordPress installation.
Endpoints
| Method | Route | Input | Purpose |
|---|---|---|---|
| POST (Premium) | /premium/geo-settings |
adapter, api_key, test_ip |
Save Geo Lookup provider settings. |
The Input column lists route-specific parameters. A path parameter in {braces} is required. WordPress validates body and query parameters against the registered route schema. Premium rows require the Complete Package add-on.
Parameter guide
The route table shows which operation uses each parameter. Path parameters are required; other requirements depend on the operation.
| Parameter | Type | Meaning |
|---|---|---|
adapter |
string |
Provider: ipapi, ip-api, ipstack, geoapify, or ipgeolocation. |
api_key |
string |
Provider API key. |
test_ip |
string |
Optional IP for testing provider results. |
Access level and authorization
This endpoint group does not use the shared access-level selector unless a row explicitly names it.
Required permission: aam_manager and aam_manage_configs. See Authentication and Error handling.
Example
POST /wp-json/aam/v2/premium/geo-settings
Authorization: Basic <base64 username:application-password>
Content-Type: application/json
{"adapter":"ipapi","api_key":"<provider-key>","test_ip":""}
This submits premium geolocation settings. Send adapter (ipapi, ip-api, ipstack, geoapify, or ipgeolocation), api_key, and optional test_ip in the request body. The endpoint validates a non-empty test IP.