WordPress · Domain verification
The neuroon-search plugin verifies your domain automatically: it's not a public API call you have to code yourself, nor something you can do against the REST API directly. Just click a button in the WordPress admin.
How the flow works
- You generate the API Key in the Neuroon dashboard.
- Paste it into Settings → Neuroon Search → Settings tab.
- Click Verify Domain.
- The plugin internally checks that the current domain matches the
shop.urlalready registered in Neuroon. - If they match, the plugin stores the verification status internally. The Products, Widget and Diagnostics tabs appear.
Retrieve verification data
To inspect the current state without re-verifying, check:
/api/integrations/v1/shopwhich returns the shop's verification status.
Unverify
If you sell the shop, move domains or want to rotate credentials, from the admin Settings tab → Unverify Domain reverts verification and clears local options. It's not a call you make against the API.
Rotate the API Key
API Keys are revocable. If a key has leaked:
- Generate a new key in the Neuroon dashboard.
- Update Settings → Neuroon Search → API Key and save.
- Revoke the old one from the dashboard.
The plugin does not store the key in plaintext outside wp_options. On shared environments, restrict database access and consider moving the key to a constant in wp-config.php with a custom filter.
Common errors
| Code | Cause | Fix |
|---|---|---|
401 Unauthorized | Invalid or revoked API Key | Regenerate and re-paste the key. |
404 Not Found | The shopId does not exist or does not belong to your key | Click Verify Domain from scratch; the plugin re-verifies and updates the stored status. |
If verification keeps failing, check that get_site_url() matches exactly the domain (shop.url) registered in the Dashboard — aliases (www. vs apex) must match.
Best practices
- Verify from the canonical domain you intend to use in production. If your shop forces
https://www.example.com, do not verifyhttps://example.com. - Do not expose the API Key to the frontend. It is used only server-to-server from PHP.
- Re-verify after a URL change (
siteurlorhomein WP). Domain comparison is normalized (httpvshttpsand trailing slashes don't matter), but the host still has to match.
Next steps
- Product sync — the Products tab is enabled only after verifying.
- Authentication · API Key — scope, rotation and rate limits.
- Reference · Errors — codes catalog.