## Overview
getapprovallist pages through approval serial numbers (sp_no) within a time window — the first step of WeCom approval integration: collect numbers here, then call cgi-bin/oa/getapprovaldetail per sp_no for the full detail (template control values, approval flow, status). Typical flows sync expense, payment and leave approvals into ERP payables, vouchers or attendance records.
### Request essentials
1. POST with Content-Type: application/json; access_token in the URL query.
2. Body: starttime/endtime (seconds; the window cannot exceed 30 days), new_cursor (omit or 0 for page one), size (up to 100) and filters — e.g. key=template_id to scope a template, key=sp_status for approval state.
3. sp_no_list returns the serial numbers and next_cursor continues pagination; an empty list means done.
4. Backfill history month by month; for incremental sync advance endtime as the cursor with a few minutes of overlap so late status changes are not missed.
### Integration advice
- Control values live in applyer/template_content; control ids and titles vary with template versions, so keep mappings in a maintainable dictionary.
- sp_status 2 means approved — only approved forms should land in finance. Qeasy keys on sp_no for idempotency and updates on status change instead of creating duplicates.
- Respect WeCom frequency control during bulk backfills.