X API Key Transfer Form Errors Out

Is this your situation?

The short answer

What you see, and why

Check these first

• Check for app rule violations. Automated or scripted accounts must comply with X's Developer Policy.Verify: Review notices sent about the app.
• Check if the app's use case changed. A developer who substantially changes an app's purpose or functionality must re-obtain express consent from the user.Verify: Compare current function against original approval.
• Check who authorizes the app's activity. Users are ultimately responsible for third-party applications they authorize to access their account.Verify: Confirm which account authorizes the app.

How X handles this

• Automated activity is subject to the X Rules and, for developers using the X API, the Developer Agreement and Policy.
• X may rate limit, suspend, or terminate developers' access to the API based on violations of those rules.
• Users are ultimately responsible for actions taken with their account or by applications associated with it.

Which path applies to you?

1. Does the form reject the transfer on submission? X may rate limit, suspend, or terminate developer access to the API based on a rules violation.
2. Has the app's purpose or functionality changed since it was approved? A developer must re-obtain express consent from the user before continuing automated action through their account.
3. Is the key tied to an account you no longer control? Users remain ultimately responsible for third-party applications they authorize on their account.

Step by step: finding the cause

1. Confirm which account currently authorizes the app. Users are ultimately responsible for third-party applications they authorize to access their account.Confirm: Check the account settings for the authorization tied to this app.
2. Review whether the app's functionality has changed. A developer must re-obtain express consent from the user if the purpose or functionality of the app has substantially changed.Confirm: Compare the app's current behavior to its original approval.
3. Check for any violation of the Developer Agreement and Policy. Automated or scripted accounts must comply with X's Developer Policy.Confirm: Look for any developer-facing notice about a policy violation.
4. Check for signs of rate limiting or suspension on the key. X may rate limit, suspend, or terminate developers' access to the API based on violations of the X Rules or Developer Agreement and Policy.Confirm: Look for an API response indicating a limited or suspended key.
5. Check whether automated activity triggered a filtering action. If automated activity violates the rules, X may filter posts from search results.Confirm: Search for recent posts from the account to see if they appear.
6. Confirm the receiving account is eligible to hold the key. Users are ultimately responsible for the actions taken with their account.Confirm: Check the receiving account's standing before retrying the form.

Common mistakes

• Assuming the error is a form bug. You treat the error as a technical fault and look for a form workaround instead.Why it happens: X may rate limit, suspend, or terminate developer access based on violations of the rules.
• Not re-confirming consent after changing the app. You change the app's purpose and expect the existing consent to still cover it.Why it happens: A developer must re-obtain express consent if the app's purpose or functionality has substantially changed.
• Overlooking shared responsibility for the app. You treat the app as separate from the account when access is restricted.Why it happens: Users are ultimately responsible for third-party applications they authorize to access their account.

Quick reference

Keeping track of who has access