404/api-keys/:id/disable, /api-keys/:id/enable

API key not found

How to fix the Scrnpix API 404 error when trying to enable or disable an API key that does not exist.

When Does This Happen?

This error occurs when you try to enable or disable an API key using an ID that does not exist or belongs to a different user. Each user can only manage their own API keys.

Reproduce This Error

curl -X POST \
  -H "Cookie: session=your-jwt" \
  "https://api.scrnpix.com/api-keys/nonexistent-id/disable"

{"error": "API key not found"}

How to Fix

1List your API keys with GET /api-keys to find valid key IDs
2Use the correct key ID from the list response
3Verify you are authenticated as the owner of the API key

Correct Request

curl -X POST \
  -H "Cookie: session=your-jwt" \
  "https://api.scrnpix.com/api-keys/valid-key-id/disable"

{"success": true}

Related Errors

Missing authorization

How to fix the Scrnpix API 401 error when the session cookie is missing from requests to dashboard endpoints.

Invalid token

How to fix the Scrnpix API 401 error when the session JWT token is expired, malformed, or has an invalid signature.

Frequently Asked Questions

How do I find my API key IDs?

Send a GET request to /api-keys with your session cookie. The response includes an array of keys, each with an id field that you can use for enable/disable operations.

Still Having Issues?

Check your API key and subscription status in the dashboard, or explore our language guides for integration examples.

Go to Dashboard