Not Found (404)

The resource does not exist for your key. Resources that exist but belong to another partner answer exactly the same — the API never confirms other tenants' data.

Common causes

• An id from a different environment (sandbox ids never exist in production).
• A webhook endpoint that was deleted: testing or deleting it answers 404 at once, and ids are not reused. Its delivery history stays readable with GET /v1/webhook_endpoints/{id}/deliveries.
• church_id that your key never imported.
• POST /v1/churches/{id}/bank-account or POST /v1/churches/{id}/verification for a church that another platform registered first (your import answered linked: existing_church). Its account and legal details stay with that platform, even though the church appears in GET /v1/churches.

What to do: list the parent collection (GET /v1/churches, GET /v1/webhook_endpoints) and use ids from the response.

An id over 100 characters, or one the API cannot decode, also gets this 404. A path with a malformed percent sign, such as %zz, never reaches the API: the gateway in front of it answers 400 with an HTML body (see API errors).