# Punch flow
**Notice**：To understand the usage scenarios and configuration process of event subscription, please refer to [overview of event subscription](https://open.feishu.cn/document/ukTMukTMukTM/uUTNz4SN1MjL1UzM).

**Event**

The notifications of the user's attendance record information will be sent after recording attendance successfully.

**Event type**

`attendance.user_flow.created_v1`

**Event body**
|Name|Type|Description|
|---|---|---|
|schema|string|Event mode|
|header|event_header|Event header|
|&emsp;∟event_id|string|Event ID|
|&emsp;∟event_type|string|Event type|
|&emsp;∟create_time|string|Event creation timestamp (unit: millisecond)|
|&emsp;∟token|string|Event Token|
|&emsp;∟app_id|string|App ID|
|&emsp;∟tenant_key|string|Tenant Key|
|event|-|Event body|
|&emsp;∟employee_id|string|[Feishu Admin Backend](https://example.feishu.cn/admin/contacts/departmentanduser) > Organizational Structure > Members and Departments > User ID in member details|
|&emsp;∟employee_no|string|[Feishu Admin Backend](https://example.feishu.cn/admin/contacts/departmentanduser) > Organizational structure > Members and departments > Employee ID in member details|
|&emsp;∟location_name|string|Attendance location name information|
|&emsp;∟check_time|string|Attendance time, timestamp accurate to the second|
|&emsp;∟comment|string|Attendance remark|
|&emsp;∟record_id|string|Attendance record ID|
|&emsp;∟longitude|float|Attendance longitude. **Notice**: Returning longitude and latitude is not currently supported|
|&emsp;∟latitude|float|Attendance latitude. **Notice**: Returning longitude and latitude is not currently supported|
|&emsp;∟ssid|string|Attendance Wi-Fi SSID|
|&emsp;∟bssid|string|Attendance Wi-Fi MAC address|
|&emsp;∟is_field|boolean|Whether it's offsite attendance|
|&emsp;∟is_wifi|boolean|Whether it's Wi-Fi attendance|
|&emsp;∟type|int|Record generating method, available value: [0(user record attendance), 1(administrator modification), 2(user correction), 3(system automatic generation), 4(no off-duty attendance), 5(record attendance by machine), 6(express attendance), 7(attendance open platform import)]|
|&emsp;∟photo_urls|string\[\]|Attendance photo list|
|&emsp;∟risk_result|int|Suspicious cheating clock-in behavior, 0: No suspicion of cheating, 1: Suspected use of cheating software, 2: Suspected use of someone else's device for clock-in, 3: Suspected multiple people using the same device for clock-in.|
**Callback example**
```
{
  "schema": "2.0",
  "header": {
    "event_id": "41fae5c12837ead344eced982fbde395",
    "token": "wz5vVgAqJ0cghdfdjdVuxeyTt8hvYHBg",
    "create_time": "1615381917707",
    "event_type": "attendance.user_flow.created_v1",
    "tenant_key": "2fce678eb60d1651",
    "app_id": "cli_a0c203e66cf8100c"
  },
  "event": {
    "bssid": "b0:b8:67:62:18:73",
    "check_time": "1615381916",
    "comment": "",
    "employee_id": "2b68933a",
    "employee_no": "",
    "is_field": false,
    "is_wifi": false,
    "latitude": 30.29245030908851,
    "location_name": "Xixibafangcheng, Wuchang Street, Yuhang District, Hangzhou City, Zhejiang Province, China",
    "longitude": 120.04004357074373,
    "photo_urls": [],
    "record_id": "6938012269578125316",
    "ssid": "ByteDance Inc",
    "type": 0,
    "risk_result": 0
  }
}
```