...
ID: The ID of the API key. This is the first 32 characters of the full service API key, which does not contain the secret of the key.
NAME: The name of the API key.
STATE: Indicates whether the API key is currently Enabled, Disabled, or Expired. An enabled API key is available for use while an expired key is no longer valid. You can enable and disable a valid user API key, but you cannot enable or disable an expired one. Fourteen (14) days prior to expiration of your service API key, Infoblox Platform will notify you in-app and via email on a daily basis. You can create a new API key to replace the expiring one, and then delete the old one when it expires.
EXPIRES AT: The timestamp when the API key will expire or has expired.
LAST USED AT: The timestamp when the API key was last used in an API operation. For troubleshooting purposes, this gives you an idea when the API key was last used in case of suspicious activities.
CREATED AT: The timestamp when the API key was first created.
UPDATED AT: The timestamp when the API key was last updated.
TYPE: The type of API keys. This can be one of the following:
Legacy: Legacy keys are user API keys that were automatically generated for signed-in user in previous releases. Infoblox will deprecate legacy keys in the near future. For information, see Configuring User API Keys.
Interactive: Interactive keys are user API keys that signed-in users created for themselves. All signed-in users are allowed to create user API keys for themselves. For information, see Configuring User API Keys.
Service: Service API keys are API keys created for service account users. These keys are used to facilitate API authentication between devices. No signed-in users are involved in the API requests.
CREATED BY: The user who created this API key.
UPDAETD UPDATED BY: The user who last updated this API key.
...