# Search for offboarding information

This interface supports searching for offboarding information in fields such as employee ID, resignation approval start time, and resignation date, which can obtain information including resignation date, reason for resignation, resignation status, and process approval status.
**Notice**：Note: This interface will return data according to the permission range of "Employee Data" owned by the application. Please make sure you have applied for "Employee Resources" in "Developer Backend - Permission Management - Data Permissions - Feishu CoreHR (Enterprise Edition) Data Permissions" Scope of authority.

## Request

Facts | &nbsp;
---|---
HTTP URL | https://open.feishu.cn/open-apis/corehr/v1/offboardings/search
HTTP Method | POST
Rate Limit | [100 per minute](https://open.feishu.cn/document/ukTMukTMukTM/uUzN04SN3QjL1cDN)
Supported app types | Custom App、Store App
Required scopes<br>**To use this API, you must have at least 1 of the listed scopes.**<br>Enable any scope from the list | Get offboarding information(corehr:offboarding:read)<br>Update employee's offboarding information(corehr:offboarding:write)
Required field scopes | **Notice**：The response body of the API contains the following sensitive fields, and they will be returned only after corresponding scopes are added. If you do not need the fields, it is not recommended that you request the scopes.<br>Get employee's offboarding reason(corehr:employment.offboarding_reason:read)<br>Get custom field in offboarding information(corehr:offboarding.custom_field:read)<br>Read post-termination blocklist(corehr:offboarding.block_list:read)<br>Read and write post-termination blocklist(corehr:offboarding.block_list:write)<br>Obtain user ID(contact:user.employee_id:readonly)<br>Get last attendance day in resignation request(corehr:offboarding.last_attendance_date:read)<br>Get non-competition clauses in resignation request(corehr:offboarding.noncompete_agreement:read)<br>Read post-termination account retention field(corehr:offboarding.retain_account:read)<br>Read and write post-termination account retention field(corehr:offboarding.retain_account:write)<br>Get e-signature fields in resignation request(corehr:offboarding.signature:read)<br>Get social insurance information in resignation request(corehr:offboarding.social_insurance:read)

### Request header

Parameter | Type | Required | Description
---|---|---|---
Authorization | string | Yes | `tenant_access_token`<br>**Value format**: "Bearer `access_token`"<br>**Example value**: "Bearer t-7f1bcd13fc57d46bac21793a18e560"<br>[How to choose and get access token](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/trouble-shooting/how-to-choose-which-type-of-token-to-use)
Content-Type | string | Yes | **Fixed value**: "application/json; charset=utf-8"

### Query parameters

Parameter | Type | Required | Description
---|---|---|---
page_size | int | Yes | Page size, up to 100<br>**Example value**: 100<br>**Data validation rules**:<br>- Value range: `1` ～ `100`
page_token | string | No | Page identifier. It is not filled in the first request, indicating traversal from the beginning; when there will be more groups, the new page_token will be returned at the same time, and the next traversal can use the page_token to get more groups<br>**Example value**: 6891251722631890445
user_id_type | string | No | User ID categories<br>**Example value**: open_id<br>**Optional values are**:<br>- open_id：Identifies a user to an app. The same user has different Open IDs in different apps. [How to get Open ID](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/trouble-shooting/how-to-obtain-openid)<br>- union_id：Identifies a user to a tenant that acts as a developer. A user has the same Union ID in apps developed by the same developer, and has different Union IDs in apps developed by different developers. A developer can use Union ID to link the same user's identities in multiple apps.[How to get Union ID](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/trouble-shooting/how-to-obtain-union-id)<br>- user_id：Identifies a user to a tenant. The same user has different User IDs in different tenants. In one single tenant, a user has the same User ID in all apps （including store apps）. User ID is usually used to communicate user data between different apps. [How to get User ID](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/trouble-shooting/how-to-obtain-user-id)<br><md-enum-item key="people_corehr_id" ><br>**Default value**: `open_id`<br>**When the value is `user_id`, the following field scopes are required**:<br>Obtain user ID(contact:user.employee_id:readonly)

### Request body

Parameter | Type | Required | Description
---|---|---|---
employment_ids | string\[\] | No | Employment ID list.The ID type is consistent with the value of the query parameter user_id_type:<br>1. When the value of user_id_type is open_id, please refer to [How to obtain your own Open ID](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/trouble-shooting/how-to-obtain-openid) for the ID acquisition method.<br>2. When the value of user_id_type is user_id, please refer to [How to obtain your own User ID](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/trouble-shooting/how-to-obtain-user-id) for the ID acquisition method.<br>3. When the value of user_id_type is union_id, please refer to [How to obtain your own Union ID](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/trouble-shooting/how-to-obtain-union-id) for the ID acquisition method.<br>4. When the value of user_id_type is people_corehr_id, first refer to [How to obtain your own User ID](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/trouble-shooting/how-to-obtain-user-id) to obtain the User ID. Then obtain the employment ID through [ID conversion](https://open.feishu.cn/document/uAjLw4CM/ukTMukTMukTM/reference/corehr-v1/common_data-id/convert).<br>**Example value**: ["7140964208476371111"]
apply_initiating_time_start | string | No | Offboarding approval initiation time(the start of the search range).This field is optional and need to be used together with the end of the search range. please pass in the second-level timestamp format<br>**Example value**: "1672578336"
apply_initiating_time_end | string | No | Offboarding approval initiation time(the end of the search range).This field is optional and need to be used together with the start of the search range. Please pass in in the second-level timestamp format<br>**Example value**: "1674133537"
apply_finished_time_start | string | No | Exit approval end time (start range of search), please pass in the second-level timestamp format. This field is not required and needs to be used in conjunction with exit approval end time (end range of search).<br>**Example value**: "1641007353"
apply_finished_time_end | string | No | Exit approval end time (end range of search), please pass in the second-level timestamp format. This field is not required and needs to be used with exit approval end time (start range of search).<br>**Example value**: "1641007353"
expected_offboarding_date_start | string | No | Expected offboarding date(the start of the search range).This field is optional and need to be used together with the end of the search range.please enter in date format.<br>**Example value**: "2022-01-01"
expected_offboarding_date_end | string | No | Expected offboarding date(the end of the search range).This field is optional and need to be used together with the start of the search range.please enter in date format.<br>**Example value**: "2022-01-01"
offboarding_date_start | string | No | Offboarding date(the start of the search range).This field is optional and need to be used together with the end of the search range.please enter in date format.<br>**Example value**: "2022-01-01"
offboarding_date_end | string | No | Offboarding date(the start of the search range).This field is optional and need to be used together with the start of the search range.please enter in date format.<br>**Example value**: "2022-01-01"
statuses | string\[\] | No | Separation status, an "or" relationship between multiple states.It will searching offboarding information in all status when the value is empty.<br>**Example value**: ["Approving"]<br>**Optional values are**:<br>- Approving：Approving approval<br>- Approved：Approved<br>- Offboarded：Offboarded<br>- Rejected：Rejected Rejected<br>- Withdrawn：Withdrawn<br>- NoNeedApproval：NoNeedApproval is not required<br>**Data validation rules**:<br>- Maximum length: `10`
reasons | string\[\] | No | The reason for leaving list can be obtained through the [[Query employee reason for leaving list]] (/ssl: ttdoc/uAjLw4CM/ukTMukTMukTM/reference/corehr-v1/offboarding/query) interface, and the departure information related to the lower-level reasons is not returned when querying.It will searching offboarding information in all reason when the value is empty.<br>** Field permission requirements: ** <br>Search by reason for offboarding(corehr:employment.offboarding_reason.search:read)<br>**Example value**: ["Voluntary"]
employee_reasons | string\[\] | No | The reason for leaving (employee) list can be obtained through the [[Query the employee reason for leaving list]] (/ssl: ttdoc/uAjLw4CM/ukTMukTMukTM/reference/corehr-v1/offboarding/query) interface, and the departure information related to the subordinate reason is not returned when querying.It will searching offboarding information in all reason when the value is empty.<br>** Field permission requirements: **<br>Search by reason for offboarding(corehr:employment.offboarding_reason.search:read)<br>**Example value**: ["Voluntary"]

### Request body example
```json
{
    "employment_ids": [
        "7140964208476371111"
    ],
    "apply_initiating_time_start": "1672578336",
    "apply_initiating_time_end": "1674133537",
    "apply_finished_time_start": "1641007353",
    "apply_finished_time_end": "1641007353",
    "expected_offboarding_date_start": "2022-01-01",
    "expected_offboarding_date_end": "2022-01-01",
    "offboarding_date_start": "2022-01-01",
    "offboarding_date_end": "2022-01-01",
    "statuses": [
        "Approving"
    ],
    "reasons": [
        "Voluntary"
    ],
    "employee_reasons": [
        "Voluntary"
    ]
}
```

## Response

### Response body

Parameter | Type | Description
---|---|---
code | int | Error codes, fail if not zero
msg | string | Error descriptions
data | \- | \-
items | offboarding\[\] | The offboarding information of employees
initiating_type | string | Type of offboarding, options including: <br>-offboarding_initiated_by_self : employee apply offboarding by self<br>-offboarding_initiated_by_others : apply offboarding application by others<br>-offboarding_directly : direct offboarding
status | string | Offboarding Status<br>**Optional values are**:<br>- Approving：Approving<br>- Approved：Approved<br>- Offboarded：Offboarded<br>- Rejected：Rejected<br>- Withdrawn：Withdrawn<br>- NoNeedApproval：NoNeedApproval
application_info | application_info | Offboarding approval information
apply_initiator_id | string | Initiator's employment ID of the offboarding. The ID type is consistent with the value of the query parameter user_id_type. When user_id_type is user_id, this field takes the employee's user_id. If user_id_type is people_corehr_id, this field takes the employee's Feishu CoreHR employment ID.
apply_initiating_time | string | Offboarding initiating time
apply_finish_time | string | Offboarding application approval time
process_id | string | Offboarding application process ID. Can be used to [query process related information](https://open.feishu.cn/document/uAjLw4CM/ukTMukTMukTM/corehr-v2/process/list), for example: as the process_id of [get individual process details](https://open.feishu.cn/document/uAjLw4CM/ukTMukTMukTM/corehr-v2/process/list) to query the process details.
offboarding_info | offboarding_info | The offboarding information of employee
employment_id | string | Offboarding employee's employment ID.The ID type is consistent with the value of the query parameter user_id_type:<br>1. When the value of user_id_type is open_id, please refer to [How to obtain your own Open ID](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/trouble-shooting/how-to-obtain-openid) for the ID acquisition method.<br>2. When the value of user_id_type is user_id, please refer to [How to obtain your own User ID](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/trouble-shooting/how-to-obtain-user-id) for the ID acquisition method.<br>3. When the value of user_id_type is union_id, please refer to [How to obtain your own Union ID](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/trouble-shooting/how-to-obtain-union-id) for the ID acquisition method.<br>4. When the value of user_id_type is people_corehr_id, first refer to [How to obtain your own User ID](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/trouble-shooting/how-to-obtain-user-id) to obtain the User ID. Then obtain the employment ID through [ID conversion](https://open.feishu.cn/document/uAjLw4CM/ukTMukTMukTM/reference/corehr-v1/common_data-id/convert).
hrbp_id | string\[\] | Employee hrbp ID list.The ID type is consistent with the value of the query parameter user_id_type:<br>1. When the value of user_id_type is open_id, please refer to [How to obtain your own Open ID](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/trouble-shooting/how-to-obtain-openid) for the ID acquisition method.<br>2. When the value of user_id_type is user_id, please refer to [How to obtain your own User ID](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/trouble-shooting/how-to-obtain-user-id) for the ID acquisition method.<br>3. When the value of user_id_type is union_id, please refer to [How to obtain your own Union ID](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/trouble-shooting/how-to-obtain-union-id) for the ID acquisition method.<br>4. When the value of user_id_type is people_corehr_id, first refer to [How to obtain your own User ID](https://open.feishu.cn/document/uAjLw4CM/ugTN1YjL4UTN24CO1UjN/trouble-shooting/how-to-obtain-user-id) to obtain the User ID. Then obtain the employment ID through [ID conversion](https://open.feishu.cn/document/uAjLw4CM/ukTMukTMukTM/reference/corehr-v1/common_data-id/convert).
expected_offboarding_date | string | Expected offboarding date
offboarding_date | string | Offboarding date
reason | enum | Offboarding reason<br>**Required field scopes**:<br>Get employee's offboarding reason(corehr:employment.offboarding_reason:read)
enum_name | string | enumeration value
display | i18n\[\] | enumerated multilingual display
lang | string | language
value | string | content
reason_explanation | string | Offboarding reason explanation<br>**Required field scopes**:<br>Get employee's offboarding reason(corehr:employment.offboarding_reason:read)
employee_reason | enum | Employee reason explanation<br>**Required field scopes**:<br>Get employee's offboarding reason(corehr:employment.offboarding_reason:read)
enum_name | string | enumeration value
display | i18n\[\] | enumerated multilingual display
lang | string | language
value | string | content
employee_reason_explanation | string | Detailed reasons for offboarding (employees)<br>**Required field scopes**:<br>Get employee's offboarding reason(corehr:employment.offboarding_reason:read)
add_block_list | string | Whether to join the offboarding block list. Note: This field is of character type. Optional values are:<br>-true: yes<br>-false: no<br>**Required field scopes (Satisfy any)**:<br>Read post-termination blocklist(corehr:offboarding.block_list:read)<br>Read and write post-termination blocklist(corehr:offboarding.block_list:write)
block_reason | enum | The reason of block list, the enumeration value can be queried<br>[[Get field details]](https://open.feishu.cn/document/uAjLw4CM/ukTMukTMukTM/reference/corehr-v1/custom_field/get_by_param) interface to obtain, check according to the following parameters:<br>object_api_name= "offboarding_info"<br>custom_api_name= "block_reason"<br>**Required field scopes (Satisfy any)**:<br>Read post-termination blocklist(corehr:offboarding.block_list:read)<br>Read and write post-termination blocklist(corehr:offboarding.block_list:write)
enum_name | string | enum uniquely identifies
display | i18n\[\] | Enumerate multilingual display
lang | string | Language
value | string | Content
block_reason_explanation | string | The block reason explanation<br>**Required field scopes (Satisfy any)**:<br>Read post-termination blocklist(corehr:offboarding.block_list:read)<br>Read and write post-termination blocklist(corehr:offboarding.block_list:write)
custom_fields | custom_field_data\[\] | custom field<br>**Required field scopes**:<br>Get custom field in offboarding information(corehr:offboarding.custom_field:read)
custom_api_name | string | Unique identification of custom fields
name | custom_name | custom field name
zh_cn | string | Chinese
en_us | string | English
type | int | Custom field types. Optional values are:<br>-1: Text types, including hyperlinke fields<br>-2: Boolean type<br>-3: Number type<br>-4: Enumeration types<br>-5: Lookup type, such as leavers, competing companies, etc<br>-8: Time tpye<br>-9: Attachment type<br>Note: Unsupported field types are not specified.
value | string | Field value, which is the string escaped by json, according to the metadata definition, the field format is different (such as 123, 123.23, "true", ["id1", "id2"], "2006-01-02 15:04:05")
retain_account | boolean | Whether to keep the Feishu account after leaving the job<br>**Required field scopes (Satisfy any)**:<br>Read post-termination account retention field(corehr:offboarding.retain_account:read)<br>Read and write post-termination account retention field(corehr:offboarding.retain_account:write)
social_insurance_end_date | string | Year and month of social security suspension, return in the date format of YYYY-MM<br>**Required field scopes**:<br>Get social insurance information in resignation request(corehr:offboarding.social_insurance:read)
provident_fund_end_date | string | The expiration date of the provident fund is returned in the date format of YYYY-MM<br>**Required field scopes**:<br>Get social insurance information in resignation request(corehr:offboarding.social_insurance:read)
enforce_noncompete_agreement | boolean | Whether to enforce the non-compete agreement<br>**Required field scopes**:<br>Get non-competition clauses in resignation request(corehr:offboarding.noncompete_agreement:read)
noncompete_agreement_id | string | Non-compete contract ID, you can get detailed contract information through [query single contract](https://open.feishu.cn/document/uAjLw4CM/ukTMukTMukTM/reference/corehr-v1/contract/get)<br>**Required field scopes**:<br>Get non-competition clauses in resignation request(corehr:offboarding.noncompete_agreement:read)
noncompete_agreement_company | string | Competing company ID, you can get detailed company information through [query a single company](https://open.feishu.cn/document/uAjLw4CM/ukTMukTMukTM/reference/corehr-v1/company/get)<br>**Required field scopes**:<br>Get non-competition clauses in resignation request(corehr:offboarding.noncompete_agreement:read)
noncompete_agreement_start_date | string | non-compete start date<br>**Required field scopes**:<br>Get non-competition clauses in resignation request(corehr:offboarding.noncompete_agreement:read)
noncompete_agreement_end_date | string | non-compete end date<br>**Required field scopes**:<br>Get non-competition clauses in resignation request(corehr:offboarding.noncompete_agreement:read)
sign_type | enum | Signature method, enumeration values can be queried<br>[Get field details](https://open.feishu.cn/document/uAjLw4CM/ukTMukTMukTM/reference/corehr-v1/custom_field/get_by_param) interface to get, check according to the following parameters<br>Just ask:<br>object_api_name = "offboarding_info"<br>custom_api_name = "sign_type"<br>**Required field scopes**:<br>Get e-signature fields in resignation request(corehr:offboarding.signature:read)
enum_name | string | enumeration value
display | i18n\[\] | enumerated multilingual display
lang | string | language
value | string | content
signature_file | string | Signing document ID list<br>**Required field scopes**:<br>Get e-signature fields in resignation request(corehr:offboarding.signature:read)
last_attendance_date | string | Last day of attendance<br>**Required field scopes**:<br>Get last attendance day in resignation request(corehr:offboarding.last_attendance_date:read)
is_transfer_with_workforce | boolean | Whether to transfer with knitting
offboarding_checklist | offboarding_checklist | Offboarding checklist process information
checklist_status | string | Offboarding checklist status, optional values are: <br>- AntiBegin: Not initiated<br>- Approving: In Progress <br>- Finished: Finished <br>- Rejected: Rejected <br>- Withdrawn: Withdrawn
checklist_start_time | string | Checklist start time
checklist_finish_time | string | Checklist finished time
checklist_process_id | string | Offboarding checklist process id.Can be used to [query process related information](https://open.feishu.cn/document/uAjLw4CM/ukTMukTMukTM/corehr-v2/process/list), for example: as the process_id of [get individual process details](https://open.feishu.cn/document/uAjLw4CM/ukTMukTMukTM/corehr-v2/process/list) to query the process details.
offboarding_id | string | Offboarding uniquely identifies
page_token | string | Page identifier, when has_more is true, a new page_token will also be returned. Otherwise, page_token will not be returned
has_more | boolean | Whether the response body has more parameters

### Response body example
```json
{
  "code": 0,
  "data": {
    "has_more": false,
    "items": [
      {
        "application_info": {
          "apply_finish_time": "2022-02-03 11:22:33",
          "apply_initiating_time": "2022-02-03 11:22:33",
          "apply_initiator_id": "6838119494196871234",
          "process_id": "6838119494196871234"
        },
        "initiating_type": "offboarding_directly",
        "offboarding_checklist": {
          "checklist_finish_time": "2022-02-03 11:22:33",
          "checklist_process_id": "6838119494196871234",
          "checklist_start_time": "2022-02-03 11:22:33",
          "checklist_status": "AntiBegin"
        },
        "offboarding_id": "7298499290417251879",
        "offboarding_info": {
          "add_block_list": "false",
          "block_reason": {
            "display": [
              {
                "lang": "zh-CN",
                "value": "刘梓新"
              },
              {
                "lang": "zh-CN",
                "value": "刘梓新"
              }
            ],
            "enum_name": "phone_type"
          },
          "block_reason_explanation": "xx 年 xx 月 xx 日因 xx 原因红线",
          "custom_fields": [
            {
              "custom_api_name": "name",
              "name": {
                "en_us": "Custom Name",
                "zh_cn": "自定义姓名"
              },
              "type": 1,
              "value": "\"231\""
            },
            {
              "custom_api_name": "name",
              "name": {
                "en_us": "Custom Name",
                "zh_cn": "自定义姓名"
              },
              "type": 1,
              "value": "\"231\""
            }
          ],
          "employee_reason": {
            "display": [
              {
                "lang": "zh-CN",
                "value": "刘梓新"
              },
              {
                "lang": "zh-CN",
                "value": "刘梓新"
              }
            ],
            "enum_name": "phone_type"
          },
          "employee_reason_explanation": "升学",
          "employment_id": "6893014062142064135",
          "enforce_noncompete_agreement": false,
          "expected_offboarding_date": "2022-02-08",
          "hrbp_id": [
            "6893014062142064135",
            "6893014062142064135"
          ],
          "is_transfer_with_workforce": false,
          "last_attendance_date": "2022-02-08",
          "noncompete_agreement_company": "123",
          "noncompete_agreement_end_date": "2022-02-08",
          "noncompete_agreement_id": "123",
          "noncompete_agreement_start_date": "2022-02-08",
          "offboarding_date": "2022-02-08",
          "provident_fund_end_date": "2022-02",
          "reason": {
            "display": [
              {
                "lang": "zh-CN",
                "value": "刘梓新"
              },
              {
                "lang": "zh-CN",
                "value": "刘梓新"
              }
            ],
            "enum_name": "phone_type"
          },
          "reason_explanation": "升学",
          "retain_account": false,
          "sign_type": {
            "display": [
              {
                "lang": "zh-CN",
                "value": "刘梓新"
              },
              {
                "lang": "zh-CN",
                "value": "刘梓新"
              }
            ],
            "enum_name": "phone_type"
          },
          "signature_file": "[\"123\",\"456\"]",
          "social_insurance_end_date": "2022-02"
        },
        "status": "Approving"
      },
      {
        "application_info": {
          "apply_finish_time": "2022-02-03 11:22:33",
          "apply_initiating_time": "2022-02-03 11:22:33",
          "apply_initiator_id": "6838119494196871234",
          "process_id": "6838119494196871234"
        },
        "initiating_type": "offboarding_directly",
        "offboarding_checklist": {
          "checklist_finish_time": "2022-02-03 11:22:33",
          "checklist_process_id": "6838119494196871234",
          "checklist_start_time": "2022-02-03 11:22:33",
          "checklist_status": "AntiBegin"
        },
        "offboarding_id": "7298499290417251879",
        "offboarding_info": {
          "add_block_list": "false",
          "block_reason": {
            "display": [
              {
                "lang": "zh-CN",
                "value": "刘梓新"
              },
              {
                "lang": "zh-CN",
                "value": "刘梓新"
              }
            ],
            "enum_name": "phone_type"
          },
          "block_reason_explanation": "xx 年 xx 月 xx 日因 xx 原因红线",
          "custom_fields": [
            {
              "custom_api_name": "name",
              "name": {
                "en_us": "Custom Name",
                "zh_cn": "自定义姓名"
              },
              "type": 1,
              "value": "\"231\""
            },
            {
              "custom_api_name": "name",
              "name": {
                "en_us": "Custom Name",
                "zh_cn": "自定义姓名"
              },
              "type": 1,
              "value": "\"231\""
            }
          ],
          "employee_reason": {
            "display": [
              {
                "lang": "zh-CN",
                "value": "刘梓新"
              },
              {
                "lang": "zh-CN",
                "value": "刘梓新"
              }
            ],
            "enum_name": "phone_type"
          },
          "employee_reason_explanation": "升学",
          "employment_id": "6893014062142064135",
          "enforce_noncompete_agreement": false,
          "expected_offboarding_date": "2022-02-08",
          "hrbp_id": [
            "6893014062142064135",
            "6893014062142064135"
          ],
          "is_transfer_with_workforce": false,
          "last_attendance_date": "2022-02-08",
          "noncompete_agreement_company": "123",
          "noncompete_agreement_end_date": "2022-02-08",
          "noncompete_agreement_id": "123",
          "noncompete_agreement_start_date": "2022-02-08",
          "offboarding_date": "2022-02-08",
          "provident_fund_end_date": "2022-02",
          "reason": {
            "display": [
              {
                "lang": "zh-CN",
                "value": "刘梓新"
              },
              {
                "lang": "zh-CN",
                "value": "刘梓新"
              }
            ],
            "enum_name": "phone_type"
          },
          "reason_explanation": "升学",
          "retain_account": false,
          "sign_type": {
            "display": [
              {
                "lang": "zh-CN",
                "value": "刘梓新"
              },
              {
                "lang": "zh-CN",
                "value": "刘梓新"
              }
            ],
            "enum_name": "phone_type"
          },
          "signature_file": "[\"123\",\"456\"]",
          "social_insurance_end_date": "2022-02"
        },
        "status": "Approving"
      }
    ],
    "page_token": ""
  },
  "msg": "success"
}
```

### Error code

HTTP status code | Error code | Description | Troubleshooting suggestions
---|---|---|---
400 | 1160102 | Param is invalid | Please check the paging size, paging mark and timestamp format of offboarding approval start time and try again
400 | 1160103 | No permission on param | You do not have permission to use the reason for offboarding or reason for offboarding (employee) to filter. Please confirm that the application application is searched according to the reason for offboarding (corehr:employment.offboarding_reason.search:read) and try again.
400 | 1160104 | Missing query parameter | Please ensure that the end and start time of the offboarding approval start time, expected offboarding date and offboarding date are all passed in to the post request
400 | 1160999 | general internal server error code | There is a problem with the system. If you need help, please contact [Technical Support](https://applink.feishu.cn/TLJpeNdW).

