It has been generated successfully based on your OpenAPI spec. However, it is not yet ready for production use. Here are some next steps:
- 🛠 Make your SDK feel handcrafted by customizing it
- ♻️ Refine your SDK quickly by iterating locally with the Speakeasy CLI
- 🎁 Publish your SDK to package managers by configuring automatic publishing
- ✨ When ready to productionize, delete this section from the README
Formance Stack API: Open, modular foundation for unique payments flows
This API is documented in OpenAPI format.
Formance Stack offers one forms of authentication:
- OAuth2 OAuth2 - an open protocol to allow secure authorization in a simple and standard method from web, mobile and desktop applications.
Note
Python version upgrade policy
Once a Python version reaches its official end of life date, a 3-month grace period is provided for users to upgrade. Following this grace period, the minimum python version supported in the SDK will be updated.
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 formance-sdk-python
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 formance-sdk-python
You can use this SDK in a Python shell with uv and the uvx
command that comes with it like so:
uvx --from formance-sdk-python 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.9"
# dependencies = [
# "formance-sdk-python",
# ]
# ///
from formance_sdk_python import SDK
sdk = SDK(
# 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.
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 formance_sdk_python import SDK
from formance_sdk_python.models import shared
with SDK(
security=shared.Security(
client_id="<YOUR_CLIENT_ID_HERE>",
client_secret="<YOUR_CLIENT_SECRET_HERE>",
),
) as sdk:
res = sdk.get_versions()
assert res.get_versions_response is not None
# Handle response
print(res.get_versions_response)
The same SDK client can also be used to make asychronous requests by importing asyncio.
# Asynchronous Example
import asyncio
from formance_sdk_python import SDK
from formance_sdk_python.models import shared
async def main():
async with SDK(
security=shared.Security(
client_id="<YOUR_CLIENT_ID_HERE>",
client_secret="<YOUR_CLIENT_SECRET_HERE>",
),
) as sdk:
res = await sdk.get_versions_async()
assert res.get_versions_response is not None
# Handle response
print(res.get_versions_response)
asyncio.run(main())
Available methods
- create_client - Create client
- create_secret - Add a secret to a client
- delete_client - Delete client
- delete_secret - Delete a secret from a client
- get_oidc_well_knowns - Retrieve OpenID connect well-knowns.
- get_server_info - Get server info
- list_clients - List clients
- list_users - List users
- read_client - Read client
- read_user - Read user
- update_client - Update client
- create_transactions - Create a new batch of transactions to a ledger
- add_metadata_on_transaction - Set the metadata of a transaction by its ID
- add_metadata_to_account - Add metadata to an account
- count_accounts - Count the accounts from a ledger
- count_transactions - Count the transactions from a ledger
- create_transaction - Create a new transaction to a ledger
- get_account - Get account by its address
- get_balances - Get the balances from a ledger's account
- get_balances_aggregated - Get the aggregated balances from selected accounts
- get_info - Show server information
- get_ledger_info - Get information about a ledger
- get_mapping - Get the mapping of a ledger
- get_transaction - Get transaction from a ledger by its ID
- list_accounts - List accounts from a ledger
- list_logs - List the logs from a ledger
- list_transactions - List transactions from a ledger
- read_stats - Get statistics from a ledger
- revert_transaction - Revert a ledger transaction by its ID
run_script- Execute a Numscript⚠️ Deprecated- update_mapping - Update the mapping of a ledger
- add_metadata_on_transaction - Set the metadata of a transaction by its ID
- add_metadata_to_account - Add metadata to an account
- count_accounts - Count the accounts from a ledger
- count_transactions - Count the transactions from a ledger
- create_bulk - Bulk request
- create_ledger - Create a ledger
- create_transaction - Create a new transaction to a ledger
- delete_account_metadata - Delete metadata by key
- delete_ledger_metadata - Delete ledger metadata by key
- delete_transaction_metadata - Delete metadata by key
- export_logs - Export logs
- get_account - Get account by its address
- get_balances_aggregated - Get the aggregated balances from selected accounts
- get_info - Show server information
- get_ledger - Get a ledger
- get_ledger_info - Get information about a ledger
- get_metrics - Read in memory metrics
- get_transaction - Get transaction from a ledger by its ID
- get_volumes_with_balances - Get list of volumes with balances for (account/asset)
- import_logs
- list_accounts - List accounts from a ledger
- list_ledgers - List ledgers
- list_logs - List the logs from a ledger
- list_transactions - List transactions from a ledger
- read_stats - Get statistics from a ledger
- revert_transaction - Revert a ledger transaction by its ID
- update_ledger_metadata - Update ledger metadata
- cancel_event - Cancel a running workflow
- create_trigger - Create trigger
- create_workflow - Create workflow
- delete_trigger - Delete trigger
- delete_workflow - Delete a flow by id
- get_instance - Get a workflow instance by id
- get_instance_history - Get a workflow instance history by id
- get_instance_stage_history - Get a workflow instance stage history
- get_workflow - Get a flow by id
- list_instances - List instances of a workflow
- list_triggers - List triggers
- list_triggers_occurrences - List triggers occurrences
- list_workflows - List registered workflows
- orchestrationget_server_info - Get server info
- read_trigger - Read trigger
- run_workflow - Run workflow
- send_event - Send an event to a running workflow
- cancel_event - Cancel a running workflow
- create_trigger - Create trigger
- create_workflow - Create workflow
- delete_trigger - Delete trigger
- delete_workflow - Delete a flow by id
- get_instance - Get a workflow instance by id
- get_instance_history - Get a workflow instance history by id
- get_instance_stage_history - Get a workflow instance stage history
- get_server_info - Get server info
- get_workflow - Get a flow by id
- list_instances - List instances of a workflow
- list_triggers - List triggers
- list_triggers_occurrences - List triggers occurrences
- list_workflows - List registered workflows
- read_trigger - Read trigger
- run_workflow - Run workflow
- send_event - Send an event to a running workflow
- test_trigger - Test trigger
- add_account_to_pool - Add an account to a pool
- connectors_transfer - Transfer funds between Connector accounts
- create_account - Create an account
- create_bank_account - Create a BankAccount in Payments and on the PSP
- create_payment - Create a payment
- create_pool - Create a Pool
- create_transfer_initiation - Create a TransferInitiation
- delete_pool - Delete a Pool
- delete_transfer_initiation - Delete a transfer initiation
- forward_bank_account - Forward a bank account to a connector
- get_account_balances - Get account balances
- get_bank_account - Get a bank account created by user on Formance
get_connector_task- Read a specific task of the connector⚠️ Deprecated- get_connector_task_v1 - Read a specific task of the connector
- get_payment - Get a payment
- get_pool - Get a Pool
- get_pool_balances - Get pool balances
- get_transfer_initiation - Get a transfer initiation
- install_connector - Install a connector
- list_all_connectors - List all installed connectors
- list_bank_accounts - List bank accounts created by user on Formance
- list_configs_available_connectors - List the configs of each available connector
list_connector_tasks- List tasks from a connector⚠️ Deprecated- list_connector_tasks_v1 - List tasks from a connector
- list_payments - List payments
- list_pools - List Pools
- list_transfer_initiations - List Transfer Initiations
- paymentsget_account - Get an account
- paymentsget_server_info - Get server info
- paymentslist_accounts - List accounts
read_connector_config- Read the config of a connector⚠️ Deprecated- read_connector_config_v1 - Read the config of a connector
- remove_account_from_pool - Remove an account from a pool
reset_connector- Reset a connector⚠️ Deprecated- reset_connector_v1 - Reset a connector
- retry_transfer_initiation - Retry a failed transfer initiation
- reverse_transfer_initiation - Reverse a transfer initiation
- udpate_transfer_initiation_status - Update the status of a transfer initiation
uninstall_connector- Uninstall a connector⚠️ Deprecated- uninstall_connector_v1 - Uninstall a connector
- update_bank_account_metadata - Update metadata of a bank account
- update_connector_config_v1 - Update the config of a connector
- update_metadata - Update metadata
-
add_account_to_pool - Add an account to a pool
-
approve_payment_initiation - Approve a payment initiation
-
create_account - Create a formance account object. This object will not be forwarded to the connector. It is only used for internal purposes.
-
create_bank_account - Create a formance bank account object. This object will not be forwarded to the connector until you called the forwardBankAccount method.
-
create_payment - Create a formance payment object. This object will not be forwarded to the connector. It is only used for internal purposes.
-
create_pool - Create a formance pool object
-
delete_payment_initiation - Delete a payment initiation by ID
-
delete_pool - Delete a pool by ID
-
forward_bank_account - Forward a Bank Account to a PSP for creation
-
get_account - Get an account by ID
-
get_account_balances - Get account balances
-
get_bank_account - Get a Bank Account by ID
-
get_connector_config - Get a connector configuration by ID
-
get_connector_schedule - Get a connector schedule by ID
-
get_info - Show server information
-
get_payment - Get a payment by ID
-
get_payment_initiation - Get a payment initiation by ID
-
get_pool - Get a pool by ID
-
get_pool_balances - Get pool balances
-
get_task - Get a task and its result by ID
-
initiate_payment - Initiate a payment
-
install_connector - Install a connector
-
list_accounts - List all accounts
-
list_bank_accounts - List all bank accounts
-
list_connector_configs - List all connector configurations
-
list_connector_schedule_instances - List all connector schedule instances
-
list_connector_schedules - List all connector schedules
-
list_connectors - List all connectors
-
list_payment_initiation_adjustments - List all payment initiation adjustments
-
list_payment_initiation_related_payments - List all payments related to a payment initiation
-
list_payment_initiations - List all payment initiations
-
list_payments - List all payments
-
list_pools - List all pools
-
reject_payment_initiation - Reject a payment initiation
-
remove_account_from_pool - Remove an account from a pool
-
reset_connector - Reset a connector. Be aware that this will delete all data and stop all existing tasks like payment initiations and bank account creations.
-
retry_payment_initiation - Retry a payment initiation
-
reverse_payment_initiation - Reverse a payment initiation
-
uninstall_connector - Uninstall a connector
-
update_bank_account_metadata - Update a bank account's metadata
-
update_payment_metadata - Update a payment's metadata
- create_policy - Create a policy
- delete_policy - Delete a policy
- get_policy - Get a policy
- get_reconciliation - Get a reconciliation
- list_policies - List policies
- list_reconciliations - List reconciliations
- reconcile - Reconcile using a policy
- reconciliationget_server_info - Get server info
- get_versions - Show stack version information
search- search.v1⚠️ Deprecatedsearchget_server_info- Get server info⚠️ Deprecated
- confirm_hold - Confirm a hold
- create_balance - Create a balance
- create_wallet - Create a new wallet
- credit_wallet - Credit a wallet
- debit_wallet - Debit a wallet
- get_balance - Get detailed balance
- get_hold - Get a hold
- get_holds - Get all holds for a wallet
- get_transactions
- get_wallet - Get a wallet
- get_wallet_summary - Get wallet summary
- list_balances - List balances of a wallet
- list_wallets - List all wallets
- update_wallet - Update a wallet
- void_hold - Cancel a hold
- walletsget_server_info - Get server info
- activate_config - Activate one config
- change_config_secret - Change the signing secret of a config
- deactivate_config - Deactivate one config
- delete_config - Delete one config
- get_many_configs - Get many configs
- insert_config - Insert a new config
- test_config - Test one config
- update_config - Update one config
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 formance_sdk_python import SDK
from formance_sdk_python.models import shared
from formance_sdk_python.utils import BackoffStrategy, RetryConfig
with SDK(
security=shared.Security(
client_id="<YOUR_CLIENT_ID_HERE>",
client_secret="<YOUR_CLIENT_SECRET_HERE>",
),
) as sdk:
res = sdk.get_versions(,
RetryConfig("backoff", BackoffStrategy(1, 50, 1.1, 100), False))
assert res.get_versions_response is not None
# Handle response
print(res.get_versions_response)
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 formance_sdk_python import SDK
from formance_sdk_python.models import shared
from formance_sdk_python.utils import BackoffStrategy, RetryConfig
with SDK(
retry_config=RetryConfig("backoff", BackoffStrategy(1, 50, 1.1, 100), False),
security=shared.Security(
client_id="<YOUR_CLIENT_ID_HERE>",
client_secret="<YOUR_CLIENT_SECRET_HERE>",
),
) as sdk:
res = sdk.get_versions()
assert res.get_versions_response is not None
# Handle response
print(res.get_versions_response)
Handling errors in this SDK should largely match your expectations. All operations return a response object or raise an exception.
By default, an API error will raise a errors.SDKError exception, which has the following properties:
Property | Type | Description |
---|---|---|
.status_code |
int | The HTTP status code |
.message |
str | The error message |
.raw_response |
httpx.Response | The raw HTTP response |
.body |
str | The response content |
When custom error responses are specified for an operation, the SDK may also raise their associated exceptions. You can refer to respective Errors tables in SDK docs for more details on possible exception types for each operation. For example, the add_metadata_on_transaction_async
method may raise the following exceptions:
Error Type | Status Code | Content Type |
---|---|---|
errors.V2ErrorResponse | default | application/json |
errors.SDKError | 4XX, 5XX | */* |
from formance_sdk_python import SDK
from formance_sdk_python.models import errors, shared
with SDK(
security=shared.Security(
client_id="<YOUR_CLIENT_ID_HERE>",
client_secret="<YOUR_CLIENT_SECRET_HERE>",
),
) as sdk:
res = None
try:
res = sdk.ledger.v2.add_metadata_on_transaction(request={
"id": 1234,
"ledger": "ledger001",
"request_body": {
"admin": "true",
},
"dry_run": True,
})
assert res is not None
# Handle response
print(res)
except errors.V2ErrorResponse as e:
# handle e.data: errors.V2ErrorResponseData
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 | Default values |
---|---|---|---|
0 | http://localhost |
||
1 | https://{organization}.{environment}.formance.cloud |
environment: models.ServerEnvironment organization: str |
"eu.sandbox" "orgID-stackID" |
If the selected server has variables, you may override their default values through the additional parameters made available in the SDK constructor.
from formance_sdk_python import SDK
from formance_sdk_python.models import shared
with SDK(
server_idx=1,
security=shared.Security(
client_id="<YOUR_CLIENT_ID_HERE>",
client_secret="<YOUR_CLIENT_SECRET_HERE>",
),
) as sdk:
res = sdk.get_versions()
assert res.get_versions_response is not None
# Handle response
print(res.get_versions_response)
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 formance_sdk_python import SDK
from formance_sdk_python.models import shared
with SDK(
server_url="http://localhost",
security=shared.Security(
client_id="<YOUR_CLIENT_ID_HERE>",
client_secret="<YOUR_CLIENT_SECRET_HERE>",
),
) as sdk:
res = sdk.get_versions()
assert res.get_versions_response is not None
# Handle response
print(res.get_versions_response)
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 formance_sdk_python import SDK
import httpx
http_client = httpx.Client(headers={"x-custom-header": "someValue"})
s = SDK(client=http_client)
or you could wrap the client with your own custom logic:
from formance_sdk_python import SDK
from formance_sdk_python.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 = SDK(async_client=CustomClient(httpx.AsyncClient()))
This SDK supports the following security scheme globally:
Name | Type | Scheme |
---|---|---|
client_id client_secret |
oauth2 | OAuth2 Client Credentials Flow |
You can set the security parameters through the security
optional parameter when initializing the SDK client instance. For example:
from formance_sdk_python import SDK
from formance_sdk_python.models import shared
with SDK(
security=shared.Security(
client_id="<YOUR_CLIENT_ID_HERE>",
client_secret="<YOUR_CLIENT_SECRET_HERE>",
),
) as sdk:
res = sdk.get_versions()
assert res.get_versions_response is not None
# Handle response
print(res.get_versions_response)
The SDK
class implements the context manager protocol and registers a finalizer function to close the underlying sync and async HTTPX clients it uses under the hood. This will close HTTP connections, release memory and free up other resources held by the SDK. In short-lived Python programs and notebooks that make a few SDK method calls, resource management may not be a concern. However, in longer-lived programs, it is beneficial to create a single SDK instance via a context manager and reuse it across the application.
from formance_sdk_python import SDK
from formance_sdk_python.models import shared
def main():
with SDK(
security=shared.Security(
client_id="<YOUR_CLIENT_ID_HERE>",
client_secret="<YOUR_CLIENT_SECRET_HERE>",
),
) as sdk:
# Rest of application here...
# Or when using async:
async def amain():
async with SDK(
security=shared.Security(
client_id="<YOUR_CLIENT_ID_HERE>",
client_secret="<YOUR_CLIENT_SECRET_HERE>",
),
) as sdk:
# Rest of application here...
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 formance_sdk_python import SDK
import logging
logging.basicConfig(level=logging.DEBUG)
s = SDK(debug_logger=logging.getLogger("formance_sdk_python"))
This SDK is in beta, and there may be breaking changes between versions without a major version update. Therefore, we recommend pinning usage to a specific package version. This way, you can install the same version each time without breaking changes unless you are intentionally looking for the latest version.
While we value open-source contributions to this SDK, this library is generated programmatically. Feel free to open a PR or a Github issue as a proof of concept and we'll do our best to include it in a future release!