Skip to main content

Account and profile

Use Account to edit your profile, set display preferences, manage MFA and create API keys for the current account.

Note: Balancer is in beta. Endpoints, fields and behavior may change before general availability, and the feature must be enabled on your account before use. Contact your NetActuate account manager to request access.

Profile​

Profile

Edit your identity, display preferences and notification preferences. These preferences do not configure alert delivery.

  1. Open Account, then Profile.
  2. Update First name, Last name, Time zone, Date, Time, Theme or Locale as needed.
  3. Select Save. Reopen Profile and verify the saved values.
FieldRequiredDescriptionMatching API field
EmailYesValid email. Validation: Enter a valid email address.user.email
PhoneNoPhone number; an empty value clears it.user.phone
First nameYes1-64 characters. Validation: First name is required.user.firstName
Last nameYes1-64 characters. Validation: Last name is required.user.lastName
Time zoneNoPreferred time zone.user.preferences.timezone
DateNoDate format; initially locale when unset.user.preferences.dateFormat
TimeNo12h or 24h; initially 12h when unset.user.preferences.timeFormat
ThemeNosystem, light or dark; initially system when unset.user.preferences.themeMode
LocaleNoPreferred locale.user.preferences.locale
Certificate expiry and renewal failuresNoSave the preference; does not configure notification delivery.user.preferences.dashboardDefaults.notifications.certificateExpiry
Origin health changesNoSave the preference.user.preferences.dashboardDefaults.notifications.originHealth
Every configuration change on this accountNoSave the preference.user.preferences.dashboardDefaults.notifications.configurationChanges

Verify with the API​

Use the API host shown in the Balancer portal in place of https://<your-api-host>. Set $BALANCER_API_KEY to your credential for this context.

curl --fail-with-body --silent --show-error --request GET \
--url "https://<your-api-host>/user" \
--header "x-api-key: $BALANCER_API_KEY"

Expect HTTP 200 with code set to 200. The response includes data.account.name, data.organization.organizationId, data.organization.name, data.organization.isAdmin. Compare the returned configuration with the screen. A successful configuration read does not verify that an edge has applied it.

API reference: Get your profile and preferences.

Profile (alternate view 2)​

Profile

Edit your identity, display preferences and notification preferences. These preferences do not configure alert delivery.

  1. Open Account, then Profile.
  2. Update First name, Last name, Time zone, Date, Time, Theme or Locale as needed.
  3. Select Save. Reopen Profile and verify the saved values.
FieldRequiredDescriptionMatching API field
EmailYesValid email. Validation: Enter a valid email address.user.email
PhoneNoPhone number; an empty value clears it.user.phone
First nameYes1-64 characters. Validation: First name is required.user.firstName
Last nameYes1-64 characters. Validation: Last name is required.user.lastName
Time zoneNoPreferred time zone.user.preferences.timezone
DateNoDate format; initially locale when unset.user.preferences.dateFormat
TimeNo12h or 24h; initially 12h when unset.user.preferences.timeFormat
ThemeNosystem, light or dark; initially system when unset.user.preferences.themeMode
LocaleNoPreferred locale.user.preferences.locale
Certificate expiry and renewal failuresNoSave the preference; does not configure notification delivery.user.preferences.dashboardDefaults.notifications.certificateExpiry
Origin health changesNoSave the preference.user.preferences.dashboardDefaults.notifications.originHealth
Every configuration change on this accountNoSave the preference.user.preferences.dashboardDefaults.notifications.configurationChanges

API equivalent​

Set your theme preference. Use the API host shown in the Balancer portal in place of https://<your-api-host>. Set $BALANCER_API_KEY to your credential for this context.

curl --fail-with-body --silent --show-error --request PATCH \
--url "https://<your-api-host>/user" \
--header "x-api-key: $BALANCER_API_KEY" \
--header "Content-Type: application/json" \
--data '{"user":{"preferences":{"themeMode":"dark"}}}'

Expect HTTP 200 with code set to 200. The response acknowledges the stored change. Reopen the portal screen or run the read example below to verify it.

API reference: Update the current Balancer user's profile and UI preferences.

Verify with the API​

Use the API host shown in the Balancer portal in place of https://<your-api-host>. Set $BALANCER_API_KEY to your credential for this context.

curl --fail-with-body --silent --show-error --request GET \
--url "https://<your-api-host>/user" \
--header "x-api-key: $BALANCER_API_KEY"

Expect HTTP 200 with code set to 200. The response includes data.account.name, data.organization.organizationId, data.organization.name, data.organization.isAdmin. Compare the returned configuration with the screen. A successful configuration read does not verify that an edge has applied it.

API reference: Get your profile and preferences.

Profile (alternate view 3)​

Profile

Edit your identity, display preferences and notification preferences. These preferences do not configure alert delivery.

  1. Open Account, then Profile.
  2. Update First name, Last name, Time zone, Date, Time, Theme or Locale as needed.
  3. Select Save. Reopen Profile and verify the saved values.
FieldRequiredDescriptionMatching API field
EmailYesValid email. Validation: Enter a valid email address.user.email
PhoneNoPhone number; an empty value clears it.user.phone
First nameYes1-64 characters. Validation: First name is required.user.firstName
Last nameYes1-64 characters. Validation: Last name is required.user.lastName
Time zoneNoPreferred time zone.user.preferences.timezone
DateNoDate format; initially locale when unset.user.preferences.dateFormat
TimeNo12h or 24h; initially 12h when unset.user.preferences.timeFormat
ThemeNosystem, light or dark; initially system when unset.user.preferences.themeMode
LocaleNoPreferred locale.user.preferences.locale
Certificate expiry and renewal failuresNoSave the preference; does not configure notification delivery.user.preferences.dashboardDefaults.notifications.certificateExpiry
Origin health changesNoSave the preference.user.preferences.dashboardDefaults.notifications.originHealth
Every configuration change on this accountNoSave the preference.user.preferences.dashboardDefaults.notifications.configurationChanges

Verify with the API​

Use the API host shown in the Balancer portal in place of https://<your-api-host>. Set $BALANCER_API_KEY to your credential for this context.

curl --fail-with-body --silent --show-error --request GET \
--url "https://<your-api-host>/user" \
--header "x-api-key: $BALANCER_API_KEY"

Expect HTTP 200 with code set to 200. The response includes data.account.name, data.organization.organizationId, data.organization.name, data.organization.isAdmin. Compare the returned configuration with the screen. A successful configuration read does not verify that an edge has applied it.

API reference: Get your profile and preferences.

Security and MFA​

Security and MFA

Manage authenticator factors, rotate recovery codes and end sessions. Password changes use the password reset flow.

  1. Open Account, then Security. Select Change beside Password to start a reset.
  2. Select Add authenticator, enter Name (e.g. iPhone, Authy), scan the enrollment code, then enter 6-digit code to finish enrollment. Verify the factor appears.
  3. Select Rotate beside Recovery codes and store the replacement set securely.
  4. To end all your sessions, select Sign out everywhere and confirm. Expect your current session to end too.
FieldRequiredDescriptionMatching API field
Name (e.g. iPhone, Authy)Yes, to start enrollment1-64 characters. Validation: Name is required.name
6-digit codeYes, to confirm enrollmentCode from the enrolled authenticator.code

Verify with the API​

Use the API host shown in the Balancer portal in place of https://<your-api-host>. Set $BALANCER_API_KEY to your credential for this context.

curl --fail-with-body --silent --show-error --request GET \
--url "https://<your-api-host>/user/mfa-factors" \
--header "x-api-key: $BALANCER_API_KEY"

Expect HTTP 200 with code set to 200. The response includes data.mfaFactors[].mfaFactorId, data.mfaFactors[].type, data.mfaFactors[].name, data.mfaFactors[].destination. Compare the returned configuration with the screen. A successful configuration read does not verify that an edge has applied it.

API reference: Returns the current user's MFA factors.

API keys​

API keys

Create and manage credentials for the current account. The access you can select is bounded by your own access.

  1. Open Account, then API keys. Select Create key.
  2. Enter Name and, if needed, Description (optional), Expires on (optional) and Access (optional). Submit the dialog.
  3. Store the revealed credential securely. Return to API keys to verify its name and expiry.
  4. Use the key row actions to edit or revoke a key. Verify that a revoked key no longer appears.
FieldRequiredDescriptionMatching API field
NameYes1-64 characters. Validation: Name is required.apiKey.name
Description (optional)NoUp to 255 characters.apiKey.description
Expires on (optional)NoExpiry date, converted to an ISO timestamp.apiKey.expiresOn
Access (optional)Noread-only, write or admin, subject to your access ceiling.apiKey.accessMode

API equivalent​

Create a read-only API key. Store the returned credential securely; the verification read lists metadata. Use the API host shown in the Balancer portal in place of https://<your-api-host>. Set $BALANCER_API_KEY to your credential for this context.

curl --fail-with-body --silent --show-error --request POST \
--url "https://<your-api-host>/user/api-keys" \
--header "x-api-key: $BALANCER_API_KEY" \
--header "Content-Type: application/json" \
--data '{"apiKey":{"name":"example.com","accessMode":"read-only"}}'

Expect HTTP 200 with code set to 200. The response acknowledges the stored change. Reopen the portal screen or run the read example below to verify it.

API reference: Create an API key for your account user.

Verify with the API​

Use the API host shown in the Balancer portal in place of https://<your-api-host>. Set $BALANCER_API_KEY to your credential for this context.

curl --fail-with-body --silent --show-error --request GET \
--url "https://<your-api-host>/user/api-keys" \
--header "x-api-key: $BALANCER_API_KEY"

Expect HTTP 200 with code set to 200. Compare the returned configuration with the screen. A successful configuration read does not verify that an edge has applied it.

API reference: Returns your account user's API keys.