What does 401 account_mismatch mean?

The Account ID in X-Clatter-Account isn't the account that owns the key.

Code: account_mismatch · HTTP status: 401

A key only works together with its owner's Account ID. Someone else's Account ID is refused.

Common causes#

• a key from one account and the Account ID of another (common when you have a personal and a work account)
• a teammate's key used with your own Account ID
• a typo in the Account ID

How to fix it#

1. Open Console › Settings while signed in to the account that created the key and copy that Account ID.
2. Matching is case-insensitive, so letter case isn't the problem; check the characters.
3. If you can't tell which account owns a key, create a fresh key in the account you want to bill.

Should my code retry?#

Not retryable until the pair matches.

The error body uses the OpenAI shape, so OpenAI SDKs raise it as an exception you can catch:

{"error": {"message": "...", "type": "...", "code": "account_mismatch", "param": null}}

Every response also carries an X-Request-Id. Keep it in your logs; it's the quickest way for support to find a request.

See the full list in the Model API reference.

Still need help?#

• General support: support@clatterlabs.com or team@clatterlabs.xyz
• Infrastructure questions, or permanent deletion of your data (your whole account or one service): infrastructure@clatterlabs.xyz

We usually reply within the first hour, and always within 24 hours. A full support team is with you.