Skip to main content
GET
Get User Jobs

Get User Jobs

Retrieve job status information, counts, and statistics for the authenticated user. This simplified endpoint automatically detects the user from the API key, eliminating the need for user IDs in the URL.
Requires a user-specific API key with users:read permission. Global API keys should use the legacy routes.

Request

x-api-key
string
required
Your user-specific API key with users:read permission (format: bna_hexstring)

Query Parameters

startDate
number
Unix timestamp for filtering jobs from this date
endDate
number
Unix timestamp for filtering jobs until this date
status
string
Filter jobs by status (e.g., “completed”, “pending”, “failed”)
type
string
Filter jobs by type (e.g., “linkedin_action”, “data_enrichment”)

Examples

Get All Jobs

Get Jobs with Date Range

Get Jobs by Status

Response

userId
string
The authenticated user’s ID
success
boolean
Always true for successful requests
data
object
Job information and statistics

Advanced Use Cases

1. Job Status Monitoring Dashboard

2. Job Progress Tracking

3. Automated Job Cleanup

Legacy Routes

For backward compatibility, these legacy routes are still supported but require explicit user IDs:
  • GET /api/v2/users/jobs/userJobStatus/:userId - Get user job status
  • GET /api/v2/users/jobs/jobStatus - Get all jobs (requires jobs:read permission)
  • GET /api/v2/users/jobs/jobCounts - Get job counts only
  • PUT /api/v2/users/jobs/editJobMessage/:jobId - Edit job message (requires jobs:update)

Error Responses

Global API Key Used (400)

Invalid Permission (403)

Next Steps

LinkedIn Integration

Check LinkedIn integration status

User Integrations

Manage user integrations

Schedule Actions

Schedule LinkedIn actions

User Guide

Learn user management best practices