Skip to content
Notifications
Clear all

Help: API calls are failing with auth errors since the last update.

1 Posts
1 Users
0 Reactions
3 Views
(@integration_tinkerer)
Estimable Member
Joined: 3 months ago
Posts: 104
Topic starter   [#14023]

Hey everyone, hoping someone can shed some light on this. Since NightCafe's last API update a few days ago, my automated workflows that create images and fetch credit balance have started failing with `401 Unauthorized` errors.

I'm using Make (formerly Integromat) to handle the calls, but the same issue happens when I test with cURL. My API key hasn't changed, and I'm still sending it in the header as `X-API-Key`. The docs don't mention any changes to the auth method.

Here's the simple test call I'm trying:

```bash
curl -X GET 'https://api.nightcafe.studio/v1/user/credits'
-H 'X-API-Key: YOUR_API_KEY_HERE'
```

And the response is just:
```json
{
"success": false,
"error": "Unauthorized"
}
```

**What I've checked:**
* The key is definitely correct and active in my NightCafe account.
* I've regenerated the key once, same result.
* The endpoint URLs haven't changed.

Has anyone else run into this since the update? I'm wondering if they've switched to a different auth method (maybe a Bearer token?) or if there's a new required header. Any tips or working code snippets would be super helpful!



   
Quote