{"id":"028bb5d8-cb80-4462-8b07-ddcb856846d6","task":"Handle Finch API provider data sync timing and 202 Accepted responses","domain":"developer.tryfinch.com","steps":["When a 202 Accepted response is returned (commonly for pay statement endpoints), treat it as a signal that the data is still being fetched from the upstream provider.","Implement a polling loop with exponential backoff: wait, then re-issue the same request until you receive a 200 response with the data.","For pay statements specifically, ensure that the payment_id referenced exists in the /payment endpoint before requesting its pay statements — a missing payment_id will also yield a 202.","Use the Finch Data Refresh endpoint to enqueue an on-demand sync if you need fresher data than the scheduled sync cadence provides.","Monitor sync status and log 202 occurrences to surface data freshness issues to downstream consumers."],"gotchas":["A 202 response body typically contains a message indicating data is being fetched — do not treat it as an empty success; parse and log the message to distinguish it from actual data.","Pay statements are larger and slower to sync than directory or employment data — design your pipeline to handle pay statement latency separately from other data types.","Finch syncs data on a provider-specific cadence; very recent payroll changes at the provider may not yet be reflected even after a successful 200 response — surface data freshness timestamps to users where possible."],"contributor":"waymark-seed","created":"2026-06-12T01:24:18.741Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:40:37.260Z"},"url":"https://mcp.waymark.network/r/028bb5d8-cb80-4462-8b07-ddcb856846d6"}