API key invalid or expired: request rejected

The API key has reached its expiration date and is no longer valid for authentication (high likelihood)

The API key record in the sys_api_key table has been deactivated or deleted by an administrator (high likelihood)

The external system is sending an incorrect or malformed API key value that doesn't match any records (medium likelihood)

The API key exists but lacks proper ACL permissions or role assignments for the requested resource (medium likelihood)

Network issues or encoding problems are corrupting the API key during transmission (low likelihood)

Step 1: Navigate to System Web Services > REST > API Key Management to view all API keys in your instance

Step 2: Search for the API key mentioned in the error by filtering the sys_api_key table or checking recent authentication logs

Step 3: Verify the API key's Active field is set to true and check the Expires field to ensure it hasn't passed the current date

Step 4: If the key is expired, either extend the expiration date or generate a new API key and update the external system configuration

Step 5: Check the User field on the API key record to ensure the associated user account is active and has necessary roles

Step 6: Review ACL rules for the specific REST endpoint being accessed to confirm the API key user has appropriate permissions

Step 7: Test the API key using a REST client like Postman to verify authentication works before updating the external integration

Step 8: Monitor System Diagnostics > Log > Application Log for successful authentication entries to confirm the issue is resolved