> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getprimo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Ignore an offboarding

> Discard a pending offboarding: cancels it with the open tasks of its ticket, clears the last day of the employee and gives them back their access, so they stay in the company. Only a PENDING offboarding can be ignored (`ONLY_PENDING_OFFBOARDING_CAN_BE_IGNORED` otherwise): once a step has started, cancel the remaining tasks with `updateTaskStatus`. Refused with `OFFBOARDING_NOT_FOUND` for an offboarding of another company.

Key: WriteScope: Company


## OpenAPI

````yaml https://api.getprimo.com/openapi.json post /offboardings/{offboardingId}/ignore
openapi: 3.1.1
info:
  title: Public API - BETA
  description: Read docs on https://docs.getprimo.com/
  version: '1.0'
  contact: {}
servers:
  - url: https://api.getprimo.com
security:
  - apikey: []
tags: []
paths:
  /offboardings/{offboardingId}/ignore:
    post:
      tags:
        - Offboardings
      summary: Ignore an offboarding
      description: >-
        Discard a pending offboarding: cancels it with the open tasks of its
        ticket, clears the last day of the employee and gives them back their
        access, so they stay in the company. Only a PENDING offboarding can be
        ignored (`ONLY_PENDING_OFFBOARDING_CAN_BE_IGNORED` otherwise): once a
        step has started, cancel the remaining tasks with `updateTaskStatus`.
        Refused with `OFFBOARDING_NOT_FOUND` for an offboarding of another
        company.
      operationId: ignoreOffboarding
      parameters:
        - name: offboardingId
          required: true
          in: path
          schema:
            type: string
      responses:
        default:
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetOffboarding_Output'
components:
  schemas:
    GetOffboarding_Output:
      type: object
      properties:
        id:
          type: string
        employeeId:
          type: string
        ticketId:
          description: The offboarding ticket, whose tasks are its steps (`getTicket`)
          anyOf:
            - type: string
            - type: 'null'
        ticketReference:
          description: The reference the cockpit shows for that ticket
          anyOf:
            - type: string
            - type: 'null'
        isLegacy:
          description: >-
            Whether the offboarding runs on the steppers from before offboarding
            tickets
          type: boolean
        stepModel:
          description: >-
            How the offboarding holds its steps: ACTIONS (the steppers from
            before offboarding tickets) or INTENTS (typed tasks under its
            ticket, run through the intent tools such as
            `executeOffboardingConfirmationIntent`). Null while it has neither a
            ticket nor a step.
          anyOf:
            - type: string
              enum:
                - ACTIONS
                - INTENTS
            - type: 'null'
        status:
          type: string
          enum:
            - PENDING
            - SCHEDULED
            - IN_PROGRESS
            - CLOSED
            - CANCELED
        source:
          type: string
          enum:
            - COCKPIT
            - MERGE
            - KOMBO
            - API
        terminationDate:
          type: string
          format: date-time
          pattern: >-
            ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$
        createdAt:
          type: string
          format: date-time
          pattern: >-
            ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z))$
      required:
        - id
        - employeeId
        - isLegacy
        - status
        - source
        - terminationDate
        - createdAt
      additionalProperties: false
  securitySchemes:
    apikey:
      scheme: bearer
      bearerFormat: API key
      type: http
      description: >-
        Use your Primo API key in the Authorization header as `Bearer
        <API_KEY>`.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.