> For the complete documentation index, see [llms.txt](https://docs.live-eo.com/tradeaware/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.live-eo.com/tradeaware/using-the-tradeaware-api/authentication/rotate-client-secret.md).

# Rotate client secret

In order to keep your account safe, we recommend that you rotate your OAuth2.0 machine-to-machine client secret regularly.

### Prerequisites

* You created an OAuth2.0 machine-to-machine client for your account as described in [Authentication](/tradeaware/using-the-tradeaware-api/authentication.md).

### Impact

The client secret is necessary for your OAuth2.0 machine-to-machine client to request an access token which, in turn, is used to access the TradeAware API.

Rotating the client secret will immediately (more precisely: up to a 30 second delay) invalidate your existing client secret. Thereby, any attempts to request a new access token with the previous client secret will fail.

Only the new client secret will enable a successful request for a new access token.

That means, **expect some downtime between the time of secret rotation and your application being updated with the new secret and any necessary redeployments.** For more information, see [#downtime](#downtime "mention").

### How to

Before we dive into the step-by-step guide, please be aware of the following:

Depending on your application's hosting provider, you may need to redeploy the application for any changed environment variables and environment secrets to come into effect. This depends on your hosting provider, so please consult their documentation before continuing with the following steps.

#### Step-by-step

* Log in to the [TradeAware Web App](https://tradeaware.live-eo.com/) and navigate to the [Developer Tools](https://tradeaware.live-eo.com/admin/dev-tools). Alternatively to using the URL directly, you may do the following: After login, click the profile icon in the bottom left corner, then choose "Manage Account". Then, click "Developer Tools".
* On the Developer Tools page, click the heading of the "Danger Zone" section to display further options.
* Under the section "Rotate Secret", click the red button "Rotate".
* A dialog opens for you to confirm the secret rotation. Follow the instructions in the dialog and confirm the dialog with "Rotate". **WARNING: THIS ACTION IS IMMEDIATE AND CANNOT BE REVERTED.**
* Next, the dialog will close and bring you back to the Developer Tools. In the field "Client Secret", copy your new client secret,
* Update your application to use the new client secret.

### Downtime

We currently do not support client secret rotation with zero downtime.

You may be able to achieve zero downtime coincidentally by timing the secret rotation right after your OAuth2.0 machine-to-machine client requested a new access token. However, this is difficult to time.

### Programmatically rotating client secrets

We currently do not support this feature. If you are interested in this functionality, please [contact support](mailto:support@live-eo.com).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.live-eo.com/tradeaware/using-the-tradeaware-api/authentication/rotate-client-secret.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.