MyWalmart 员工数据 API:打卡、排班与库存
MyWalmart 是 Walmart 门店团队用于查看打卡状态、每周排班、班次转让、每日名册与货架库存的员工应用。这些界面对接两个 GraphQL 网关:劳动力网关 /v1/graphql/associate(已登录用户、打卡、班次、名册、通道状态、工单)与资料网关 /v1/graphql/profile(WIN、入职日期、紧急联系人、税务地址)。货架库存是 /v1/inventory 下独立的 REST 面,提供部门库存、增量、商品详情与例外清单调用。登录请求发送 Bearer 令牌加 x-country-code、x-user-id、x-store-id 与 x-client-id 身份请求头。
MyWalmart 是 Walmart 面向美国门店团队的员工应用:打卡状态、每周排班、班次转让、每日名册、统一资料(WIN、入职日期、职位名称)与紧急联系人,以及映射 UPC 到通道与货位的货架扫描库存。背后是 GraphQL 网关 /v1/graphql/associate(劳动力)与 /v1/graphql/profile(资料),以及 /v1/inventory 的 REST 库存面。登录调用携带 Bearer 令牌与国家/用户/门店请求头;货架库存调用另加 feature-key 扫描请求头。
应用截图
API 端点一览
已登录员工(当前会话)
POST
/v1/graphql/associateosint返回为首页提供数据的已登录员工信息包:WIN、偏好姓名、部门、职位类别、在职状态与当前打卡状态。
认证方式: Bearer 员工令牌(Authorization: Bearer),另加身份请求头 x-country-code、x-user-id、x-store-id 与 x-client-id。
- associateId
- displayName
- employmentStatus
- department
- jobCategoryCode
- jobCategoryCodeDesc
- preferredFirstName
- preferredLastName
- walmartIdentificationNumber
- clockStatus
- facilityDivNumber
- facilityRegionNumber
依据应用界面重构的示意示例,并非实时抓包。
POST /v1/graphql/associate HTTP/1.1 Authorization: Bearer <access-token> x-country-code: US x-user-id: u-18492031 x-store-id: 100 x-client-id: <client-id> Content-Type: application/json { "operationName": "getCurrentAssociate", "query": "query getCurrentAssociate { currentAssociate { associate { associateId displayName employmentStatus department jobCategoryCode jobCategoryCodeDesc preferredFirstName preferredLastName walmartIdentificationNumber clockStatus { status } } } }", "variables": {} }{ "data": { "currentAssociate": { "associate": { "associateId": "10001234", "displayName": "Jordan Lee", "employmentStatus": "A", "department": "82", "jobCategoryCode": "1", "jobCategoryCodeDesc": "Sales Associate", "preferredFirstName": "Jordan", "preferredLastName": "Lee", "walmartIdentificationNumber": "10001234", "clockStatus": { "status": "IN" }, "facilityDivNumber": "1", "facilityRegionNumber": "6" } } } }依据应用界面推导;端点细节为示意说明,并非实际抓包。
镜像登录后首页渲染的员工卡片同一组身份请求头随应用内每次劳动力调用发送
按用户 ID 查询员工资料
POST
/v1/graphql/profileosint按用户 ID 查询统一员工资料——WIN、入职日期、职位名称与偏好全名——供资料页与团队卡片页使用。
认证方式: Bearer 员工令牌,携带相同的国家/用户/门店身份请求头。
- associateProfile
- hireDate
- positionTitle
- preferredFormattedName
- walmartIdentificationNumber
- userId
依据应用界面重构的示意示例,并非实时抓包。
POST /v1/graphql/profile HTTP/1.1 Authorization: Bearer <access-token> x-country-code: US Content-Type: application/json { "operationName": "getAssociateProfile", "query": "query getAssociateProfile($userId: String!) { associateProfile(userId: $userId) { hireDate positionTitle preferredFormattedName walmartIdentificationNumber } }", "variables": { "userId": "u-18492031" } }{ "data": { "associateProfile": { "hireDate": "2019-04-12", "positionTitle": "Customer Service Manager", "preferredFormattedName": "Jordan Lee", "walmartIdentificationNumber": "10001234" } } }依据应用界面推导;端点细节为示意说明,并非实际抓包。
支撑资料页头部与团队卡片界面查询以登录时签发的用户 ID 为键
打卡/考勤状态
POST
/v1/graphql/associateopendata读取每日名册的门店级打卡状态:每个 WIN 是否已打卡、最近打卡类型/时间,以及缺勤或电话请假代码。
认证方式: Bearer 员工令牌,另加 x-country-code、x-user-id、x-store-id 与 x-client-id 请求头。
- associateId
- win
- punch
- clockStatus
- clockStatusDesc
- lastPunchTime
- lastPunchType
- absenceRsnCode
- absenceTypeCode
- callInMethodCode
- callInTimestamp
依据应用界面重构的示意示例,并非实时抓包。
POST /v1/graphql/associate HTTP/1.1 Authorization: Bearer <access-token> x-country-code: US x-store-id: 100 Content-Type: application/json { "operationName": "getPunchState", "query": "query getPunchState($countryCode: String!, $startDate: Date!, $storeId: String!) { rosterDay(countryCode: $countryCode, startDate: $startDate, storeId: $storeId) { associateId win punch { clockStatus clockStatusDesc lastPunchTime lastPunchType } absence(countryCode: $countryCode, date: $startDate) { absenceRsnCode absenceTypeCode callInMethodCode callInTimestamp } } }", "variables": { "countryCode": "US", "startDate": "2026-09-27", "storeId": "100" } }{ "data": { "rosterDay": [{ "associateId": "10001234", "win": "10001234", "punch": { "clockStatus": "IN", "clockStatusDesc": "Clocked in", "lastPunchTime": "2026-09-27T13:02:11Z", "lastPunchType": "IN" }, "absence": { "absenceRsnCode": null, "absenceTypeCode": null, "callInMethodCode": null, "callInTimestamp": null } }] } }依据应用界面推导;端点细节为示意说明,并非实际抓包。
驱动打卡状态徽标与每日名册条缺勤与电话请假代码与名册记录同行返回
团队排班(含实时打卡状态)
POST
/v1/graphql/associateopendata按日期范围批量获取一个或多个 WIN 的班次与实时打卡状态——排班列表与经理团队工时视图背后的数据。
认证方式: Bearer 员工令牌,另加 x-country-code、x-user-id、x-store-id 与 x-client-id 请求头。
- associateId
- firstName
- lastName
- userId
- win
- clockStatus
- status
- lastPunchType
- lastPunchTime
- scheduleShifts
- shiftId
- shiftStartTime
- shiftEndTime
依据应用界面重构的示意示例,并非实时抓包。
POST /v1/graphql/associate HTTP/1.1 Authorization: Bearer <access-token> Content-Type: application/json { "operationName": "getTeamSchedules", "query": "query getTeamSchedules($wins: [String!]!, $startDate: String!, $endDate: String!) { teamSchedules(request: { wins: $wins, startDate: $startDate, endDate: $endDate }) { associateId firstName lastName userId win clockStatus { status lastPunchType lastPunchTime clockStatusDesc errorCode } scheduleShifts { shiftId shiftStartTime shiftEndTime } } }", "variables": { "wins": ["10001234"], "startDate": "2026-09-21", "endDate": "2026-09-27" } }{ "data": { "teamSchedules": [{ "associateId": "10001234", "firstName": "Jordan", "lastName": "Lee", "userId": "u-18492031", "win": "10001234", "clockStatus": { "status": "IN", "lastPunchType": "IN", "lastPunchTime": "2026-09-27T13:02:11Z", "clockStatusDesc": "Clocked in", "errorCode": null }, "scheduleShifts": [{ "shiftId": "88412001", "shiftStartTime": "2026-09-27T13:00:00Z", "shiftEndTime": "2026-09-27T21:00:00Z" }] }] } }依据应用界面推导;端点细节为示意说明,并非实际抓包。
供给一周概览排班列表经理视图通过同一查询批量请求多个 WIN
员工门店排班
POST
/v1/graphql/associateopendata按 WIN 与门店编号返回员工的门店排班,含零售周、班次起止与带工种代码的事件,供排班日历使用。
认证方式: Bearer 员工令牌,另加 x-country-code、x-user-id、x-store-id 与 x-client-id 请求头。
- winNbr
- sourceInfo
- weeks
- scheduleWeekStartDate
- scheduleWeekEndDate
- wmWeek
- shiftId
- shiftStartTime
- shiftEndTime
- storeNumber
- jobCode
- jobDescription
依据应用界面重构的示意示例,并非实时抓包。
POST /v1/graphql/associate HTTP/1.1 Authorization: Bearer <access-token> x-store-id: 100 Content-Type: application/json { "operationName": "getStoreSchedule", "query": "query getStoreSchedule($country: String!, $storeNbr: Int!, $win: Int!, $startDate: String!, $endDate: String!) { storeSchedule(country: $country, storeNbr: $storeNbr, win: $win, startDate: $startDate, endDate: $endDate) { winNbr sourceInfo weeks { scheduleWeekStartDate scheduleWeekEndDate wmWeek schedules { shiftId shiftStartTime shiftEndTime storeNumber events { type startTime endTime jobCode jobDescription } } } } }", "variables": { "country": "US", "storeNbr": 100, "win": 10001234, "startDate": "2026-09-21", "endDate": "2026-10-04" } }{ "data": { "storeSchedule": { "winNbr": 10001234, "sourceInfo": "WFM", "weeks": [{ "scheduleWeekStartDate": "2026-09-21", "scheduleWeekEndDate": "2026-09-27", "wmWeek": "2026-38", "schedules": [{ "shiftId": "88412001", "shiftStartTime": "2026-09-27T13:00:00Z", "shiftEndTime": "2026-09-27T21:00:00Z", "storeNumber": 100, "events": [{ "type": "SHIFT", "startTime": "2026-09-27T13:00:00Z", "endTime": "2026-09-27T21:00:00Z", "jobCode": "1-SALES", "jobDescription": "Sales Associate" }] }] }] } } }依据应用界面推导;端点细节为示意说明,并非实际抓包。
驱动排班日历的周页面带工种代码的事件说明每个班次块的角色
门店每日名册
POST
/v1/graphql/associateosint列出门店每日名册上的在职员工,含偏好姓名、薪资类型、职位类别、打卡状态与分配班次——即团队点名视图。
认证方式: Bearer 员工令牌,另加 x-country-code、x-user-id、x-store-id 与 x-client-id 请求头。
- associateId
- firstName
- lastName
- fullName
- preferredFullName
- payType
- jobCategoryCodeDesc
- userId
- clockStatus
- lastPunchType
- shift
依据应用界面重构的示意示例,并非实时抓包。
POST /v1/graphql/associate HTTP/1.1 Authorization: Bearer <access-token> x-country-code: US x-store-id: 100 Content-Type: application/json { "operationName": "getStoreRoster", "query": "query getStoreRoster($storeNbr: Int!, $countryCode: String!, $days: Int!, $startDate: Date!, $storeId: String!) { storeRoster(countryCode: $countryCode, days: $days, employmentStatus: \"A\", startDate: $startDate, storeId: $storeId) { associateId firstName lastName fullName preferredFullName payType jobCategoryCodeDesc userId punch { clockStatus lastPunchType } shift { name number } } }", "variables": { "storeNbr": 100, "countryCode": "US", "days": 1, "startDate": "2026-09-27", "storeId": "100" } }{ "data": { "storeRoster": [{ "associateId": "10001234", "firstName": "Jordan", "lastName": "Lee", "fullName": "Jordan Lee", "preferredFullName": "Jordan Lee", "payType": "HOURLY", "jobCategoryCodeDesc": "Sales Associate", "userId": "u-18492031", "punch": { "clockStatus": "IN", "lastPunchType": "IN" }, "shift": { "name": "First", "number": 1 } }] } }依据应用界面推导;端点细节为示意说明,并非实际抓包。
填充日计划打开时的团队点名默认筛选为在职状态的员工
紧急联系人
POST
/v1/graphql/profileosint从统一资料读取员工的紧急联系人簿与合规授权——紧急联系人页使用的姓名、关系、电话与邮箱。
认证方式: Bearer 员工令牌。通过 id-type 参数以 WIN 或用户 ID 为键查询。
- userID
- optInEmergencyCompliance
- firstName
- lastName
- relationship
- isPrimary
- emailAddress
- emailType
- internationalPhoneCode
- phoneNumber
- phoneType
依据应用界面重构的示意示例,并非实时抓包。
POST /v1/graphql/profile HTTP/1.1 Authorization: Bearer <access-token> Content-Type: application/json { "operationName": "getEmergencyContacts", "query": "query getEmergencyContacts($idType: IdType!, $winOrId: String!) { associateById(id: $winOrId, idType: $idType) { profile { contactData { emergencyCompliance { optInEmergencyCompliance txnStatus } emergencyContacts { firstName lastName relationship isPrimary email { emailAddress emailType } phone { countryCode phoneNumber phoneType } } } userID } } }", "variables": { "idType": "WIN", "winOrId": "10001234" } }{ "data": { "associateById": { "profile": { "userID": "u-18492031", "contactData": { "emergencyCompliance": { "optInEmergencyCompliance": true, "txnStatus": "COMMITTED" }, "emergencyContacts": [{ "firstName": "Alex", "lastName": "Lee", "relationship": "SPOUSE", "isPrimary": true, "email": { "emailAddress": "[email protected]", "emailType": "HOME" }, "phone": { "countryCode": "1", "phoneNumber": "4795550100", "phoneType": "MOBILE" } }] } } } } }依据应用界面推导;端点细节为示意说明,并非实际抓包。
镜像紧急联系人页的首要联系人卡片合规授权标记随同一次资料读取返回
税务/邮寄地址
POST
/v1/graphql/profileosint从资料的联系数据返回员工的税务与邮寄地址行——街道、城市、州、邮编及邮寄/首要标记。
认证方式: Bearer 员工令牌。以 WIN 为范围的资料读取。
- associateId
- addressLine1
- addressLine2
- city
- countryName
- postalCode
- stateCode
- stateName
- isMailing
- isPermanent
- isPrimary
- formattedAddress
依据应用界面重构的示意示例,并非实时抓包。
POST /v1/graphql/profile HTTP/1.1 Authorization: Bearer <access-token> Content-Type: application/json { "operationName": "getTaxAddress", "query": "query getTaxAddress($win: String!) { associateById(id: $win) { associateId profile { contactData { addresses { addressLine1 addressLine2 city countryName postalCode stateCode stateName isMailing isPermanent isPrimary formattedAddress } } } } }", "variables": { "win": "10001234" } }{ "data": { "associateById": { "associateId": "10001234", "profile": { "contactData": { "addresses": [{ "addressLine1": "702 SW 8th St", "addressLine2": "", "city": "Bentonville", "countryName": "United States", "postalCode": "72716", "stateCode": "AR", "stateName": "Arkansas", "isMailing": true, "isPermanent": true, "isPrimary": true, "formattedAddress": "702 SW 8th St, Bentonville, AR 72716" }] } } } } }依据应用界面推导;端点细节为示意说明,并非实际抓包。
支撑资料页的地址卡片邮寄与首要标记决定页面首先展示哪一行
创建班次转让
POST
/v1/graphql/associateopendata把某 WIN 在某门店的班次发布到接班转让池,并返回已转让班次事件(工种代码、起止时间)。
认证方式: Bearer 员工令牌。以 WIN+门店为范围;经理与符合条件的员工可转让班次。
- winNbr
- shiftId
- isShiftOffered
- type
- startTime
- endTime
- jobCode
- hrdwJobCode
- jobDescription
依据应用界面重构的示意示例,并非实时抓包。
POST /v1/graphql/associate HTTP/1.1 Authorization: Bearer <access-token> Content-Type: application/json { "operationName": "offerShiftToPool", "query": "mutation offerShiftToPool($country: String!, $storeNbr: Int!, $win: Long!, $input: ShiftOfferInput) { offerShift(country: $country, storeNbr: $storeNbr, win: $win, input: $input) { winNbr shiftId isShiftOffered events { type startTime endTime jobCode hrdwJobCode jobDescription } } }", "variables": { "country": "US", "storeNbr": 100, "win": 10001234, "input": { "shiftId": "88412001" } } }{ "data": { "offerShift": { "winNbr": 10001234, "shiftId": "88412001", "isShiftOffered": true, "events": [{ "type": "SHIFT", "startTime": "2026-09-28T13:00:00Z", "endTime": "2026-09-28T21:00:00Z", "jobCode": "1-SALES", "hrdwJobCode": "1SALES", "jobDescription": "Sales Associate" }] } } }依据应用界面推导;端点细节为示意说明,并非实际抓包。
对应班次转让确认面板返回的事件镜像该班次的日历块
门店通道/分区状态
POST
/v1/graphql/associateopendata返回货架补货所用的通道/区域/分区作业状态:哪个分区处于活动状态、最近由谁处理,以及 UPC 拣货清单。
认证方式: Bearer 员工令牌。国家与门店请求头标识站点。
- aisleId
- zoneName
- sectionId
- isSectionActive
- sectionLastWorkedTs
- legacySectionId
- lastWorkedUser
- state
- pickList
依据应用界面重构的示意示例,并非实时抓包。
POST /v1/graphql/associate HTTP/1.1 Authorization: Bearer <access-token> x-country-code: US x-store-id: 100 Content-Type: application/json { "operationName": "getAisleState", "query": "query getAisleState($country: String!, $storeId: Int!, $aisles: [String]) { aisleState(country: $country, storeId: $storeId, aisles: $aisles) { aisles { aisleId zoneName sections { sectionId isSectionActive sectionLastWorkedTs legacySectionId lastWorkedUser state pickList } } } }", "variables": { "country": "US", "storeId": 100, "aisles": ["12"] } }{ "data": { "aisleState": { "aisles": [{ "aisleId": "12", "zoneName": "Grocery", "sections": [{ "sectionId": "12-A", "isSectionActive": true, "sectionLastWorkedTs": "2026-09-27T15:41:00Z", "legacySectionId": "012A", "lastWorkedUser": "10001234", "state": "IN_PROGRESS", "pickList": ["0049000051234"] }] }] } } }依据应用界面推导;端点细节为示意说明,并非实际抓包。
驱动通道地图上每个分区的状态标记拣货清单与扫描叠加层高亮的是同一组 UPC
按部门获取货架库存
GET
/v1/inventory/shelf-stockopendata下载部门级货架库存:CID、UPC、描述、图片与货架位置(通道、分区、SGLN、区域),供扫描叠加层使用。
认证方式: Bearer 令牌加身份请求头(x-country-code、x-user-id、x-store-id、x-client-id)及 x-feature-key: shelf-scan 请求头。查询 token 用于分页。
- items
- cid
- upc
- description
- image
- isItemOnFeature
- section
- aisle
- mod_location
- sgln
- zone
- barcode
- token
依据应用界面重构的示意示例,并非实时抓包。
GET /v1/inventory/shelf-stock?dept=82 HTTP/1.1 Authorization: Bearer <access-token> x-country-code: US x-user-id: u-18492031 x-store-id: 100 x-client-id: <client-id> x-feature-key: shelf-scan{ "items": [{ "cid": 5588123, "upc": "0049000051234", "description": "Great Value Whole Milk 1 gal", "image": "https://example.invalid/img/milk.jpg", "isItemOnFeature": false, "location": { "section": 12, "aisle": 12, "mod_location": "12-A-04", "sgln": "0078742000123.12.A", "zone": "Grocery", "barcode": ["0049000051234"] } }], "token": ["page-eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9"] }依据应用界面推导;端点细节为示意说明,并非实际抓包。
按部门填充扫描叠加层的商品卡片分页 token 在下一次调用中继续下载
按部门获取货架库存增量
GET
/v1/inventory/shelf-stock/deltasopendata获取某部门在两个时间戳之间的 CID/UPC 资格增量,让设备端库存缓存无需全量下载即可刷新。
认证方式: Bearer 令牌。与部门库存调用相同的货架扫描请求头;查询 token 用于续传增量分页。
- cidUpdates
- upcUpdates
- token
- cid
- upc
- shelfEligible
- deptId
- startTimestamp
- endTimestamp
依据应用界面重构的示意示例,并非实时抓包。
GET /v1/inventory/shelf-stock/deltas?dept=82&from=1758902400000&to=1758988800000 HTTP/1.1 Authorization: Bearer <access-token> x-country-code: US x-store-id: 100 x-feature-key: shelf-scan{ "cidUpdates": [{ "cid": 5588123, "shelfEligible": true }], "upcUpdates": [{ "upc": "0049000051234", "cid": 5588123 }], "token": ["page-eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9"] }依据应用界面推导;端点细节为示意说明,并非实际抓包。
在全量同步之间保持部门库存缓存新鲜时间戳界定设备请求的增量窗口
货架叠加层商品详情
GET
/v1/inventory/itemsopendata员工点击货架叠加层时水合商品卡片:UPC、CID、描述、图片及所有已知货架位置。
认证方式: Bearer 令牌。相同的货架扫描请求头;upc 查询参数是扫描或点击的叠加层条码。
- upc
- description
- image
- cid
- locations
- section
- aisle
- mod_location
- sgln
- zone
依据应用界面重构的示意示例,并非实时抓包。
GET /v1/inventory/items?upc=0049000051234 HTTP/1.1 Authorization: Bearer <access-token> x-country-code: US x-store-id: 100 x-feature-key: shelf-scan[{ "upc": "0049000051234", "description": "Great Value Whole Milk 1 gal", "image": "https://example.invalid/img/milk.jpg", "cid": 5588123, "locations": [{ "section": 12, "aisle": 12, "mod_location": "12-A-04", "sgln": "0078742000123.12.A", "zone": "Grocery" }] }]依据应用界面推导;端点细节为示意说明,并非实际抓包。
员工点击高亮的货架叠加层时打开返回该扫码的所有已知位置
货架例外/筛选 UPC
GET
/v1/inventory/exceptionsopendata下载例外 UPC 集合(清仓、删除、主推),货架扫描器用它们筛选叠加层资格。
认证方式: Bearer 令牌。相同的货架扫描请求头。查询 filters=clearance,deleted,分页 token 可选。
- itemFilter
- itemDetails
- upc
- token
- filters
- paginationToken
依据应用界面重构的示意示例,并非实时抓包。
GET /v1/inventory/exceptions?filters=clearance,deleted HTTP/1.1 Authorization: Bearer <access-token> x-country-code: US x-store-id: 100 x-feature-key: shelf-scan[{ "itemFilter": "clearance", "itemDetails": [{ "upc": "0049000059999" }], "token": "page-2" }]依据应用界面推导;端点细节为示意说明,并非实际抓包。
扫描器会隐藏这些例外清单上的条码每个筛选桶独立分页
创建设施工单
POST
/v1/graphql/associateopendata从非紧急告警或任务创建设施工单,让员工能从应用提交门店维修工单。
认证方式: Bearer 员工令牌。用户 ID 与国家代码标识操作者;position 为员工岗位角色。
- taskId
- eventId
- userId
- position
- countryCode
- status
- data
依据应用界面重构的示意示例,并非实时抓包。
POST /v1/graphql/associate HTTP/1.1 Authorization: Bearer <access-token> Content-Type: application/json { "operationName": "openWorkOrder", "query": "mutation openWorkOrder($taskId: String!, $eventId: String!, $userId: String!, $position: String!, $countryCode: String!) { openWorkOrder(input: { alarm: { taskId: $taskId, eventId: $eventId, countryCode: $countryCode }, userId: $userId, position: $position }) { status data } }", "variables": { "taskId": "WO-TASK-4412", "eventId": "evt-9981", "userId": "u-18492031", "position": "Sales Associate", "countryCode": "US" } }{ "data": { "openWorkOrder": { "status": "CREATED", "data": "884199" } } }依据应用界面推导;端点细节为示意说明,并非实际抓包。
从维修任务的操作面板提交返回的 ID 即设施队列跟踪的工单号
数据类别
- 员工资料
- Walmart 识别号(WIN)
- 工时与考勤
- 排班与班次
- 门店名册
- 紧急联系人
- 税务地址
- 门店库存位置
数据使用场景与案例
员工身份与 WIN 查询
HR 与门店运营工具可通过已登录员工查询与资料查询解析用户 ID 或 WIN,获取偏好姓名、入职日期、职位名称、部门与职位类别——与首页和资料页渲染的字段相同。
工时、考勤与班次覆盖
劳动力看板可轮询打卡状态与团队排班查询,获取打卡状态(clockStatus、lastPunchType、lastPunchTime)与班次起止;当班次需要进入接班池时,再调用班次转让 mutation。
货架位置库存同步
店内库存作业可分页拉取部门货架库存调用的 UPC 与位置(通道、分区、货位),在两次同步之间应用资格增量,并通过商品详情调用水合扫描到的商品。
紧急联系人与税务地址审计
合规工作流可从资料图谱读取紧急联系人簿(relationship、phoneNumber、emailAddress、授权标记)与税务地址行(邮寄/首要标记、postalCode、stateCode)。
常见问题
MyWalmart 在接口层面如何标识一名员工?
劳动力 GraphQL 的用户查询返回 associateId、walmartIdentificationNumber(WIN)、偏好姓名、部门与 jobCategoryCode。资料读取以用户 ID 或 WIN 为入参,返回 hireDate、positionTitle 与 preferredFormattedName。后续调用把同一身份写入 x-user-id 与 x-store-id 请求头。
哪些端点支撑打卡与每周排班?
打卡状态查询从每日名册行读取 clockStatus、lastPunchType 与 lastPunchTime。排班查询返回 shiftId、shiftStartTime、shiftEndTime 与带工种代码的事件;班次转让 mutation 把班次发布到接班池。
货架位置库存来自哪里?
REST 库存面按部门列出库存,含 UPC、描述与通道/分区/货位位置;提供两个时间戳之间的资格增量;水合扫描商品的详情卡片;并下载清仓、删除 UPC 等例外清单。
MyWalmart API 调用发送哪些认证请求头?
员工登录一次后,应用会附加 Authorization: Bearer 及 x-country-code、x-user-id、x-store-id、x-client-id。货架库存请求再加 x-feature-key 请求头,用于标识扫描功能。
相关主题
- MyWalmart API
- Walmart 员工数据 API
- WIN walmartIdentificationNumber
- 员工打卡状态
- 门店排班 API
- 货架库存位置
- 紧急联系人资料
- 班次转让 API
需要集成这个 App 的数据 API?
我们可为任意指定 App 交付定制集成——源码交付 USD 500 起,或托管 API 按调用计费。告诉我们您需要的数据即可。
- 每个项目均签 NDA 与 SOW
- 3–7 天交付
- 验收通过后才付款
- 仅在授权范围内作业