Codat's Accounting API is a flexible API for pulling and pushing up-to-date accounting data to your customer's accounting software. It gives you a simple way to view, create, update adn delete data without having to worry about each platform's specific complexities.
Accounting API: > ### New to Codat?
Our Accounting API reference is relevant only to our existing clients. Please reach out to your Codat contact so that we can find the right product for you.
A flexible API for pulling accounting data, normalized and aggregated from 20 accounting integrations.
Standardize how you connect to your customers’ accounting software. View, create, update, and delete data in the same way for all the leading accounting software.
| Endpoints | Description |
|---|---|
| Accounts | Access standardized Accounts from linked accounting software. |
| Account transactions | Access standardized Account transactions from linked accounting software. |
| Bank accounts | Access standardized Bank accounts from linked accounting software. |
| Bank account transactions | Access standardized Bank transactions for bank accounts from linked accounting software. |
| Bills | Access standardized Bills from linked accounting software. |
| Bill credit notes | Access standardized Bill credit notes from linked accounting software. |
| Bill payments | Access standardized Bill payments from linked accounting software. |
| Credit notes | Access standardized Credit notes from linked accounting software. |
| Customers | Access standardized Customers from linked accounting software. |
| Direct costs | Access standardized Direct costs from linked accounting software. |
| Direct incomes | Access standardized Direct incomes from linked accounting software. |
| Company info | Access standardized Company info from linked accounting software. |
| Invoices | Access standardized Invoices from linked accounting software. |
| Item receipts | Access standardized Item receipts from linked accounting software. |
| Items | Access standardized Items from linked accounting software. |
| Journals | Access standardized Journals from linked accounting software. |
| Journal entries | Access standardized Journal entries from linked accounting software. |
| Payments | Access standardized Payments from linked accounting software. |
| Payment methods | Access standardized Payment methods from linked accounting software. |
| Purchase orders | Access standardized Purchase orders from linked accounting software. |
| Sales orders | Access standardized Sales orders from linked accounting software. |
| Suppliers | Access standardized Suppliers from linked accounting software. |
| Tax rates | Access standardized Tax rates from linked accounting software. |
| Tracking categories | Access standardized Tracking categories from linked accounting software. |
| Transfers | Access standardized Transfers from linked accounting software. |
| Reports | Access standardized Reports from linked accounting software. |
The SDK can be installed with either pip or poetry package managers.
PIP is the default package installer for Python, enabling easy installation and management of packages from PyPI via the command line.
pip install codat-accounting
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-accounting
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.
# Synchronous Example
from codat_accounting import CodatAccounting
from codat_accounting.models import shared
s = CodatAccounting(
security=shared.Security(
auth_header="Basic BASE_64_ENCODED(API_KEY)",
),
)
res = s.account_transactions.get(request={
"account_transaction_id": "<value>",
"company_id": "8a210b68-6988-11ed-a1eb-0242ac120002",
"connection_id": "2e9d2c44-f675-40ba-8049-353bfcb5e171",
})
if res is not None:
# handle response
pass
The same SDK client can also be used to make asychronous requests by importing asyncio.
# Asynchronous Example
import asyncio
from codat_accounting import CodatAccounting
from codat_accounting.models import shared
async def main():
s = CodatAccounting(
security=shared.Security(
auth_header="Basic BASE_64_ENCODED(API_KEY)",
),
)
res = await s.account_transactions.get_async(request={
"account_transaction_id": "<value>",
"company_id": "8a210b68-6988-11ed-a1eb-0242ac120002",
"connection_id": "2e9d2c44-f675-40ba-8049-353bfcb5e171",
})
if res is not None:
# handle response
pass
asyncio.run(main())
Certain SDK methods accept file objects as part of a request body or multi-part request. It is possible and typically recommended to upload files as a stream rather than reading the entire contents into memory. This avoids excessive memory consumption and potentially crashing with out-of-memory errors when working with very large files. The following example demonstrates how to attach a file stream to a request.
[!TIP]
For endpoints that handle file uploads bytes arrays can also be used. However, using streams is recommended for large files.
from codat_accounting import CodatAccounting
from codat_accounting.models import shared
s = CodatAccounting(
security=shared.Security(
auth_header="Basic BASE_64_ENCODED(API_KEY)",
),
)
s.bills.upload_attachment(request={
"bill_id": "EILBDVJVNUAGVKRQ",
"company_id": "8a210b68-6988-11ed-a1eb-0242ac120002",
"connection_id": "2e9d2c44-f675-40ba-8049-353bfcb5e171",
})
# Use the SDK ...
Some of the endpoints in this SDK support retries. If you use the SDK without any configuration, it will fall back to the default retry strategy provided by the API. However, the default retry strategy can be overridden on a per-operation basis, 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_accounting import CodatAccounting
from codat_accounting.models import shared
from codataccounting.utils import BackoffStrategy, RetryConfig
s = CodatAccounting(
security=shared.Security(
auth_header="Basic BASE_64_ENCODED(API_KEY)",
),
)
res = s.account_transactions.get(request={
"account_transaction_id": "<value>",
"company_id": "8a210b68-6988-11ed-a1eb-0242ac120002",
"connection_id": "2e9d2c44-f675-40ba-8049-353bfcb5e171",
},
RetryConfig("backoff", BackoffStrategy(1, 50, 1.1, 100), False))
if res is not None:
# handle response
pass
If you'd like to override the default retry strategy for all operations that support retries, you can use the retry_config optional parameter when initializing the SDK:
from codat_accounting import CodatAccounting
from codat_accounting.models import shared
from codataccounting.utils import BackoffStrategy, RetryConfig
s = CodatAccounting(
retry_config=RetryConfig("backoff", BackoffStrategy(1, 50, 1.1, 100), False),
security=shared.Security(
auth_header="Basic BASE_64_ENCODED(API_KEY)",
),
)
res = s.account_transactions.get(request={
"account_transaction_id": "<value>",
"company_id": "8a210b68-6988-11ed-a1eb-0242ac120002",
"connection_id": "2e9d2c44-f675-40ba-8049-353bfcb5e171",
})
if res is not None:
# handle response
pass
Handling errors in this SDK should largely match your expectations. All operations return a response object or raise an error. If Error objects are specified in your OpenAPI Spec, the SDK will raise the appropriate Error type.
| Error Object | Status Code | Content Type |
|---|---|---|
| errors.ErrorMessage | 401,402,403,404,409,429,500,503 | application/json |
| errors.SDKError | 4xx-5xx | / |
from codat_accounting import CodatAccounting
from codat_accounting.models import errors, shared
s = CodatAccounting(
security=shared.Security(
auth_header="Basic BASE_64_ENCODED(API_KEY)",
),
)
res = None
try:
res = s.account_transactions.get(request={
"account_transaction_id": "<value>",
"company_id": "8a210b68-6988-11ed-a1eb-0242ac120002",
"connection_id": "2e9d2c44-f675-40ba-8049-353bfcb5e171",
})
if res is not None:
# handle response
pass
except errors.ErrorMessage as e:
# handle e.data: errors.ErrorMessageData
raise(e)
except errors.SDKError as e:
# handle exception
raise(e)
You can override the default server globally by passing a server index to the server_idx: int optional parameter when initializing the SDK client instance. The selected server will then be used as the default on the operations that use it. This table lists the indexes associated with the available servers:
| # | Server | Variables |
|---|---|---|
| 0 | https://api.codat.io | None |
from codat_accounting import CodatAccounting
from codat_accounting.models import shared
s = CodatAccounting(
server_idx=0,
security=shared.Security(
auth_header="Basic BASE_64_ENCODED(API_KEY)",
),
)
res = s.account_transactions.get(request={
"account_transaction_id": "<value>",
"company_id": "8a210b68-6988-11ed-a1eb-0242ac120002",
"connection_id": "2e9d2c44-f675-40ba-8049-353bfcb5e171",
})
if res is not None:
# handle response
pass
The default server can also be overridden globally by passing a URL to the server_url: str optional parameter when initializing the SDK client instance. For example:
from codat_accounting import CodatAccounting
from codat_accounting.models import shared
s = CodatAccounting(
server_url="https://api.codat.io",
security=shared.Security(
auth_header="Basic BASE_64_ENCODED(API_KEY)",
),
)
res = s.account_transactions.get(request={
"account_transaction_id": "<value>",
"company_id": "8a210b68-6988-11ed-a1eb-0242ac120002",
"connection_id": "2e9d2c44-f675-40ba-8049-353bfcb5e171",
})
if res is not None:
# handle response
pass
The Python SDK makes API calls using the httpx HTTP library. In order to provide a convenient way to configure timeouts, cookies, proxies, custom headers, and other low-level configuration, you can initialize the SDK client with your own HTTP client instance.
Depending on whether you are using the sync or async version of the SDK, you can pass an instance of HttpClient or AsyncHttpClient respectively, which are Protocol's ensuring that the client has the necessary methods to make API calls.
This allows you to wrap the client with your own custom logic, such as adding custom headers, logging, or error handling, or you can just pass an instance of httpx.Client or httpx.AsyncClient directly.
For example, you could specify a header for every request that this sdk makes as follows:
from codat_accounting import CodatAccounting
import httpx
http_client = httpx.Client(headers={"x-custom-header": "someValue"})
s = CodatAccounting(client=http_client)
or you could wrap the client with your own custom logic:
from codat_accounting import CodatAccounting
from codat_accounting.httpclient import AsyncHttpClient
import httpx
class CustomClient(AsyncHttpClient):
client: AsyncHttpClient
def __init__(self, client: AsyncHttpClient):
self.client = client
async def send(
self,
request: httpx.Request,
*,
stream: bool = False,
auth: Union[
httpx._types.AuthTypes, httpx._client.UseClientDefault, None
] = httpx.USE_CLIENT_DEFAULT,
follow_redirects: Union[
bool, httpx._client.UseClientDefault
] = httpx.USE_CLIENT_DEFAULT,
) -> httpx.Response:
request.headers["Client-Level-Header"] = "added by client"
return await self.client.send(
request, stream=stream, auth=auth, follow_redirects=follow_redirects
)
def build_request(
self,
method: str,
url: httpx._types.URLTypes,
*,
content: Optional[httpx._types.RequestContent] = None,
data: Optional[httpx._types.RequestData] = None,
files: Optional[httpx._types.RequestFiles] = None,
json: Optional[Any] = None,
params: Optional[httpx._types.QueryParamTypes] = None,
headers: Optional[httpx._types.HeaderTypes] = None,
cookies: Optional[httpx._types.CookieTypes] = None,
timeout: Union[
httpx._types.TimeoutTypes, httpx._client.UseClientDefault
] = httpx.USE_CLIENT_DEFAULT,
extensions: Optional[httpx._types.RequestExtensions] = None,
) -> httpx.Request:
return self.client.build_request(
method,
url,
content=content,
data=data,
files=files,
json=json,
params=params,
headers=headers,
cookies=cookies,
timeout=timeout,
extensions=extensions,
)
s = CodatAccounting(async_client=CustomClient(httpx.AsyncClient()))
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_accounting import CodatAccounting
from codat_accounting.models import shared
s = CodatAccounting(
security=shared.Security(
auth_header="Basic BASE_64_ENCODED(API_KEY)",
),
)
res = s.account_transactions.get(request={
"account_transaction_id": "<value>",
"company_id": "8a210b68-6988-11ed-a1eb-0242ac120002",
"connection_id": "2e9d2c44-f675-40ba-8049-353bfcb5e171",
})
if res is not None:
# handle response
pass
You can setup your SDK to emit debug logs for SDK requests and responses.
You can pass your own logger class directly into your SDK.
from codat_accounting import CodatAccounting
import logging
logging.basicConfig(level=logging.DEBUG)
s = CodatAccounting(debug_logger=logging.getLogger("codat_accounting"))
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.
FAQs
Access standardized accounting data from our accounting integrations.
We found that codat-accounting demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
ENISA’s 2024 report highlights the EU’s top cybersecurity threats, including rising DDoS attacks, ransomware, supply chain vulnerabilities, and weaponized AI.
Security News
NIST's new password guidelines remove periodic changes and special character requirements, focusing on longer, more secure passwords for better authentication practices.
Security News
A record 2,709 developers participated in the 2024 Ruby on Rails Community Survey, revealing key tools, practices, and trends shaping the Rails ecosystem.