Was this content helpful?
How could we make this article more helpful?
Account API allows you to access Lyve Cloud account information through an API endpoint. The account API can be generated only by the account administrators. You can perform all Lyve Cloud operations using the account API credentials.
Account API enables customers and sub-account administrators to leverage Lyve Cloud account's functionality programmatically.
You can perform the following actions using account API:
For more information, see Lyve Cloud Account API version 2.
The API uses the secure HTTP/1.1 over TLS 1.2 protocol and operates mainly with JSON-formatted messages. All API responses are assigned specific numeric codes that help you quickly identify if a request to an endpoint is successful or unsuccessful. For more information on error codes, see List of API error codes in the Account API version 2.
The credentials never expire when generating API credentials unless you configure an expiration duration. You can change the default setting by setting an expiry duration for all newly created API credentials; see Setting expiration duration. This limits the validity of the Account API credentials, which need to be changed again after the expiration. After the expiration date, the secret credentials cannot be used for authentication but will stay associated with the account until you delete or regenerate it.
The status of credentials will show as one of the following. The status is based on the expiration duration.
After the credentials are generated, use these credentials to generate a time-bound token. This token is used to authenticate the Lyve Cloud Account API and is passed as a Bearer header value.
You must attempt to generate credentials the second time if Account API generation fails.
You can re-generate the credentials regardless of their expiration status. If you already have active credentials and still regenerate new credentials, the old credentials become inactive.
Once you delete the credentials, you can again generate new credentials. However, any workload that uses these credentials will immediately lose access to the resources.