---
title: "Get Expected Payment Date"
method: GET
path: "/billpay/expected-payment-date"
tags: ["Bill Pay"]
---

# Get Expected Payment Date

`GET /billpay/expected-payment-date`

## Request

- Base URL: `https://api.meow.com/v1`
- URL: `https://api.meow.com/v1/billpay/expected-payment-date`
- Auth: API key in header `x-api-key`
- TypeScript: <https://skmtc.dev/meow/apis/meow-api/docs/billpay/expected-payment-date/get.ts> (a function with typed inputs; its response is checked against the schema)

Returns the date a payment sent on a given rail is expected to reach the vendor, based on the banking calendar and the funding account's daily cutoffs.

## Query parameters

- `payment_type` 'ACH' | 'WIRE' | 'INTERNATIONAL_PAYMENT_FX' | 'CHECK' | 'CRYPTO', required: The rails this API names, spelled the way the bills API spells them. A caller reads `payment_details.payment_type` off a bill and feeds it back here, so the FX rail has to answer to BillPaymentTypeEnum's name for it — the internal PaymentDeliveryRail calls the same rail INTERNATIONAL_PAYMENT.
- `initiated_at` string, date-time, required: When the payment would be sent.
- `instant_eligible` boolean: Whether the payment may auto-route an instant rail when it executes, which only a crypto send does and only when sent immediately. A scheduled send funds over a wire, so leave this false to get the wire-funded date.
- `account_id` string, nullable: The funding account, in the same id format returned by `GET /accounts`. Defaults to the entity's default bill pay account, or to your key's account when the key is restricted to one account.

## Headers

- `x-entity-id` string, uuid

## Response `200`

Successful Response

- ExpectedPaymentDateResponse
  - `expected_delivery_date` string, date, required: ISO 8601 full-date in the format `YYYY-MM-DD` (per [IETF RFC 3339](https://xml2rfc.tools.ietf.org/public/rfc/html/rfc3339.html#anchor14)).

## Other responses

- `400`: The request could not be processed.
- `401`: Authentication failed.
- `403`: The API key is not authorized for this operation, or the user of a global API key is an admin or controller without approved KYC. The KYC case returns the message `KYC is required for controllers and admins.` until that user completes KYC in the Meow dashboard.
- `429`: Too many requests.

---

[API](https://skmtc.dev/meow/apis/meow-api.md) - [All operations](https://skmtc.dev/meow/apis/meow-api/llms.txt) - [OpenAPI document](https://skmtc.dev/meow/apis/meow-api/revisions/ea2d7e25b63b?raw)