# Confirmation of Funds API Specification API

> Confirmation of Funds API Specification API on Apizie: 4 endpoints (Create Funds Confirmation Consent, Get Funds Confirmation Consent, Delete Funds Confirmation Consent, Create Funds Confirmation) returned as clean JSON through one API key. Send your own provider key in the x-upstream-key header. Call it over REST at https://apizie.tech/v1/finance:openbanking-org-uk-confirmation-funds-openapi/{endpoint} or from Claude, ChatGPT and Cursor through the Apizie MCP server. Free plan: 1,000 requests a month.

- Project key: `finance:openbanking-org-uk-confirmation-funds-openapi`
- Category: Finance
- Status: byok
- Source: https://openbanking.org.uk
- Page: https://apizie.tech/api/finance/openbanking-org-uk-confirmation-funds-openapi
- OpenAPI: https://apizie.tech/api/finance/openbanking-org-uk-confirmation-funds-openapi/openapi.json

Swagger for Confirmation of Funds API Specification

## Endpoints

### Create Funds Confirmation Consent
`POST https://apizie.tech/v1/finance:openbanking-org-uk-confirmation-funds-openapi/create-funds-confirmation-consents` (byok)

| Parameter | Type | Required | Description |
|---|---|---|---|
| x-fapi-auth-date | string | no | The time when the PSU last logged in with the TPP. All dates in the HTTP headers are represented as RFC 7231 Full Dates. An example is… |
| x-fapi-customer-ip-address | string | no | The PSU's IP address if the PSU is currently logged in with the TPP. |
| x-fapi-interaction-id | string | no | An RFC4122 UID used as a correlation id. |
| x-customer-user-agent | string | no | Indicates the user-agent that the PSU is using. |
| body | object | yes | JSON request body |

### Get Funds Confirmation Consent
`GET https://apizie.tech/v1/finance:openbanking-org-uk-confirmation-funds-openapi/get-funds-confirmation-consents-consent-id` (byok)

| Parameter | Type | Required | Description |
|---|---|---|---|
| ConsentId | string | yes | ConsentId |
| x-fapi-auth-date | string | no | The time when the PSU last logged in with the TPP. All dates in the HTTP headers are represented as RFC 7231 Full Dates. An example is… |
| x-fapi-customer-ip-address | string | no | The PSU's IP address if the PSU is currently logged in with the TPP. |
| x-fapi-interaction-id | string | no | An RFC4122 UID used as a correlation id. |
| x-customer-user-agent | string | no | Indicates the user-agent that the PSU is using. |

### Delete Funds Confirmation Consent
`POST https://apizie.tech/v1/finance:openbanking-org-uk-confirmation-funds-openapi/delete-funds-confirmation-consents-consent-id` (byok)

| Parameter | Type | Required | Description |
|---|---|---|---|
| ConsentId | string | yes | ConsentId |
| x-fapi-auth-date | string | no | The time when the PSU last logged in with the TPP. All dates in the HTTP headers are represented as RFC 7231 Full Dates. An example is… |
| x-fapi-customer-ip-address | string | no | The PSU's IP address if the PSU is currently logged in with the TPP. |
| x-fapi-interaction-id | string | no | An RFC4122 UID used as a correlation id. |
| x-customer-user-agent | string | no | Indicates the user-agent that the PSU is using. |

### Create Funds Confirmation
`POST https://apizie.tech/v1/finance:openbanking-org-uk-confirmation-funds-openapi/create-funds-confirmations` (byok)

| Parameter | Type | Required | Description |
|---|---|---|---|
| x-fapi-auth-date | string | no | The time when the PSU last logged in with the TPP. All dates in the HTTP headers are represented as RFC 7231 Full Dates. An example is… |
| x-fapi-customer-ip-address | string | no | The PSU's IP address if the PSU is currently logged in with the TPP. |
| x-fapi-interaction-id | string | no | An RFC4122 UID used as a correlation id. |
| x-customer-user-agent | string | no | Indicates the user-agent that the PSU is using. |
| body | object | yes | JSON request body |

## Example
```
curl "https://apizie.tech/v1/finance:openbanking-org-uk-confirmation-funds-openapi/create-funds-confirmation-consents" \
  -H "x-api-key: $APIZIE_KEY" \
  -H "x-upstream-key: $PROVIDER_KEY"
```

## FAQ

### How do I call the Confirmation of Funds API Specification API?
Create a free Apizie key, then send POST https://apizie.tech/v1/finance:openbanking-org-uk-confirmation-funds-openapi/create-funds-confirmation-consents with the header x-api-key. Every endpoint returns { project, data, timestamp }.

### Is the Confirmation of Funds API Specification API free on Apizie?
Yes. The Free plan includes 1,000 requests a month at 100 requests a minute, no credit card. Confirmation of Funds API Specification itself also needs your own key from openbanking.org.uk.

### Can AI agents use the Confirmation of Funds API Specification API?
Yes. Add the Apizie MCP server (https://apizie.tech/mcp) to Claude, ChatGPT, Cursor or VS Code, then ask in plain language. The agent calls run_scraper with project key finance:openbanking-org-uk-confirmation-funds-openapi.

### What is the status of the Confirmation of Funds API Specification API?
Needs your own provider key (bring your own key)