Kling 2.1 API sunset: 410 Gone, and the kling-3 id on Sume

Krea retired Kling 1.0 through 2.1: endpoints return 410 Gone after Sep 15, 2026. Sume lists kling-3 in its video catalog; here is what to change.

4 min readSume
All posts

If you called a Kling 1.0 to 2.1 endpoint on Krea, it now returns 410 Gone. On Sume the Kling id in the video catalog is kling-3, so migrating means changing the model id and re-checking the request fields, not finding an older version.

Krea facts are from its September 9, 2026 changelog; Sume facts from the Video Router docs and OpenAPI, read 2026-09-30.

What did Krea retire?

Krea's entry says Kling is retiring Kling 1.0, 1.5, 1.6, 2.0 Master and 2.1. Their API endpoints were deprecated and sunset on September 15, 2026: until then they returned Deprecation and Sunset headers, and after that they return 410 Gone. Kling 2.5 is Krea's recommended replacement, and Kling 2.6, Kling 3.0 and Kling o1 remain available there.

What does Sume list for Kling?

Kling on Sume, from the OpenAPI schema read 2026-09-30.
ItemWhat the schema says
Video catalog idkling-3 in the Video Router model enum
ExampleA "Kling 3 text-to-video" request example
1080pAccepted by seedance-2.5, seedance-2, kling-3, wan-3.0 and gemini-omni-flash-1.1
Motion controlA separate route described as the primary Kling 3.0 Motion Control route

How do I migrate a request?

Send the same intent to the Video Router with model: "kling-3". Then read capabilities from GET /v1/video-router/models instead of carrying over limits from the old version; the docs say limits are per model. This post did not compare Kling versions' outputs.

Where do I read more about Kling 3?

See Kling 3.0 API for request shape and Kling 2.6 vs Kling 3.0 if you were on a later 2.x model. Sume does not list Kling 2.1, so there is nothing to pin to.

Sources

Related posts

More in Models

All Models posts

Written by Sume