Bank Feeds
Bank Feeds solution enables your SMB users to set up bank feeds from accounts in your application to supported accounting software.
Summary
Bank Feeds: Bank Feeds solution enables your SMB users to set up bank feeds from accounts in your application to supported accounting software.
A bank feed is a connection between a source bank account in your application and a target bank account in a supported accounting software.
Explore solution | See OpenAPI spec
Endpoints
| Endpoints | Description |
|---|---|
| Companies | Create and manage your SMB users' companies. |
| Connections | Create new and manage existing data connections for a company. |
| Source accounts | Provide and manage lists of source bank accounts. |
| Account mapping | Extra functionality for building an account management UI. |
| Company information | Get detailed information about a company from the underlying platform. |
| Transactions | Create new bank account transactions for a company's connections, and see previous operations. |
Table of Contents
- Summary
- Endpoints
- SDK Installation
- IDE Support
- SDK Example Usage
- Available Resources and Operations
- Retries
- Error Handling
- Server Selection
- Custom HTTP Client
- Authentication
- Resource Management
- Support
SDK Installation
The SDK can be installed with uv, pip, or poetry package managers.
uv
uv is a fast Python package installer and resolver, designed as a drop-in replacement for pip and pip-tools. It's recommended for its speed and modern Python tooling capabilities.
uv add codat-bankfeeds
PIP
PIP is the default package installer for Python, enabling easy installation and management of packages from PyPI via the command line.
pip install codat-bankfeeds
Poetry
Poetry is a modern tool that simplifies dependency management and package publishing by using a single pyproject.toml file to handle project metadata and dependencies.
poetry add codat-bankfeeds
Shell and script usage with uv
You can use this SDK in a Python shell with uv and the uvx command that comes with it like so:
uvx --from codat-bankfeeds python
It's also possible to write a standalone Python script without needing to set up a whole project like so:
#!/usr/bin/env -S uv run --script
# /// script
# requires-python = ">=3.10"
# dependencies = [
# "codat-bankfeeds",
# ]
# ///
from codat_bankfeeds import CodatBankFeeds
sdk = CodatBankFeeds(
# SDK arguments
)
# Rest of script here...
Once that is saved to a file, you can run it with uv run script.py where
script.py can be replaced with the actual file name.
IDE Support
PyCharm
Generally, the SDK will work well with most IDEs out of the box. However, when using PyCharm, you can enjoy much better integration with Pydantic by installing an additional plugin.
SDK Example Usage
Example
# Synchronous Example
from codat_bankfeeds import CodatBankFeeds
from codat_bankfeeds.models import shared
with CodatBankFeeds(
security=shared.Security(
auth_header="Basic BASE_64_ENCODED(API_KEY)",
),
) as codat_bank_feeds:
res = codat_bank_feeds.companies.create(request={
"description": "Requested early access to the new financing scheme.",
"name": "Bank of Dave",
})
# Handle response
print(res)
The same SDK client can also be used to make asynchronous requests by importing asyncio.
# Asynchronous Example
import asyncio
from codat_bankfeeds import CodatBankFeeds
from codat_bankfeeds.models import shared
async def main():
async with CodatBankFeeds(
security=shared.Security(
auth_header="Basic BASE_64_ENCODED(API_KEY)",
),
) as codat_bank_feeds:
res = await codat_bank_feeds.companies.create_async(request={
"description": "Requested early access to the new financing scheme.",
"name": "Bank of Dave",
})
# Handle response
print(res)
asyncio.run(main())
Available Resources and Operations
Available methods
AccountMapping
BankAccounts
- create - Create bank account
- get_create_model - Get create/update bank account model
- list - List bank accounts
Companies
- create - Create company
- delete - Delete a company
- get - Get company
- get_access_token - Get company access token
- list - List companies
- replace - Replace company
- update - Update company
CompanyInformation
- get - Get company information
Connections
- create - Create connection
- delete - Delete connection
- get - Get connection
- list - List connections
- unlink - Unlink connection
ManagedBankFeeds
- get_latest_sync - Get latest sync
- get_sync - Get sync
- run_ad_hoc_sync - Run ad-hoc sync
SourceAccounts
- create - Create single source account
- create_batch - Create source accounts
- delete - Delete source account
- delete_credentials - Delete all source account credentials
- generate_credentials - Generate source account credentials
- generate_otp - Generate one-time password
- list - List source accounts
- update - Update source account
Transactions
- create - Create bank transactions
- get_create_model - Get create bank transactions model
- get_create_operation - Get create operation
- list_create_operations - List create operations
Retries
Every operation in this SDK retries failed requests with a default backoff strategy. By default it retries connection errors and responses with status 408, 429 or 5XX, starting at 500 ms and backing off by a factor of 1.5 up to 60 s between attempts, for at most an hour. You can override the retry strategy for a single call, or across the entire SDK.
To change the default retry strategy for a single API call, simply provide a RetryConfig object to the call:
from codat_bankfeeds import CodatBankFeeds
from codat_bankfeeds.models import shared
from codat_bankfeeds.utils import BackoffStrategy, RetryConfig
with CodatBankFeeds(
security=shared.Security(
auth_header="Basic BASE_64_ENCODED(API_KEY)",
),
) as codat_bank_feeds:
res = codat_bank_feeds.companies.create(request={
"description": "Requested early access to the new financing scheme.",
"name": "Bank of Dave",
}, retries=RetryConfig("backoff", BackoffStrategy(1, 50, 1.1, 100), False))
# Handle response
print(res)
If you'd like to override the default retry strategy for all operations, you can use the retry_config optional parameter when initializing the SDK:
from codat_bankfeeds import CodatBankFeeds
from codat_bankfeeds.models import shared
from codat_bankfeeds.utils import BackoffStrategy, RetryConfig
with CodatBankFeeds(
retry_config=RetryConfig("backoff", BackoffStrategy(1, 50, 1.1, 100), False),
security=shared.Security(
auth_header="Basic BASE_64_ENCODED(API_KEY)",
),
) as codat_bank_feeds:
res = codat_bank_feeds.companies.create(request={
"description": "Requested early access to the new financing scheme.",
"name": "Bank of Dave",
})
# Handle response
print(res)
Error Handling
CodatBankFeedsError is the base class for all HTTP error responses. It has the following properties:
| Property | Type | Description |
|---|---|---|
err.message |
str |
Error message |
err.status_code |
int |
HTTP response status code eg 404 |
err.headers |
Mapping[str, str] |
HTTP response headers, looked up case-insensitively |
err.body |
str |
HTTP body. Can be empty string if no body is returned. |
err.raw_response |
Any |
The SDK exception or response the error was built from; prefer the properties above |
err.data |
Optional. Some errors may contain structured data. See Error Classes. |
Example
from codat_bankfeeds import CodatBankFeeds
from codat_bankfeeds.models import errors, shared
with CodatBankFeeds(
security=shared.Security(
auth_header="Basic BASE_64_ENCODED(API_KEY)",
),
) as codat_bank_feeds:
res = None
try:
res = codat_bank_feeds.companies.create(request={
"description": "Requested early access to the new financing scheme.",
"name": "Bank of Dave",
})
# Handle response
print(res)
except errors.CodatBankFeedsError as e:
# The base class for HTTP error responses
print(e.message)
print(e.status_code)
print(e.body)
print(e.headers)
print(e.raw_response)
# Depending on the method different errors may be thrown
if isinstance(e, errors.ErrorMessage):
print(e.data.can_be_retried) # Optional[str]
print(e.data.correlation_id) # Optional[str]
print(e.data.detailed_error_code) # Optional[int]
print(e.data.error) # Optional[str]
print(e.data.service) # Optional[str]
Error Classes
Primary errors:
CodatBankFeedsError: The base class for HTTP error responses.ErrorMessage: A Codat API error response. Its structured fields are onerr.data.
Less common errors (2)
Inherit from CodatBankFeedsError:
SDKError: The fallback error class if no more specific error class is matched.ResponseValidationError: Type mismatch between the response data and the expected Pydantic model. Provides access to the Pydantic validation error via thecauseattribute.
Network failures, such as a refused connection or a timeout, are raised by the underlying HTTP library: urllib3 by default, or httpx when you pass client.
Server Selection
Override Server URL Per-Client
The default server can be overridden globally by passing a URL to the server_url: str optional parameter when initializing the SDK client instance. For example:
from codat_bankfeeds import CodatBankFeeds
from codat_bankfeeds.models import shared
with CodatBankFeeds(
server_url="https://api.codat.io",
security=shared.Security(
auth_header="Basic BASE_64_ENCODED(API_KEY)",
),
) as codat_bank_feeds:
res = codat_bank_feeds.companies.create(request={
"description": "Requested early access to the new financing scheme.",
"name": "Bank of Dave",
})
# Handle response
print(res)
Custom HTTP Client
The Python SDK can make its API calls through an httpx client you provide. This is a convenient way to configure cookies, proxies, custom headers, and other low-level settings. Pass an httpx.Client instance as the client parameter when initializing the SDK. It carries every request, including those made by the _async methods. The async_client parameter is accepted for compatibility with earlier SDK versions but is not used.
The SDK sets the timeout of every request itself, so a timeout configured on the httpx.Client is overridden. Use the timeout_ms parameter instead, when initializing the SDK or on a single call. The default is 5000 ms.
For example, you could specify a header for every request that this SDK makes as follows:
from codat_bankfeeds import CodatBankFeeds
import httpx
http_client = httpx.Client(headers={"x-custom-header": "someValue"})
s = CodatBankFeeds(client=http_client)
or you could subclass httpx.Client to wrap each request in your own custom logic:
from codat_bankfeeds import CodatBankFeeds
import httpx
class CustomClient(httpx.Client):
def send(self, request: httpx.Request, **kwargs) -> httpx.Response:
request.headers["Client-Level-Header"] = "added by client"
return super().send(request, **kwargs)
s = CodatBankFeeds(client=CustomClient())
Authentication
Per-Client Security Schemes
This SDK supports the following security scheme globally:
| Name | Type | Scheme |
|---|---|---|
auth_header |
apiKey | API key |
You can set the security parameters through the security optional parameter when initializing the SDK client instance. For example:
from codat_bankfeeds import CodatBankFeeds
from codat_bankfeeds.models import shared
with CodatBankFeeds(
security=shared.Security(
auth_header="Basic BASE_64_ENCODED(API_KEY)",
),
) as codat_bank_feeds:
res = codat_bank_feeds.companies.create(request={
"description": "Requested early access to the new financing scheme.",
"name": "Bank of Dave",
})
# Handle response
print(res)
Resource Management
The CodatBankFeeds class implements the context manager protocol, so existing code that uses it in a with or async with block keeps working. Leaving the context does not close any HTTP connections: if you pass your own client, close it yourself when you are done. In longer-lived programs, create a single SDK instance via a context manager and reuse it across the application.
from codat_bankfeeds import CodatBankFeeds
from codat_bankfeeds.models import shared
def main():
with CodatBankFeeds(
security=shared.Security(
auth_header="Basic BASE_64_ENCODED(API_KEY)",
),
) as codat_bank_feeds:
# Rest of application here...
pass
# Or when using async:
async def amain():
async with CodatBankFeeds(
security=shared.Security(
auth_header="Basic BASE_64_ENCODED(API_KEY)",
),
) as codat_bank_feeds:
# Rest of application here...
pass
Support
If you encounter any challenges while utilizing our SDKs, please don't hesitate to reach out for assistance. You can raise any issues by contacting your dedicated Codat representative or reaching out to our support team. We're here to help ensure a smooth experience for you.
Metadata
Release files for codat-bankfeeds 13.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| codat_bankfeeds-13.0.0.tar.gz | 110.4 kB | With provenance | Details for codat_bankfeeds-13.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| codat_bankfeeds-13.0.0-py3-none-any.whl | Python 3 | none | any | Details for codat_bankfeeds-13.0.0-py3-none-any.whl |
Total release size: 411.9 kB
Release files / codat_bankfeeds-13.0.0.tar.gz
| Download URL | codat_bankfeeds-13.0.0.tar.gz |
|---|---|
| Size | 110.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
78c27d5358a37f9119d6f17c24d7c7f538e918526469286450a71b857bc4bd42
|
|
BLAKE2b-256 checksum How to use checksums |
40505b2aafb81a5f3fd9911c81a58b9a1d97e2a2aa60ab88bc0428e96dcd89dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logRelease files / codat_bankfeeds-13.0.0-py3-none-any.whl
| Download URL | codat_bankfeeds-13.0.0-py3-none-any.whl |
|---|---|
| Size | 301.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e2211bc24a4490cb9fb65b3a0dcafbcee5a92504e574d8cc3401d5ddf06548db
|
|
BLAKE2b-256 checksum How to use checksums |
0ff3166faddeb04f89a87dc78b7c479411814ec0f37385cc2839804e3a143ca3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logSecurity for codat-bankfeeds 13.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for codat_bankfeeds-13.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.