Facebook Ads Authentication Error Codes

  • Updated on Sep 10, 2025
  • Published on Apr 16, 2024
  • 5 minute(s) read
Prev Next

You cannot make any changes to External Platform Integrations without having either an Administrator or an Editor with PII access in InOne. Refer to User Roles for further information.

The integration with the Facebook Business Account might not be authenticated. In this case, you receive an error code. You can check below for the codes and further details:

458: App not installed

If you receive a 458: App not installed error while integrating Facebook Ads, it means you have not logged into your app. You need to re-authenticate. To solve the problem:

  1. Open the app where you encountered the error.
  2. Look for the option to log out or sign out.
  3. Tap on the option to log out.
  4. After logging out, log in with your credentials to re-authenticate.

459: User Checkpointed

If you receive a 459: User Checkpointed error while integrating Facebook Ads, you must log in to Facebook's website to correct the issue. Then,

  1. Open a web browser on your device.
  2. Go to either https://www.facebook.com or https://m.facebook.com.
  3. Log in with your Facebook credentials.
  4. Follow any on-screen instructions or prompts to resolve the checkpoint issue. 
  5. Contact Support: If the issue persists or if you believe the error is unjustified, you can contact Facebook's support team for further assistance. Provide as much detail as possible about the error and any relevant circumstances to help them investigate and resolve the issue effectively.
  6. Check for Updates: Ensure your Facebook app or browser is up-to-date. Sometimes, outdated versions can cause compatibility issues, leading to errors.

460: Password Changed

If you receive a 460: Password Changed error while integrating Facebook Ads:

If you logged in using the OS-integrated flow (iOS 6 and above):

  1. Go to Facebook OS settings on your device.
  2. Update your password there.

If not:

  1. Remove the Ad account from the Integration Settings in InOne. 
  2. Log out of Facebook.
  3. Log in again from the Integration Settings.
  4. Add the Ad accounts you deleted in step 1, which will refresh the token for you and create a new long-lived token.

463: Expired

If you receive a 463: Expired error while integrating Facebook Ads, it means your login status or access token has expired, been revoked, or is invalid. To solve the issue:

Obtain a New Access Token

  • If your access token has expired, you must obtain a new one. This often involves reauthorizing your app or service with Facebook.
  • Follow the authentication process provided by Facebook for your app or service to generate a new access token.

Reauthorize Your App

  • If your access token has been revoked or invalidated, you might need to reauthorize your app or service with Facebook.
  • This typically involves logging into your app or service again and following the prompts to grant the necessary permissions.

Check for Token Expiry

  • Make sure your app or service handles access tokens correctly, including checking for expiry dates.
  • Implement mechanisms within your app to handle token expiration gracefully, such as automatically refreshing tokens when they expire.

Review Token Handling Policies

  • Review Facebook's documentation and policies regarding access token usage and expiration.
  • Ensure that your app or service complies with Facebook's guidelines for token management.

Refresh the Access Token

The responsible team member needs to follow the steps below to change the access token related to the accounts they added:

  1. Remove the Ad account from the InOne panel.
  2. Log out of Facebook in the panel.
  3. Log in again.
  4. Add the ad account again.

Those steps will refresh the access token.

Troubleshoot Technical Issues

  • If you're encountering persistent issues with expired access tokens despite following proper procedures, check for any technical issues on your end.
  • Ensure that your app's integration with Facebook's authentication services is implemented correctly and is up to date.

Contact Facebook Support

  • If you cannot resolve the issue on your own, consider contacting Facebook's developer support for assistance.
  • Provide details about the error code and any relevant circumstances to help them assist you more effectively.

464: Unconfirmed User

If you receive a 464: Unconfirmed User error while integrating Facebook Ads, it means that there's an issue with the user account that needs to be addressed. To solve it:

  1. Open a web browser on your device.
  2. Go to either https://www.facebook.com or https://m.facebook.com.
  3. Log in with your Facebook credentials.

Check for Confirmation Messages

After logging in, check for confirmation messages or prompts indicating that action is required to confirm the user account.

Follow the Confirmation Instructions

  • If there are any confirmation messages or prompts, follow the instructions to confirm the user account.
  • This might involve verifying your email address or mobile phone number associated with the account.

Resend Confirmation Email/SMS

  • If you didn't receive a confirmation message or the confirmation link has expired, look for options to resend the confirmation email or SMS.
  • Follow the link in the confirmation email or the instructions provided in the SMS to confirm your account.

Contact Support if Necessary

  • If you're unable to confirm the user account or encounter any issues during the process, consider contacting Facebook support for assistance.
  • Provide details about the error code and any relevant information about your account to help them assist you effectively.

Check for Account Restrictions

  • Ensure that your account is not restricted or blocked for any reason. Sometimes, account restrictions can prevent confirmation processes from being completed.
  • Review Facebook's Community Standards and guidelines to ensure compliance with their policies.

467: Invalid Access Token

If you receive a 467: Invalid Access Token error while integrating Facebook Ads, it means your access token has expired, been revoked, or is invalid. To solve the issue:

  • Handle expired access tokens appropriately, which might involve obtaining a new access token or reauthorizing your app.
  • Or you can follow these steps.
  1. Remove the Ad account from the Integration Settings in InOne. 
  2. Log out of Facebook.
  3. Log in again from the Integration Settings.
  4. Add the Ad accounts you deleted in step 1, which will refresh the token for them and create a new long-lived token.

492: Invalid Session

If you receive a 492: Invalid Session error while integrating Facebook Ads, it means you don't have the appropriate role on the associated Facebook Page. To solve the problem:

Check Page Roles

  • Verify the roles assigned to your Facebook Page and ensure that the user attempting to access it has the appropriate role.
  • You might need a specific role (e.g., admin, editor, moderator) to perform particular actions on the page.

Adjust User Roles

  • If the user does not have the necessary role, you must adjust their roles accordingly.
  • Access the Page Settings on Facebook and modify the roles of the users as needed.

Confirm User's Role

  • Ask the user to confirm their assigned role on the Facebook Page.
  • They can access the Page settings or ask the Page administrator to check their page roles.

Grant Necessary Permissions

  • Make sure that you have been granted the necessary permissions to perform the actions you are attempting.
  • Some actions on Facebook Pages might require specific permissions or roles.

Contact Page Administrator

  • If you're not the administrator of the Facebook Page, contact the Page administrator to inquire about the user's role and permissions.
  • The administrator can make any necessary adjustments to user roles to resolve the issue.

Review Facebook's Page Policies

  • Review Facebook's guidelines and policies regarding Page roles and permissions to ensure compliance.
  • Ensure that the user's actions comply with Facebook's requirements and restrictions.

Troubleshoot Technical Issues

  • If the issue persists despite correct role assignments, check for any technical issues on your end.
  • Ensure that your app's integration with Facebook's Page management services is implemented correctly and is up to date.

Contact Facebook Support

  • If you're unable to resolve the issue on your own, consider contacting Facebook's support team for assistance.
  • Provide details about the error code and any relevant circumstances to help them assist you more effectively.