Skip to Content
Browse documentation

Create Reseller API Logins

Create dedicated Reseller API credentials in RAPP, configure source-IP access and identify the three required authentication headers.

Sign in to the reseller's RAPP interface and open Eenos → API → API Manager. Create credentials under the reseller that will own the integration. WAP API users and reseller panel passwords are separate credentials.

Create a dedicated API user

  1. Enter an unused API Username within this reseller. The form uses the Linux-style lowercase username pattern: start with a lowercase letter or underscore, then lowercase letters, digits, underscores or hyphens, up to 32 characters; the server regex also allows an optional final dollar sign within that limit.
  2. Enter and confirm a unique password. The browser requires at least eight characters; the current server form requires non-empty matching values and trims surrounding whitespace.
  3. Select Remote Access: allow any IP or restrict to specified addresses. The initial selection is open access.
  4. For restricted access, enter individual IPv4/IPv6 addresses separated by commas. Hostnames, URLs and CIDR ranges are not accepted. Confirm creation and inspect the saved row.

The browser requires a non-empty restricted list. The server form can accept an empty restricted list, which will match no client, so verify the saved addresses. A password hash is stored; the password cannot be recovered from the API-user listing. Duplicate names are rejected within the same reseller.

The full API Manager guide covers the table, confirmations, password changes and deletion. Mutations are unavailable through the panel on a demo server. Source-IP policy changes require creating a replacement API user; changing a password does not edit that policy.

Use the correct identities

HeaderExampleMeaning
X-RESELLERexampleresellerReseller hosting username.
X-API-USERbilling_apiAPI username created inside that reseller.
X-API-PASSWORDYOUR_API_PASSWORDChosen API password.

These are authentication headers, not fields passed to account-creation operations. Keep credentials on the integration backend. The API account operates within the authenticated reseller's account/package scope; the API Manager does not provide per-operation scopes.

Verify and rotate

Test from the intended integration host using Connect and Test API Login. Check the returned reseller and username before sending any account operation. If access is restricted, a successful test from another host does not prove that the production integration's IP is allowed.

To rotate credentials, create and test a replacement, update the integration and revoke the old API user once no clients depend on it. Password changes require updating every client using that API user; deletion prevents later authentication with it.