Q: What does this feature do?
It lets you remotely pause or unpause a running container via the Uptycs API — useful for containing a compromised or problematic workload without killing it outright.
Q: What do I need before I can use this?
- Uptycs-Protect must be enabled on your tenant
- The Remediation flag must be enabled in your flag profile
- An API key with Remediation permission (Admin users have this by default), or a Bot token with the same permission
Q: How do I identify which container to pause?
Use the Uptycs UI or API to find the affected Node and container, and note down its Asset ID and Container ID.
Q: How do I authenticate the API call?
- Go to the remediationJobs API docs
- Enter your API Key and Secret, then click "Generate Token"
- Copy the generated Bearer token
Q: How long is the token valid?
15 minutes. If it expires mid-task, just regenerate a new one from the same page.
Q: What does the API call look like?
A POST request to your customer's remediationJobs endpoint, with:
Authorization: Bearer <token> header- A JSON body containing your
assetId and a request object with an id and action
Q: What's the difference between pausing and unpausing?
Only one field changes — the action value in the request body: pause_container vs. unpause_container. Everything else (URL, headers, assetId, container/request id) stays the same.
Q: Where do I get the Customer ID used in the URL?
From your key.json file (the same one containing your API Key/Secret).
Q: Is there a UI button for this yet?
Not currently — this is API-only for now, but a UI button is on the roadmap. Until then, this API workflow is the supported path.
Q: Has this been tested?
Yes — internally validated on a live tenant using a real container hostname, with both pause and unpause confirmed working via API request.