List Tracking
Retrieve all tracking configurations associated with your API key, including their status, performance metrics, and configuration details.Endpoint
HTTP Request
Query Parameters
page
- Type: Integer
- Description: Page number for pagination
- Default: 1
- Example:
?page=2
limit
- Type: Integer
- Description: Number of tracking configurations per page
- Default: 20
- Maximum: 100
- Example:
?limit=50
status
- Type: String
- Description: Filter tracking configurations by status
- Options:
active,inactive,paused,error - Example:
?status=active
type
- Type: String
- Description: Filter by tracking type
- Options:
keyword,user,topic - Example:
?type=keyword
search
- Type: String
- Description: Search tracking configurations by name or description
- Example:
?search=javascript
sort
- Type: String
- Description: Sort field and direction
- Options:
created_at,updated_at,name,items_tracked - Format:
field:ascorfield:desc - Default:
created_at:desc - Example:
?sort=items_tracked:desc
Response Format
Success Response (200 OK)
Tracking Object Fields
Basic Information
- id: Unique tracking identifier
- name: Human-readable tracking name
- type: Tracking type (keyword, user, topic)
- active: Whether tracking is currently active
- description: Detailed description of tracking purpose
Configuration
- config: Main tracking configuration
- filters: Additional filtering criteria
- delivery: Data delivery configuration
Status Information
- status: Current tracking status
active: Tracking is running and collecting datainactive: Tracking is disabledpaused: Tracking is temporarily pausederror: Tracking has encountered errors
Timestamps
- created_at: When tracking was created
- updated_at: When tracking was last updated
Statistics
- items_tracked: Total number of items tracked
- last_item_at: Timestamp of last tracked item
- daily_average: Average items tracked per day
- success_rate: Percentage of successful data collection
- error_count: Number of errors encountered
Implementation Examples
JavaScript (Node.js)
Python
cURL
Advanced Filtering and Sorting
Status-Based Filtering
Type-Based Filtering
Search Functionality
Sorting Options
Pagination Handling
Performance Monitoring
Tracking Health Analysis
Automated Monitoring
Error Handling
Common Error Responses
401 Unauthorized
429 Too Many Requests
Error Handling Implementation
Best Practices
For Monitoring
- Regular Checks: Monitor tracking status and performance regularly
- Alert Thresholds: Set appropriate alert thresholds for your use case
- Performance Analysis: Track success rates and data volume
- Proactive Maintenance: Address issues before they become critical
For Performance
- Pagination: Use pagination for large tracking lists
- Filtering: Use specific filters to reduce data volume
- Caching: Cache tracking data to reduce API calls
- Batch Operations: Process multiple tracking configurations together
For Management
- Regular Reviews: Periodically review tracking configurations
- Optimization: Optimize tracking based on performance data
- Documentation: Document tracking purposes and configurations
- Cleanup: Remove or deactivate unused tracking configurations