Problem

Currently, only PUBLIC_BASE_URL has trailing slash sanitization applied via the sanitize_base_url() helper function. The API_BASE_URL does not undergo the same normalization, which can lead to inconsistent behavior when users provide URLs with trailing slashes.

Since all API endpoints start with / (e.g., /v1/instances, /v1/products), and the URL construction in src/api/client.rs uses simple concatenation:

let url = format!("{}{}", api_base_url, endpoint);

A trailing slash in API_BASE_URL would result in double slashes like:
https://api.cloudzy.com/developers//v1/instances

Solution

Apply the existing sanitize_base_url() function to API_BASE_URL in addition to PUBLIC_BASE_URL to ensure consistent handling of trailing slashes.

Changes Required

In src/config.rs, update the get_api_base_url() function on line 26:

Before:

pub fn get_api_base_url() -> String {
    env::var("API_BASE_URL").unwrap_or_else(|_| DEFAULT_API_BASE_URL.to_string())
}

After:

pub fn get_api_base_url() -> String {
    sanitize_base_url(&env::var("API_BASE_URL").unwrap_or_else(|_| DEFAULT_API_BASE_URL.to_string()))
}

This change:

• ✅ Prevents double slashes in API URLs
• ✅ Maintains backward compatibility - URLs without trailing slashes work identically
• ✅ Provides consistent behavior with PUBLIC_BASE_URL
• ✅ No breaking changes - existing implementations continue to work

Testing

The fix should be tested with:

1. API_BASE_URL=https://api.cloudzy.com/developers (no trailing slash)
2. API_BASE_URL=https://api.cloudzy.com/developers/ (with trailing slash)
3. API_BASE_URL= (empty, should use default)

All cases should produce valid API URLs without double slashes.