> ## 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 status

> Retrieve the current status of an auto bidding job



## OpenAPI

````yaml get /auto-bidding/jobs/{id}/status
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:
  /auto-bidding/jobs/{id}/status:
    get:
      tags:
        - Auto Bidding
      summary: Get job status
      description: Retrieve the current status of an auto bidding job
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: integer
          description: The job ID
      responses:
        '200':
          description: Successful operation
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AutoBiddingJobStatusResponse'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '402':
          $ref: '#/components/responses/PaymentRequired'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          description: Job not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '429':
          $ref: '#/components/responses/TooManyRequests'
      security:
        - apiToken: []
components:
  schemas:
    AutoBiddingJobStatusResponse:
      type: object
      properties:
        success:
          type: boolean
        job:
          $ref: '#/components/schemas/AutoBiddingJobStatus'
    Error:
      type: object
      properties:
        error:
          type: string
    AutoBiddingJobStatus:
      type: object
      properties:
        id:
          type: integer
        upwork_job_id:
          type: string
        status:
          type: string
          description: >-
            Available values: `scheduled`, `processing`, `applied`, `skipped`,
            `failed`
        reason:
          type: string
          nullable: true
          description: >-
            Reason for the job status (skip reason or error message), available
            only for `skipped` and `failed` statuses
        status_title:
          type: string
          description: Human-readable status title
        scheduled_at:
          type: string
        processed_at:
          type: string
          nullable: true
        error_message:
          type: string
          nullable: true
        retry_count:
          type: integer
        is_ready_for_processing:
          type: boolean
        upwork_application_uid:
          type: string
          nullable: true
          description: >-
            Upwork application UID of the submitted proposal. Use it with `GET
            /proposals/by-uid/{applicationUid}` to fetch the proposal.
    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
  responses:
    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'
    TooManyRequests:
      description: More than 30 requests a minute. See Rate Limiting
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  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.