Skip to Content
Browse documentation

Manage Reseller API Users

Create Eenos reseller API users, configure individual allowed source IPs, rotate passwords and remove API credentials with confirmation.

Open Eenos → API → API Manager.

For integration headers, ownership rules and endpoint examples, use the Reseller API reference and connection guide.

Existing API users

The table shows row number, API username, creation and update timestamps, remote-access mode, allowed IP addresses and actions. It lists users for the signed-in reseller, without displaying their passwords. Search and paging help locate a user; the default page size is 25.

Open means connections are allowed from any IP. Restricted means authentication checks the recorded client IP against the saved address list. This is source-IP policy, not a switch that disables the credential entirely.

Create an API user

FieldRequirements and behavior
API UsernameRequired and unique within this reseller. The visible form accepts 1–32 characters, starting with a lowercase letter or underscore, followed by lowercase letters, digits, underscores or hyphens.
PasswordRequired; the browser form requires at least eight characters and provides generation, visibility and strength controls. Use a strong unique password.
Confirm PasswordRequired and must match the password.
Remote AccessChoose any IP or only specified IP addresses. The initial selection allows any IP.
Allowed IP AddressesEnter individual IPv4/IPv6 addresses separated by commas when restricting access.

Choose Create API User, inspect the confirmation and confirm creation, or cancel. The server rejects duplicate usernames, mismatched passwords and invalid non-empty allowed addresses. The browser's password-length requirement is not a substitute for choosing a strong password; the current server forms require non-empty passwords without the same explicit minimum-length rule.

Passwords are stored as hashes rather than displayed as recoverable values. Save the chosen password securely for the integration; use password change if you lose it.

Restrict source addresses

Use individual addresses such as 192.0.2.10, 2001:db8::10. Do not enter CIDR networks, hostnames or URLs. Whitespace around comma-separated addresses is stripped during validation. When open mode is selected, supplied IP text is not used as a restriction.

The browser requires at least one address for restricted mode. The server can accept an empty restricted list, which matches no client, so check the saved list after creating the user. Authentication compares the detected client IP with recorded strings; verify access from the intended client, especially with IPv6 representations or proxy/NAT paths.

Confirm the actual client address

Allow the address the panel receives for the integration, not merely the address of your workstation. A valid saved IP list does not prove that the intended client will match it. Keep credentials restricted while investigating connectivity rather than assuming open access is required.

Change a password

Use the user's password-change action, confirm the username and enter New Password. The browser requires at least eight characters. Submit the change and inspect the response, then update the integration's credential store and verify authentication with the new password.

Changing an API password is separate from changing your reseller panel password. Existing integrations using the old API password need updating. The action changes the password and update timestamp; it does not edit source-IP policy.

Delete an API user

Use the row's delete action, inspect the intended username and confirm deletion, or cancel. The helper acts within the signed-in reseller's credential records. Deleting the user removes that stored credential, preventing future authentication with it; dependent integrations must be updated or retired separately.

Deletion is not an integration rollback

Removing credentials does not reverse account or service changes already made through the API. Check dependencies before deleting and verify that the integration no longer relies on the removed user.

Results and limits

Create, password-change and delete outcomes are recorded as reseller security activity. Review validation and write errors before retrying, and reload the table to inspect current state. Demo sessions cannot perform these mutations.

This page has no general edit form for an existing user's source-IP list or a per-user endpoint-permission selector. Plan a replacement credential and integration transition when access policy must change, preserving the needed restrictions. A success alert confirms the management operation, not an end-to-end API request.