Create WAP API Logins
Create dedicated root administrator API credentials in Eenos WAP, configure allowed source IPs and prepare an integration for authentication.
Sign in to WAP as the root administrator over HTTPS, then open Preferences → API Manager → Create API Account. See the WAP API Manager guide for its complete table, password-change and deletion controls.
Account fields
| Field | What to enter |
|---|---|
| API User Name | A unique API username. For browser/server compatibility, use 5–30 lowercase characters, begin with a letter or underscore, then use lowercase letters, digits, underscores or hyphens. |
| Password | A long, unique API password. This is not the server's root password. |
| Re-enter Password | The same password again. |
| Remote Access: Allow any IP | No account-level source-IP allowlist; authentication is still required. |
| Remote Access: Allow the following IPs only | Restrict requests to the integration's allowed source addresses. |
| Whitelisted IPs | Individual IPv4/IPv6 addresses separated by commas. At least one valid IP is required for restricted access; hostnames, ports and CIDR ranges are not supported here. |
The default access choice allows any IP. Select the intended policy explicitly before confirming. For a remote integration, allow its actual outbound/NAT IP rather than its private address or the IP of the hosted website.
Create and verify
- Complete the fields and select Create API User.
- Review the named account in the confirmation and select Create.
- Confirm the table row and its remote-access policy.
- Store the password securely; existing passwords cannot be retrieved from the table. A forgotten password must be changed.
- Follow Connect and Test API Login from the intended integration host.
Creation does not open a firewall port or establish that a remote client can reach WAP. Demo sessions cannot create, change or delete API users.
Source-IP restrictions and proxies
The current backend compares the client IP against the stored address list. It uses the first X-Forwarded-For value when present, otherwise the remote socket address. If a proxy is in the path, ensure the server's proxy configuration replaces untrusted forwarded headers and reports the intended client address. Do not treat an IP allowlist as a replacement for secure credentials and a controlled network path.
Maintain the integration account
Use a separate API account per integration. Password rotation requires updating that integration's stored secret and testing again. The API Manager password-change dialog does not edit source-IP restrictions; use the documented replacement-account workflow when the access policy must change.
Delete an old account only after its replacement works. Avoid copying credentials into source repositories, public tickets or request URLs.