> ## Documentation Index > Fetch the complete documentation index at: https://www.vollna.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Get job competition > Returns the competition on one job you sent a proposal to: applicants, interviews and hires 1, 4 and 14 days after posting, next to the niche of the job's categories. Counts against the daily niche_difficulty cap ## OpenAPI ````yaml get /projects/{id}/competition openapi: 3.0.4 info: title: Vollna API description: API for managing Upwork profiles, proposals, results, and filters version: 1.0.0 servers: - url: https://api.vollna.com/v1 security: [] tags: - name: Profiles description: Manage Upwork profiles - name: Proposals description: Access and manage Upwork proposals - name: Results description: View monitoring results and projects - name: Filters description: Manage monitoring filters - name: Auto Bidding description: Manage auto bidding jobs and setups - name: Account description: The token team's account, plan and meters - name: Invitations description: Upwork invitations - name: Projects description: Upwork jobs and their competition - name: AI Qualifier description: A filter's AI qualifier and its verdicts - name: Market Insights description: Upwork market analytics and saved searches - name: Proposal Templates description: Proposal templates and their results paths: /projects/{id}/competition: get: tags: - Projects summary: Get job competition description: >- Returns the competition on one job you sent a proposal to: applicants, interviews and hires 1, 4 and 14 days after posting, next to the niche of the job's categories. Counts against the daily niche_difficulty cap parameters: - name: id in: path required: true description: Project ID of a job one of your Upwork profiles bid on schema: type: integer responses: '200': description: Successful operation content: application/json: schema: type: object properties: data: type: object properties: job: type: object properties: projectId: type: integer title: type: string url: type: string publishedAt: type: string format: date-time nullable: true snapshots: type: array items: $ref: '#/components/schemas/ActivitySnapshot' applicantsDay1: type: integer nullable: true niche: allOf: - $ref: '#/components/schemas/NicheDifficulty' - type: object properties: categoryIds: type: array items: type: integer description: >- available is false with a reason when the job has no category or the plan has no full Market Insights '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '402': $ref: '#/components/responses/PaymentRequired' '403': $ref: '#/components/responses/Forbidden' '404': description: The job is not one your Upwork profiles bid on content: application/json: schema: $ref: '#/components/schemas/ServiceError' '429': description: >- The daily niche_difficulty cap is used up, or the rate limit is reached content: application/json: schema: $ref: '#/components/schemas/ServiceError' security: - apiToken: [] components: schemas: ActivitySnapshot: type: object description: What Upwork showed on the job on one day properties: dayOffset: type: integer description: 'Days after the job was posted: 1, 4 or 14' capturedAt: type: string format: date-time status: type: string description: Job status on Upwork, for example ACTIVE nullable: true applicants: type: integer nullable: true invitedToInterview: type: integer nullable: true hired: type: integer nullable: true invitationsSent: type: integer nullable: true positions: type: integer description: Positions the client wants to fill nullable: true NicheDifficulty: type: object description: >- How hard a niche is to win, from Upwork's own counts over the last 180 days properties: available: type: boolean description: >- false when fewer than 20 jobs in the scope have activity data over the last 180 days reason: type: string description: Why the figures are missing; only when available is false jobs: type: integer description: Jobs with activity data in the scope avgApplicants: type: number interviewRatePct: type: number fillRatePct: type: number difficulty: type: integer description: 0 to 100; higher is harder to win minimum: 0 maximum: 100 crowding: type: integer odds: type: integer reliability: type: integer ServiceError: type: object properties: error: type: string description: Short error title example: Validation failed message: type: string description: What went wrong and what to send instead, written for the user fields: type: object description: >- Per-field messages keyed by dot path, when several fields fail at once additionalProperties: type: string Error: type: object properties: error: type: string responses: BadRequest: description: >- Invalid request. message says what to send instead; fields names each invalid field content: application/json: schema: $ref: '#/components/schemas/ServiceError' Unauthorized: description: Missing or unknown API token content: application/json: schema: $ref: '#/components/schemas/Error' PaymentRequired: description: The team's subscription is not active content: application/json: schema: $ref: '#/components/schemas/Error' Forbidden: description: >- The plan has no API access, or the token team may not do this. message says why content: application/json: schema: $ref: '#/components/schemas/ServiceError' securitySchemes: apiToken: type: apiKey name: X-API-TOKEN in: header description: API token for authentication ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.