Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Data Streams
  • Access management
  • Pricing policy
    • Overview
    • All methods
      • CreateStream
      • DecreaseStreamRetentionPeriod
      • DeleteStream
      • DescribeStream
      • IncreaseStreamRetentionPeriod
      • GetRecords
      • GetShardIterator
      • ListStreams
      • PutRecord
      • PutRecords
      • UpdateShardCount
    • Common errors
    • Examples
  • FAQ

In this article:

  • Request
  • Request options
  • Response
  • Errors
  1. HTTP API compatible with Amazon Kinesis Data Streams
  2. Methods
  3. DeleteStream

DeleteStream

Written by
Yandex Cloud
Updated at August 15, 2025
  • Request
    • Request options
  • Response
  • Errors

Deletes a stream, including all its shards and data.

On success, this method starts the stream deletion process, changes the stream status to DELETING, and returns an HTTP 200 response.

You can only delete a stream if its status is ACTIVE.

The stream will remain in the DELETING status until Data Streams completes the deletion. While in the DELETING status, the data stream may continue to process read and write operations, such as PutRecord, PutRecords and GetRecords, until deletion completes. To check the stream status, use the DescribeStream method.

If an application attempts to access a deleted stream, the API returns ResourceNotFoundException.

RequestRequest

The request contains JSON-formatted data.

{
  "EnforceConsumerDeletion": boolean,
  "StreamName": "string"
}

Request optionsRequest options

Option Description
EnforceConsumerDeletion If this option is omitted or set to false while the stream has active consumers, the deletion fails with ResourceInUseException error.

Type: Boolean
Required: No
StreamName Data stream name.

Type: String
Size: 1-128 characters.
The possible values are: [a-zA-Z][a-zA-Z0-9-]+*(?<!-)$
Required: Yes

ResponseResponse

Successful responses include an HTTP 200 code and an empty response body.

ErrorsErrors

Error Description HTTP code
LimitExceededException The request limit is exceeded. 400
ResourceInUseException The resource is currently locked by another operation. 400
ResourceNotFoundException The requested resource was not found. 400

Errors common to all methods may occur.

Was the article helpful?

Previous
DecreaseStreamRetentionPeriod
Next
DescribeStream
© 2025 Direct Cursus Technology L.L.C.