Resolving Flatfile API Access Issues After Domain Change

Last updated: October 1, 2025

Flatfile API Access Issues After Domain Change

When changing your application's domain, you may need to ensure proper access to Flatfile API endpoints.

Symptoms

  • Receiving "Unexpected Error" with "fetch failed" messages when trying to access Flatfile services

  • Issues accessing Flatfile spaces after changing your application domain

Possible Causes

  • Flatfile API endpoints not properly allowlisted in your infrastructure configuration

  • Network or firewall restrictions blocking access to Flatfile services

Solutions

Solution 1: Verify and Update API Access Configuration

  1. Ensure your infrastructure configuration includes access to all necessary Flatfile API endpoints

  2. Add the required regional server URLs found in the Flatfile documentation

  3. If using infrastructure as code (like Terraform), update your configuration to include these endpoints

Solution 2: Verify Basic API Connectivity

  1. Test basic connectivity to Flatfile API using curl or similar tools

  2. Ensure you can reach the regional API servers for your deployment

  3. Check your network logs or browser developer tools if issues persist

When to Contact Support

If the above solutions do not resolve the issue, please contact our support team with the following information:

  • Complete error messages and stack traces

  • Network logs or HAR file from browser developer tools

  • Details about any recent domain or environment changes

  • Results of basic connectivity tests to Flatfile API endpoints