> ## 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 skill requests > See every skill you asked for and where it stands. **Scope:** `skills:request` ## OpenAPI ````yaml /blue-collar-api/api-reference/openapi.json get /skill-requests 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: /skill-requests: get: tags: - Skill requests summary: List skill requests description: |- See every skill you asked for and where it stands. **Scope:** `skills:request` operationId: listSkillRequests parameters: - name: status in: query required: false schema: type: string enum: - pending - approved - merged - rejected - duplicate_of example: pending - 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, oldest first 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: request_id: type: string name: type: string status: type: string enum: - pending - approved - merged - rejected - duplicate_of collar: anyOf: - type: string enum: - blue - grey - white - type: 'null' domain_hint: anyOf: - type: string - type: 'null' mandate_external_id: anyOf: - type: string - type: 'null' requested_by: anyOf: - type: string - type: 'null' skill: anyOf: - type: object properties: skill_id: type: string name: type: string - type: 'null' description: >- The existing skill for duplicate_of / merged, or the new one when approved reason: anyOf: - type: string - type: 'null' description: Why it was rejected created_at: type: string updated_at: type: string 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: - request_id: skr_9f2c41d7a8b3e65f1c02 name: Reach Truck Operation status: pending collar: blue domain_hint: Logistics and warehousing mandate_external_id: job-10452 requested_by: recruiter_1042 skill: null reason: null created_at: '2026-10-09T10:20:00.000Z' updated_at: '2026-10-09T10:20:00.000Z' count: 1 total: 1 next_cursor: null has_more: false security: - ApiKey: [] SecretKey: [] x-codeSamples: - lang: bash label: cURL source: pcall GET "/api/v1/partner/skill-requests?status=pending&limit=50" - lang: javascript label: JavaScript source: >- const res = await call("GET", "/api/v1/partner/skill-requests?status=pending&limit=50"); const { data } = await res.json(); - lang: python label: Python source: >- res = call("GET", "/api/v1/partner/skill-requests?status=pending&limit=50") data = res.json()["data"] components: 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.