two files merged into one, improved formatting.

Author: mrdavidorok

docs/troubleshooting/api/api_charset_and_encoding_fix_guide.md

@@ -11,7 +11,7 @@ This guide shows you how to resolve such issues and ensure your API outputs are
 
 Follow the steps below: 
 
-- **Set Proper Request Headers**
+1. **Set Proper Request Headers**
 
     Make sure your API call includes the appropriate headers to instruct the server on how to format the response. Add the following headers to your API configuration:
 
@@ -24,7 +24,7 @@ Follow the steps below:
 
     ![Setting Content-Type and Charset headers](../assets/20250430121409119593.png)
 
-- **Enable UTF-8 Decoding in FlutterFlow**
+2. **Enable UTF-8 Decoding in FlutterFlow**
 
     If the server does not specify encoding—or if you're still getting corrupted text—you can configure FlutterFlow to decode the API response as UTF-8 manually.
 

docs/troubleshooting/api/client-server_errors_during_the_api_call.md

@@ -6,13 +6,11 @@ title: Client-Server Errors during the API call
 # Client-Server Errors During the API Call
 
 
-When calling an API in FlutterFlow, you may run into client-server errors. These typically come as status codes that indicate what went wrong—either on your end (the client) or on the server you're requesting data from.
+When calling an API in FlutterFlow, you may run into client-server errors. These typically come as status codes that indicate what went wrong, either on your end (the client) or on the server you're requesting data from.
 
 This guide will help you understand the most common API error codes and how to fix them.
 
-## What is an API?
-
-An API (Application Programming Interface) lets two systems communicate with each other. When you make an API call, you're sending a request from your app (client) to a server, which responds with data.
+To learn more about APIs, check out our [API documentation guide](/resources/backend-logic/rest-api/).
 
 ## Common client-side status codes
 
@@ -23,7 +21,7 @@ These errors are usually caused by incorrect requests from the client side.
     Your request isn’t properly formatted. This could be due to a missing parameter, a typo, or incorrect syntax.
 
     :::tip
-    Check the API documentation to ensure you're including the correct fields and headers.
+    Check the API's own documentation to ensure you're including the correct fields and headers.
     :::
 
     ![400 Example](../assets/20250430121351345482.png)
@@ -90,7 +88,32 @@ These errors occur on the API server side.
 
     The API server took too long to respond. Try simplifying your request or reducing the size of the data being sent.
 
+
+**Troubleshooting Steps**
+
+- **Clear Browser Cache and Cookies**
+
+    If you're encountering a 400 Bad Request error, clearing your browser's cache and cookies can resolve issues related to expired or invalid data.
+
+- **Verify the Requested URL** 
+
+    Ensure the URL or endpoint is correct. Remember, domain names are case-sensitive.
+
+- **Adjust Request Parameters**
+
+    For 400 errors, check if the file size is too large (for POST requests) or if there are any other incorrect parameters.
+
+- **Consult API Documentation**
+
+    Always refer to the API's official documentation for specific requirements and troubleshooting tips.
+
+- **Contact API Support**
+
+    If you continue to face issues, reaching out to the API's support team can provide further assistance and insights into resolving the problem.
+
+Understanding these common API error status codes and their solutions can significantly smooth the development process, ensuring more efficient and effective communication between your application and the APIs you rely on.
+
 :::tip[Final tips]
-- Always check the API documentation, inspect your request, and look up error messages. If the issue persists, contact the API provider.
-- Once you fix the issue, your calls should return a `200 OK`—which means everything is working as expected!
+- Always check the API's own documentation, inspect your request, and look up error messages. If the issue persists, contact the API provider.
+- Once you fix the issue, your calls should return a `200 OK`, which means everything is working as expected!
 :::

docs/troubleshooting/api/securing_your_api_keys_in_private_api_calls.md

@@ -8,11 +8,11 @@ title: Securing Your API Keys in Private API Calls
 
 Ensuring the security of API keys is a critical aspect of building and maintaining a safe and reliable application. In the realm of private API calls, it's especially important to make sure your API keys are not exposed. This article aims to provide a best-practices guide on where to place your API keys to increase security in a FlutterFlow environment.​
 
-## The Misconception: Private API Calls Secure Everything
+**The Misconception: Private API Calls Secure Everything**
 
-Many users assume that simply marking an API call as 'private' is enough to protect all associated data. However, this is not the case. Private API calls run in a Cloud Function, which means any keys or sensitive data in the body will be secure — as long as they're not passed in from the frontend. Even in private API calls, if you're loading an API key from the frontend (like from Firebase remote configs), then you're still exposing it.​
+Many users assume that simply marking an API call as 'private' is enough to protect all associated data. However, this is not the case. Private API calls run in a Cloud Function, which means any keys or sensitive data in the body will be secure, as long as they're not passed in from the frontend. Even in private API calls, if you're loading an API key from the frontend (like from Firebase remote configs), then you're still exposing it.​
 
-## Where to Put Your API Keys
+## Secure Placement of API Keys in Your Project
 
     The ideal way to secure an API key is to include it in a request header or directly within the API endpoint URL. This ensures that it is never passed in from the client, thereby maintaining its confidentiality.​
 
@@ -29,7 +29,7 @@ Many users assume that simply marking an API call as 'private' is enough to prot
     ```
     The key should never be a variable that gets passed in from the frontend, as that would make it accessible via the client-side code, defeating the purpose of using private API calls for secure operations.
 
-## How to verify that your key is secured
+## Verifying the Security of Your API Key
 
     After implementing these changes, a straightforward way to verify that your key is secured is by downloading your application code and checking to make sure the API key doesn’t appear in any frontend files.​