The Kling 3.0 series models API is now fully available Learn More Get Started Overview Quick Start Changelog API Reference General Info Rate Limits Callback Schema Video Generation Models Video Omni Text to Video Image to Video Reference to Video Motion Control Multi-elements to video Extend Video Lip Sync Avatar Text to Audio Video to Audio Text to Speech Voice Clone Image Recognize Element Effects Effect Templates NEW Video Effects Image Generation Models Image Omni Image Generation Reference to Image Extend Image AI Multi-Shot Virtual Try-On Others Query user info Pricing Billing Info Prepaid Resource Packs Protocols Privacy Policy of API Service Terms of API Service API Service Level Agreement General Information API Domain https://api-singapore.klingai.com 💡 Notice: The API endpoint for the new system has been updated from https://api.klingai.com to https://api-singapore.klingai.com. This API is suitable for users whose servers are located outside of China. API Authentication Step-1：Obtain AccessKey + SecretKey Step-2：Every time you request the API, you need to generate an API Token according to the fixed encryption method; put Authorization = Bearer in the Request Header Encryption Method：Follow JWT（Json Web Token, RFC 7519）standard JWT consists of three parts：Header、Payload、Signature Python Java Copy Collapse import time import jwt ak = "" # fill access key sk = "" # fill secret key def encode_jwt_token(ak, sk): headers = { "alg": "HS256", "typ": "JWT" } payload = { "iss": ak, "exp": int(time.time()) + 1800, # The valid time, in this example, represents the current time+1800s(30min) "nbf": int(time.time()) - 5 # The time when it starts to take effect, in this example, represents the current time -5s } token = jwt.encode(payload, sk, headers=headers) return token authorization = encode_jwt_token(ak, sk) print(authorization) # Printing the generated API_TOKEN Step-3: Use the API Token generated in Step 2 to assemble the Authorization and include it in the Request Header. Assembly format: Authorization = “Bearer XXX”, where XXX is the API Token generated in Step 2. Note: There should be a space between Bearer and XXX. Error Code HTTP Status Code Service Code Definition of Service Code Explaination of Service Code Suggested Solutions 200 0 Request successful - - 401 1000 Authentication failed Authentication failed Check if the Authorization is correct 401 1001 Authentication failed Authorization is empty Fill in the correct Authorization in the Request Header 401 1002 Authentication failed Authorization is invalid Fill in the correct Authorization in the Request Header 401 1003 Authentication failed Authorization is not yet valid Check the start effective time of the token, wait for it to take effect or reissue 401 1004 Authentication failed Authorization has expired Check the validity period of the token and reissue it 429 1100 Account exception Account exception Verifying account configuration information 429 1101 Account exception Account in arrears (postpaid scenario) Recharge the account to ensure sufficient balance 429 1102 Account exception Resource pack depleted or expired (prepaid scenario) Purchase additional resource packages, or activate the post-payment service (if available) 403 1103 Account exception Unauthorized access to requested resource, such as API/model Verifying account permissions 400 1200 Invalid request parameters Invalid request parameters Check whether the request parameters are correct 400 1201 Invalid request parameters Invalid parameters, such as incorrect key or illegal value Refer to the specific information in the message field of the returned body and modify the request parameters 404 1202 Invalid request parameters The requested method is invalid Review the API documentation and use the correct request method 404 1203 Invalid request parameters The requested resource does not exist, such as the model Refer to the specific information in the message field of the returned body and modify the request parameters 400 1300 Trigger strategy Trigger strategy of the platform Check if any platform policies have been triggered 400 1301 Trigger strategy Trigger the content security policy of the platform Check the input content, modify it, and resend the request 429 1302 Trigger strategy The API request is too fast, exceeding the platform’s rate limit Reduce the request frequency, try again later, or contact customer service to increase the limit 429 1303 Trigger strategy Concurrency or QPS exceeds the prepaid resource package limit Reduce the request frequency, try again later, or contact customer service to increase the limit 429 1304 Trigger strategy Trigger the platform’s IP whitelisting policy Contact customer service 500 5000 Internal error Server internal error Try again later, or contact customer service 503 5001 Internal error Server temporarily unavailable, usually due to maintenance Try again later, or contact customer service 504 5002 Internal error Server internal timeout, usually due to a backlog Try again later, or contact customer service Previous chapter：Changelog Next chapter：Rate Limits API Domain API Authentication Error Code The Kling 3.0 Series Models API is Now Fully Available – All in One, One for All！ Models Available in This Release Kling 3.0 Motion Control, Kling Video 3.0, Kling Video 3.0 Omni, Kling Image 3.0, Kling Image 3.0 Omni Refer to Key Highlights of the Models 3.0 All-in-One: A unified model for multi-modal input and output. Most powerful consistency across the universe: Subject consistency (supports cameo, subject with voice control, i2v + subject) and text consistency. Narrative control at your fingertips: More freedom, precision, and control—up to 15 seconds long, video scene cuts, ultra-high-definition storyboards/images, custom seconds. Upgraded native audio-visual output: Supports multiple speakers and languages (with accents). Kling 3.0 Motion Control Consistent Facial Identity from any angle Complex Emotions faithfully reproduced High fidelity Restoration, Even with Face Occlusions Consistent Facial Clarity Across Dynamic Framing User Guide -> Kling Video 3.0 Compared to 2.6, expected improvements: Supports subject upload in I2V scenarios for enhanced consistency Significant improvement in multi-character referencing, especially for three-person scenarios Supports Japanese, Korean, and Spanish in addition to Chinese and English Capable of generating certain dialects and accents Better distinction and control over different types of audio (speech, sound effects, BGM) Improved text retention in I2V scenarios Supports scene transitions, with up to 6 shots and customizable storyboarding User Guide -> Kling Video 3.0 Omni Compared to O1, expected improvements: Native audio-visual synchronization Supports video subject creation Further improved consistency in reference-based tasks, especially for characters and products Combined capabilities of reference + storyboarding + audio-visual sync significantly enhance usability Supports scene transitions, with up to 6 shots Extended generation duration up to 15 seconds User Guide -> Kling Image 3.0 Highly consistent feature retention Precise response to detail modifications Accurate control over style and tone Rich imaginative capabilities User Guide -> Kling Image 3.0 Omni Enhanced narrative sense New storyboard image set generation, retaining reference image features with scene relevance Direct output of 2K/4K ultra-high-definition images Further improved detail consistency User Guide -> Thank you for your support and understanding! I Got It