Vertical Response API Error

### Debugging Steps:

1. **Verify `$EMAILID` is not null:**
Ensure that `$EMAILID` is defined and contains a valid email address. Add a debugging statement like this:

if (empty($EMAILID)) {
       echo "EMAILID is not set or empty.";
   }

2. **Check for whitespace:**
Trim any extra whitespace from `$EMAILID` to avoid issues.

$EMAILID = trim($EMAILID);

3. **Validate `$EMAILID`:**
Confirm that `$EMAILID` is a properly formatted email address:

if (!filter_var($EMAILID, FILTER_VALIDATE_EMAIL)) {
       echo "Invalid email format: " . $EMAILID;
   }

4. **Inspect the API documentation:**
Ensure that the `field_name` value (`email_address`) is valid and correctly formatted as per the Vertical Response API documentation.

5. **Test with hardcoded values:**
Replace `$EMAILID` with a hardcoded string to verify that the issue is with the value being passed:

$searchResult = $vr->searchListMembers(array(
       'session_id' => $sid,
       'field_name' => 'email_address',
       'field_value' => 'test@example.com',
       'max_records' => 200
   ));

6. **Check `$sid`:**
Verify that `$sid` (session ID) is valid and not `null`.

### Example of Fixed Code:

$EMAILID = trim($EMAILID);

if (empty($EMAILID)) {
    die("Error: EMAILID is empty or null.");
}

if (!filter_var($EMAILID, FILTER_VALIDATE_EMAIL)) {
    die("Error: Invalid email format: $EMAILID");
}

$searchResult = $vr->searchListMembers(array(
    'session_id' => $sid,
    'field_name' => 'email_address',
    'field_value' => $EMAILID,
    'max_records' => 200
));

If the issue persists, it could be related to how the API handles arguments or a deeper issue with `$sid`. Reviewing API logs (if available) might help pinpoint the problem.

### Steps to Debug and Fix

1. **Ensure the Value is Set and Not Null:**
Confirm that `$CurrentRow['Email']` contains a valid value:

if (!isset($CurrentRow['Email'])) {
       die("Error: CurrentRow['Email'] is not set.");
   }
   if (empty($CurrentRow['Email'])) {
       die("Error: CurrentRow['Email'] is empty.");
   }

2. **Trim the Value:**
Ensure there’s no leading or trailing whitespace:

$EMAILID = trim($CurrentRow['Email']);

3. **Validate Email Format:**
Validate the email address to ensure it adheres to proper syntax:

if (!filter_var($EMAILID, FILTER_VALIDATE_EMAIL)) {
       die("Error: Invalid email format for EMAILID: $EMAILID");
   }

4. **Log or Echo the Value:**
Log the value of `$EMAILID` to confirm it is being correctly assigned:

echo "EMAILID: $EMAILIDn";

5. **Ensure the API Input is Properly Encoded:**
Some APIs may require string parameters to be encoded or sanitized. For example:

$EMAILID = htmlspecialchars($EMAILID, ENT_QUOTES, 'UTF-8');

6. **Hardcode a Test Value:**
Replace `$EMAILID` with a known valid email address to isolate the issue:

$EMAILID = "test@example.com";

7. **Check API Response with Debugging:**
Add a try-catch block to capture any additional error details:

try {
       $searchResult = $vr->searchListMembers(array(
           'session_id' => $sid,
           'field_name' => 'email_address',
           'field_value' => $EMAILID,
           'max_records' => 200
       ));
   } catch (Exception $e) {
       die("API Error: " . $e->getMessage());
   }

8. **Check `field_name`:**
Ensure `field_name` is correctly specified as `email_address`. If the API has different naming conventions, confirm this against the documentation.

9. **Verify `$sid`:**
Check that `$sid` (session ID) is valid and has not expired.

10. **API Logs:**
If the Vertical Response API has logs or a dashboard, check for detailed error messages related to your API call.

### Final Example:
Here’s the corrected and validated code:

$EMAILID = trim($CurrentRow['Email']);

if (!isset($EMAILID) || empty($EMAILID)) {
    die("Error: EMAILID is not set or empty.");
}

if (!filter_var($EMAILID, FILTER_VALIDATE_EMAIL)) {
    die("Error: Invalid email format: $EMAILID");
}

try {
    $searchResult = $vr->searchListMembers(array(
        'session_id' => $sid,
        'field_name' => 'email_address',
        'field_value' => $EMAILID,
        'max_records' => 200
    ));
} catch (Exception $e) {
    die("API Error: " . $e->getMessage());
}

If the error persists after these checks, it may indicate a problem with the API implementation. Consider contacting Vertical Response support for additional clarification.

—

### 1. **Ensure `$EMAILID` is a Proper String:**
Verify that `$EMAILID` is indeed a string (not an object, array, or any other type):

if (!is_string($EMAILID)) {
    die("Error: EMAILID is not a string.");
}

—

### 2. **Encode Special Characters:**
Sometimes special characters in email addresses (e.g., `+`) can cause issues. Encode the email address before sending it to the API:

$EMAILID = urlencode(trim($EMAILID));

—

### 3. **Hardcode a Valid Email Address for Testing:**
Test with a hardcoded email address to rule out any data-related issues:

$EMAILID = "test@example.com";
$searchResult = $vr->searchListMembers(array(
    'session_id' => $sid,
    'field_name' => 'email_address',
    'field_value' => $EMAILID,
    'max_records' => 200
));

If this works, the issue is likely with the value being retrieved from `$CurrentRow['Email']`.

—

### 4. **Check API Requirements:**
Ensure that all other fields in the request (`session_id`, `field_name`, `field_value`, `max_records`) meet the API's requirements:
– `session_id` should be valid and active.
– `field_name` must match exactly with the API's expected value (`email_address`).
– `max_records` should be within the acceptable range (e.g., 200).

—

### 5. **Debug API Response:**
Use a try-catch block to catch detailed exceptions:

try {
    $searchResult = $vr->searchListMembers(array(
        'session_id' => $sid,
        'field_name' => 'email_address',
        'field_value' => $EMAILID,
        'max_records' => 200
    ));
    print_r($searchResult);
} catch (Exception $e) {
    die("API Exception: " . $e->getMessage());
}

—

### 6. **Verify API SDK Version:**
Ensure that the Vertical Response API SDK/library being used is up-to-date. An outdated SDK may cause compatibility issues.

—

### 7. **Check for Leading/Trailing Spaces or Hidden Characters:**
Hidden characters or invisible spaces might exist in `$EMAILID`. Use this to debug:

echo "EMAILID Length: " . strlen($EMAILID) . "n";
var_dump($EMAILID);

Make sure the length matches what you expect, and there are no unexpected characters.

—

### 8. **Contact Vertical Response Support:**
If none of the above resolves the issue, it’s possible that:
– There's an undocumented API constraint.
– The API key or session ID is invalid.

Share the exact request payload and error message with their support team for further clarification.

Let me know if you'd like assistance with any specific debugging steps!