> ## Documentation Index > Fetch the complete documentation index at: https://docs.userecord.io/llms.txt > Use this file to discover all available pages before exploring further. # List campaigns > List your organisation’s campaigns; filter by `mandate_id` to see one job’s. **Scope:** `campaigns:write` or `results:read` ## OpenAPI ````yaml /blue-collar-api/api-reference/openapi.json get /campaigns openapi: 3.1.0 info: title: Record Blue Collar API version: 1.0.0 description: >- Run Record candidate verification from your own system. You need two things: your **key id** and your **secret**. Everything else is generated. See Authentication for how. servers: - url: https://api-bc.userecord.io/api/v1/partner description: Blue Collar API security: [] tags: - name: Skills description: The skill taxonomy, read live a page at a time - name: Skill requests description: Ask Record to add a missing skill - name: Lookups description: >- Lookups for filling in a job mandate: places in India, the countries an abroad job can be in, and the employment types and shifts the playground offers - name: Workflows description: >- Your organisation's blue-collar workflows (read all; change and soft-delete only the ones you created) - name: Job mandates description: >- Your organisation's job mandates, addressed by Record's mandate_id (read all; change only the ones you created) - name: Campaigns description: Contact candidates for one of your jobs and verify them. Spends credits - name: Results description: >- What Record collected from each candidate: status (pending, completed, declined, failed) and an output of answers and verdicts - name: Events description: >- Pull your result events and acknowledge them: the safety net behind the webhook, and a way to receive results without exposing a URL - name: Webhooks description: >- Endpoints that Record POSTs result events to: signed, retried until you acknowledge, replayable - name: Analytics description: >- The workflow Overview analytics of the Record playground: funnel, channels, follow-ups, calls, drop-offs, languages (read-only, scope analytics:read) paths: /campaigns: get: tags: - Campaigns summary: List campaigns description: >- List your organisation’s campaigns; filter by `mandate_id` to see one job’s. **Scope:** `campaigns:write` or `results:read` operationId: listCampaigns parameters: - name: mandate_id in: query required: false description: >- Record's mandate id (JM_...): the mandate_id returned when you create the mandate schema: type: string pattern: ^JM_[A-Z0-9]{10,40}$ example: JM_261009101612456H3N8W2L5C9V1Z4 - name: job_id in: query required: false description: 'Your own id (1 to 128 of A-Z a-z 0-9 . _ : -)' schema: type: string pattern: ^[A-Za-z0-9._:-]{1,128}$ - name: status in: query required: false schema: type: string enum: - draft - waiting_for_questions - blocked - sending - paused - completed - cancelled example: sending - name: limit in: query required: false description: 1 to 100, default 50 schema: type: integer minimum: 1 maximum: 100 default: 50 example: 50 - name: cursor in: query required: false description: The next_cursor of the previous page schema: type: string maxLength: 512 responses: '200': description: One page content: application/json: schema: type: object properties: success: const: true type: boolean message: type: string data: type: object properties: items: type: array items: type: object properties: campaign_id: type: string external_id: anyOf: - type: string - type: 'null' mandate_id: type: string description: >- Record's job mandate id: the mandate this campaign runs under job_id: anyOf: - type: string - type: 'null' description: >- Your job id; null for a mandate created without one name: type: string status: type: string enum: - draft - waiting_for_questions - blocked - sending - paused - completed - cancelled description: >- draft: not started. waiting_for_questions: started, goes out by itself once the job's questions are ready. blocked: see `blocked`. sending: candidates are being contacted. blocked: anyOf: - type: object properties: reason: type: string message: type: string - type: 'null' description: >- Why a started campaign is not going out, when it is stuck language: type: string candidates: type: object properties: total: type: integer sent: type: integer description: Contacted queued: type: integer description: Waiting to be contacted failed: type: integer description: Could not be reached at all created_at: type: string started_at: anyOf: - type: string - type: 'null' sent_at: anyOf: - type: string - type: 'null' paused_at: anyOf: - type: string - type: 'null' count: type: integer description: How many items this page holds total: anyOf: - type: integer - type: 'null' description: >- How many items match your filters across all pages. null when that cannot be counted cheaply: a filter worked out per item (status, progress) on a list that is large next_cursor: anyOf: - type: string - type: 'null' description: >- Pass as `cursor` for the next page; null on the last page has_more: type: boolean description: >- true while there is a next page (with a status or progress filter that page can still come back empty) example: success: true data: items: - campaign_id: asmnt_9f2c41d7a8b3e65f external_id: ats-campaign-5521 mandate_id: JM_261009101612456H3N8W2L5C9V1Z4 job_id: job-10452 name: Warehouse Associate - October batch status: sending blocked: null language: english candidates: total: 3 sent: 3 queued: 0 failed: 0 created_at: '2026-10-05T09:12:44.000Z' started_at: '2026-10-05T09:12:45.000Z' sent_at: '2026-10-05T09:30:00.000Z' paused_at: null count: 1 total: null next_cursor: null has_more: false '400': description: '`VALIDATION_FAILED`: Bad `mandate_id` format, `cursor` or `limit`.' content: application/json: schema: $ref: '#/components/schemas/Error' security: - ApiKey: [] SecretKey: [] x-codeSamples: - lang: bash label: cURL source: >- pcall GET "/api/v1/partner/campaigns?mandate_id=JM_261009101612456H3N8W2L5C9V1Z4&status=sending&limit=50" - lang: javascript label: JavaScript source: >- const res = await call("GET", "/api/v1/partner/campaigns?mandate_id=JM_261009101612456H3N8W2L5C9V1Z4&status=sending&limit=50"); const { data } = await res.json(); - lang: python label: Python source: >- res = call("GET", "/api/v1/partner/campaigns?mandate_id=JM_261009101612456H3N8W2L5C9V1Z4&status=sending&limit=50") data = res.json()["data"] components: schemas: Error: type: object properties: success: const: false type: boolean error: type: object properties: code: type: string enum: - VALIDATION_FAILED - LIMIT_EXCEEDED - UNAUTHORIZED - SCOPE_MISSING - FORBIDDEN - HTTPS_REQUIRED - NOT_FOUND - CONFLICT - WORKFLOW_IN_USE - INSUFFICIENT_CREDITS - IDEMPOTENCY_KEY_REQUIRED - IDEMPOTENCY_KEY_REUSED - IDEMPOTENCY_IN_PROGRESS - PAYLOAD_TOO_LARGE - UNSUPPORTED_MEDIA_TYPE - RATE_LIMITED - COOLDOWN - DAILY_CAP - SERVICE_DISABLED - SERVER_ERROR message: type: string details: type: array items: type: object properties: path: type: string message: type: string request_id: type: string description: Quote it to Record support securitySchemes: ApiKey: type: apiKey in: header name: x-api-key description: Your key id, `VFN_TEST_…` or `VFN_LIVE_…`. Sent on every request. SecretKey: type: apiKey in: header name: x-secret-key description: >- Your secret, `VFN_SK_…`. **Not a real header, and never sent to the API.** It is only a form field for Try it, which uses it to sign your request in your browser. In your own code you sign each request with the secret and send `x-api-key`, `x-timestamp` and `x-signature` (see Authentication). ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.