Effective Dates
Request URL
POST /transfer-to/ach/effective-dates
Description
This endpoint returns a list of valid effective entry dates for ACH transaction requests based on the specified date parameter. The specified date may be past, present, or future. The list of dates returned represents valid effective entry dates that can be used or that could have been used on or after the given date.
When using this endpoint to determine possible effective entry dates for upcoming ACH transaction requests, keep in mind that same day transfer requests must be received prior to 9:30am CST M-F on the date specified in the effectiveEntryDate parameter of a /transfer-to/ach/create request. Next day transfer requests must be received prior to 7:30pm CST M-F on the date specified in the effectiveEntryDate parameter of a /transfer-to/ach/create request.
Schema
Property table for transfer-to/ach/effective-dates
Property | Description | Required | Schema |
---|---|---|---|
date | date | No | { "type": "string", "format": "date-time", "nullable": true } |
mode | mode | No | { "type": "string", "nullable": true } |
Request Body
Snippet Examples
javascript
const axios = require('axios');
const data = {
"date": "2024-11-13T00:00:00Z"
};
const config = {
method: 'POST',
url: '${CONNECTFI_BASE_URL}/transfer-to/ach/effective-dates',
headers: {
'Content-Type': "application/json",
'x-connectfi-token': "A long random string token received from /auth/get-token request"
},
data
};
let result;
try {
result = await axios.request(config);
if (result.status === 200) {
console.log(JSON.stringify(result.data));
}
} catch (err) {
console.log({
errCode: err.code,
responseStatus: err.response && err.response.status,
data: err.response && JSON.stringify(err.response.data)
});
}
cURL
curl --location "CONNECTFI_BASE_URL/transfer-to/ach/effective-dates" --data "{ \"date\":\"2024-11-13T00:00:00Z\"}" --header "Content-Type: application/json" --header "x-connectfi-token: A long random string token received from /auth/get-token request"
Successful Response Examples
200 SUCCESSFUL RESPONSE
HEADERS
Header | Value |
---|---|
Content-Type | application/json |
x-connectfi-token | A long random string token received from /auth/get-token request |
REQUEST BODY
RESPONSE BODY
{
"code": "0",
"data": [
{
"date": "2024-11-11",
"mode": "SameDate"
},
{
"date": "2024-11-12",
"mode": "NextDay"
},
{
"date": "2024-11-13",
"mode": "FutureDated"
},
{
"date": "2024-11-14",
"mode": "FutureDated"
},
{
"date": "2024-11-15",
"mode": "FutureDated"
},
{
"date": "2024-11-18",
"mode": "FutureDated"
},
{
"date": "2024-11-19",
"mode": "FutureDated"
},
{
"date": "2024-11-20",
"mode": "FutureDated"
},
{
"date": "2024-11-21",
"mode": "FutureDated"
},
{
"date": "2024-11-22",
"mode": "FutureDated"
},
{
"date": "2024-11-25",
"mode": "FutureDated"
},
{
"date": "2024-11-26",
"mode": "FutureDated"
}
],
"requestId": "705888c0a1ce11efadaf56da8a860aa8"
}