Skip to main content

Instagram "400 Session Invalid" Error - Complete Fix Guide

Getting the "400 Session Invalid" error with Instagram? This guide has every fix, from clearing permissions to advanced steps. Solve it now.

Updated this week

Encountering the "400 Session Invalid" error when connecting your Instagram account to Spur can be frustrating, but it's often easily resolved. This guide prioritizes the most common and straightforward solutions first.
​

Phase 1: Quick & Easy Fixes

Try these steps first. They resolve the issue for most users:

  1. Perform a Fresh Login:

    • Log out of your Instagram account on all devices and browsers.

    • Log back into Instagram directly first, then attempt the connection to Spur.

  2. Switch Your Network:

    • Disconnect from your current Wi-Fi and try using your mobile data.

    • If possible, test with an entirely different Wi-Fi network.

  3. Try a Different Browser:

    • Use an Incognito or Private window in your current browser to bypass cached data.

    • If that doesn't work, try connecting with a completely different browser (e.g., switch from Chrome to Safari).

Phase 2: Common Account-Specific Solutions

If the above steps didn't work, these fixes address common issues within your Instagram account settings:

  1. Clear Spur's Permissions Directly from Instagram:

    • Open the Instagram app on your mobile device.

    • Go to your profile β†’ tap the menu (☰) β†’ Settings and Privacy.

    • Scroll down and tap on Website permissions.

    • Go to the Apps and websites tab.

    • In the "Active" list, look for Spur or any other connected services (like Squarespace, Pinterest, etc.).

    • Tap Remove for any connections you see.

    • Also, check the "Expired" tab and remove any old connections found there, as they can sometimes block new ones.

    • After removing the connections, wait about 5 minutes, then return to Spur and try connecting again.

  2. Ensure Website Embedding is Enabled:

    • In Instagram's Settings and Privacy, go to Sharing and remix.

    • Make sure the option to "Allow embedding" or allow sharing to external websites is toggled ON.

Phase 3: More Advanced Troubleshooting

These solutions are less common but have worked for some users.

  1. Check for Multiple Linked Business Accounts:

    • Conflicts can arise if you have more than one professional account linked.

    • Temporarily unlink any extra business/creator accounts, leaving only the one you intend to connect to Spur.

  2. Verify Your Account Type:

    • Your Instagram account must be a Professional Account ("Business" or "Creator") to connect to tools like Spur. Personal accounts cannot be used.

  3. Try a Different Device and a Full Cache/Cookie Clear:

    • If you're on a desktop, try connecting using your mobile phone. Ensure to fully clear all browser cache and cookies

    • If possible, try a different computer entirely

  4. Check for an Insufficient Photo Count (Potentially Relevant for New Accounts):

    • Some integrations have failed for users with few posts.

    • If it's a new account, upload some content (10-15 photos) before trying again.

Phase 4: Advanced & Uncommon Fixes

Only try these if all previous steps have failed.

  1. Use a VPN:

    • A VPN can help bypass temporary IP-based blocks.

    • Enable a VPN to change your location, restart your device, and then try connecting from the new IP address.

  2. Wait 24 Hours:

    • Sometimes, the issue is on Instagram's end. The problem might resolve itself after a day.

Still Not Working?

If you have completed every step in this guide and are still facing the error, please contact our support team. To help us diagnose the issue quickly, please provide:

  • A screenshot of the "400 Session Invalid" error message.

  • The device, operating system, and browser you are using.

  • Confirmation that you have tried clearing the connection from both the mobile and desktop versions of Instagram.

  • How long this error has been occurring.

Pro Tip: Once your account is successfully connected, avoid disconnecting and reconnecting it unless absolutely necessary. The connection process can be sensitive, and this error can sometimes reappear after being resolved.

Did this answer your question?