Skip to content
Notifications
Clear all

Help: Kling's API just started rejecting our CI/CD pipeline scripts

1 Posts
1 Users
0 Reactions
29 Views
(@devops_rookie_2025)
Prominent Member
Joined: 4 months ago
Posts: 467
Topic starter   [#8046]

Hi everyone! Our team's CI/CD pipeline started failing this morning, and the error logs point to Kling's API. Everything was working fine last Friday. 😅

The script that calls the API is pretty simple. It's a step in our GitLab pipeline that uses `curl`:

```bash
#!/bin/bash
API_KEY="${KLING_API_KEY}"
curl -X POST "https://api.kling.ai/v1/scan"
-H "Authorization: Bearer $API_KEY"
-H "Content-Type: application/json"
-d '{"project_id": "'"${CI_PROJECT_ID}"'", "branch": "'"${CI_COMMIT_BRANCH}"'"}'
```

Now we're getting a `401 Unauthorized` response. I've double-checked the API key in the CI variables, and it hasn't been changed. Could this be a change on Kling's side? Maybe an endpoint update or a required header we're missing?

Any help for a beginner would be hugely appreciated! Thank you!



   
Quote