---
title: "Resume Pro database traffic"
method: POST
path: "/v1/subscriptions/{subscriptionId}/databases/{databaseId}/traffic/resume"
tags: ["Databases - Pro"]
---

# Resume Pro database traffic

`POST /v1/subscriptions/{subscriptionId}/databases/{databaseId}/traffic/resume`

Resumes traffic for the specified Pro database. This is available in private preview.

## Path parameters

- `subscriptionId` integer, required
- `databaseId` integer, required

## Response `204`

Traffic resumed

## Other responses

- `400` — Bad Request - The server cannot process the request due to something that is perceived to be a client error
- `401` — Unauthorized - Authentication failed for requested resource
- `403` — Forbidden - Not allowed to access requested resource (primarily due to client source IP API Key restrictions)
- `404` — Not Found - The resource you were trying to reach was not found or does not exist
- `408` — Request Timeout - The server didn't receive a complete request message within the server's allotted timeout period
- `409` — Conflict - request could not be processed because of a conflict (primarily due to another resource that exist with new updated name)
- `412` — Precondition Failed - Feature flag for this flow is off
- `429` — Too Many Requests - Too many resources are concurrently created / updated / deleted in the account. Please re-submit API requests after resource changes are completed)
- `500` — Internal system error - If this error persists, please contact customer support
- `503` — Service Unavailable - Server is temporarily unable to handle the request, please try again later. If this error persists, please contact customer support

---

[API](https://skmtc.net/redis/apis/redis-cloud-api.md) · [All operations](https://skmtc.net/redis/apis/redis-cloud-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/redis/redis-cloud-api/versions/01eef7f3c69f/schema)