[BUG]: Can't rotate API key in the UI

[alexandargyurov]

Describe the bug
While self-hosting Lago, you cannot rotate the API key that is generated for you.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Developer' tab
2. 'API keys & ID'
3. 'API key'
4. Click the dots
5. Click 'Rotate key'
6. Modal opens
7. Click rotate API key
8. Toast message "Something went wrong. If the error persists, please contact us."

Expected behavior
You can rotate at least the key you have

Screenshots

Support

• Version v1.41.3

[jdenquin]

Hello @alexandargyurov

Can you provide your API logs?

[larkthebird]

Lark investigation report

Verdict: Reproduced
Classification: bug
Confidence: high

More details

Summary

The issue reports that API key rotation fails in self-hosted Lago instances. When attempting to rotate an API key via the Developer → API keys & ID section, clicking "Rotate key" and confirming with "Rotate API key" results in the error toast "Something went wrong. If the error persists, please contact us." The reporter is on version v1.41.3.

Verification notes

Successfully reproduced the bug on Lago v1.45.1 (latest version). Set up a fresh self-hosted Lago instance using Docker, created a new account, navigated to Developer → API keys & ID, and attempted to rotate the default API key.

Steps performed:

1. Deployed Lago v1.45.1 via docker-compose
2. Created new organization "Test Org" with test user
3. Navigated to Developers panel → API keys & ID tab
4. Clicked the three-dot menu on the API key row
5. Selected "Rotate key"
6. In the modal, selected "Immediately" expiration option
7. Clicked "Rotate API key" button

Observed behavior:

• Error toast appeared: "Something went wrong. If the error persists, please contact us."
• Console showed GraphQL error: [GraphQL error]: Message: forbidden, Path: rotateApiKey, Extensions: {"status":403,"code":"cannot_rotate_with_provided_date"}

Root cause indication:
The backend API returns a 403 Forbidden with error code cannot_rotate_with_provided_date, suggesting the expiration date validation is failing even for the "Immediately" option. This appears to be a backend bug in how the rotation request handles the expiration date parameter.

Note: The reported version v1.41.3 doesn't exist on Docker Hub (available versions show v1.41.0, v1.41.1, v1.41.2), but the bug persists in the latest v1.45.1, indicating it hasn't been fixed.

Reproduction steps

1. Set up self-hosted Lago instance using docker-compose (tested on v1.45.1)
2. Create a new organization account or log in to existing account
3. Navigate to the Developer panel (bottom of left sidebar)
4. Go to 'API keys & ID' tab
5. Locate the existing API key in the table
6. Click the three-dot menu (More options) on the API key row
7. Click 'Rotate key' from the dropdown menu
8. In the modal, the 'Immediately' option should be selected by default
9. Click 'Rotate API key' button to confirm
10. Observe error toast: 'Something went wrong. If the error persists, please contact us.'
11. Console shows: GraphQL error with code 'cannot_rotate_with_provided_date' and status 403

---

Investigated by Lark — verification was performed against the described target, not the repository code.