List Account Types
Account
List Account Types
Retrieve available platform account types and their authentication requirements
GET
List Account Types
Some crawlers require user authentication (like Facebook, LinkedIn) through cookies or session tokens. The
account_type object describes the required credentials for such modules.
Account Type Fields
| Field | Type | Description |
|---|---|---|
| id | string | Unique identifier of the account type |
| name | string | The technical name of the account type (e.g., facebook-sync) |
| domain | string | Name of the platform or website this account type connects to (e.g., Facebook) |
| baseurl | string | The base URL for the platform’s login or data-fetching endpoints |
| cookies | array | A list of cookie names required for authentication. Some cookies may be marked as required or optional |
Notes
- If the
cookiesarray is empty, it means all cookies from the user session are required for authentication. - Required cookies must be provided for the crawler to work. Missing cookies will result in authentication failure.
For implementation, always verify the required cookies in the cookies array when preparing your account object for a run.
Account Limits
Some account types include aparams object that defines limits or batch configurations for the crawler when authenticated. These values help control usage and message sending.
Account Limit Parameters
| Parameter | Type | Description |
|---|---|---|
| [attribute] | object | Represents the daily limit for a specific attribute (e.g., messages, profiles, searches) |
| batch | object | (Optional) Defines the maximum number of actions per launch based on the attribute (e.g., messages, profiles) |
| batch_hours | object | (Optional) Defines the delay in hours between batch launches during the day |
Headers
Your API authentication token. Value:
Token YOUR_API_KEYAccount types with empty cookies arrays require all session cookies. Use browser dev tools to extract the full cookie set.
Code Examples
Response
200