Skip to main content
GET
/
api
/
proxy
/
account
/
{accountId}
Get Account Proxy Configuration
curl --request GET \
  --url https://onlyautomator.com/api/proxy/account/{accountId} \
  --header 'Authorization: Bearer <token>'
{
  "success": true,
  "data": {
    "proxy_id": "ws_proxy_12345abcde",
    "proxy_address": "185.123.101.234",
    "proxy_port": 8080,
    "proxy_username": "username123",
    "proxy_country_code": "US",
    "proxy_assigned_at": "2023-09-15T14:32:45Z",
    "proxy_mode": "auto",
    "proxy_is_active": true,
    "proxy_region_preference": "EU",
    "proxy_city_name": "Frankfurt"
  }
}

​
Get Account Proxy Configuration

This endpoint retrieves the current proxy configuration for a specific OnlyFans account, including proxy address, port, authentication credentials (username only in this view), country, mode, and activity status.
The password is intentionally omitted from this response for security reasons. Use the specific backend service function (getDecryptedAccountProxyConfig) if the password is required server-side.

​
Authentication

This endpoint requires authentication via bearer token representing a valid user session managed by Supabase Auth (cookies).Testing Note: Due to the requirement for a live user session, this endpoint cannot be successfully tested directly using the ‘Send’ button in this documentation with a static token.To test:
  1. Call this endpoint from your web application after logging in.
  2. Use curl or a similar tool with a valid, current user JWT obtained from your browser’s session after logging in.
Retrieving JWT Token for Testing: To test endpoints requiring a user session with tools like curl, you need the JWT access token stored by Supabase Auth in your browser.
  1. Log in to your application normally in your browser.
  2. Open Developer Tools (usually F12).
  3. Go to the Application tab (it might be called Storage in Firefox).
  4. Under the Storage section, find Cookies and select your application’s domain (e.g., http://localhost:3000 or https://onlyautomator.com).
  5. Look for a cookie named similar to sb-access-token (the exact name might vary slightly based on Supabase configuration).
  6. Copy the entire value of this cookie. This is your Bearer token.
  7. Use this copied value in the Authorization: Bearer <your_copied_token> header for your curl or other API tool requests.
Note: This token has a limited lifetime and you’ll need to copy a fresh one after it expires.

​
Response Example

{
  "data": {
    "proxy_id": "ws_proxy_12345abcde",
    "proxy_address": "185.123.101.234",
    "proxy_port": 8080,
    "proxy_username": "username123",
    // Password omitted
    "proxy_country_code": "US",
    "proxy_assigned_at": "2023-09-15T14:32:45Z",
    "proxy_mode": "auto",
    "proxy_is_active": true,
    "proxy_region_preference": "EU"
  }
}

​
Error Codes

This table provides context beyond the basic OpenAPI status codes.
Status CodeDescription
400Missing or invalid accountId parameter.
401Authentication token is missing or invalid.
404The specified accountId does not exist or has no proxy configuration.
500An internal server error occurred while fetching the data.
503Potentially relevant if a backend connectivity check fails during retrieval (though less common for GET).

​
Code Examples

// Using fetch
const getProxyConfig = async (accountId, apiToken) => {
  const response = await fetch(`https://onlyautomator.com/api/proxy/account/${accountId}`, {
    method: 'GET',
    headers: {
      'Content-Type': 'application/json',
      'Authorization': `Bearer ${apiToken}`
    }
  });
  
  if (!response.ok) {
     const errorData = await response.json();
     throw new Error(`API Error (${response.status}): ${errorData.error}`);
  }
  return await response.json();
};

// Example usage
getProxyConfig('acc123', 'your_api_token')
  .then(data => console.log(data))
  .catch(error => console.error('Error fetching proxy config:', error));

​
Security Considerations

  • The proxy password is intentionally not included in this endpoint’s response.
  • Ensure the bearer token used has appropriate, limited permissions.

Authorizations

​
Authorization
string
header
required

Standard user JWT token for authentication.

Headers

​
Authorization
string
required

Bearer token for authentication (JWT)

Path Parameters

​
accountId
string<uuid>
required

The unique identifier of the OnlyFans account.

Response

Proxy configuration retrieved successfully.

​
success
boolean
Example:

true

​
data
object