usebridge-api 0.1.2__tar.gz → 0.1.3__tar.gz

{usebridge_api-0.1.2 → usebridge_api-0.1.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: usebridge-api
-Version: 0.1.2
+Version: 0.1.3
 Summary: Python client library for the Bridge API
 Keywords: bridge,api,sdk
 Requires-Python: >=3.10,<4.0

{usebridge_api-0.1.2 → usebridge_api-0.1.3}/pyproject.toml

@@ -4,7 +4,7 @@ dynamic = ["version"]
 
 [tool.poetry]
 name = "usebridge-api"
-version = "0.1.2"
+version = "0.1.3"
 description = "Python client library for the Bridge API"
 readme = "README.md"
 authors = []

{usebridge_api-0.1.2 → usebridge_api-0.1.3}/src/usebridge_api/billing/estimate_charges/client.py

@@ -100,6 +100,10 @@ class EstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Conflicting EstimateCharge exists`
+        - `Missing Service Eligibility Amount`
+
         Parameters
         ----------
         patient_id : str
@@ -141,6 +145,13 @@ class EstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Estimate Charge Status`
+        - `Missing Customer`
+        - `Missing Customer Payment Method`
+        - `Payment Already Captured`
+        - `Payment has been Voided`
+
         Parameters
         ----------
         id : str
@@ -172,6 +183,13 @@ class EstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Estimate Charge Status`
+        - `Missing Customer`
+        - `Missing Customer Payment Method`
+        - `Payment Already Captured`
+        - `Payment has been Voided`
+
         Parameters
         ----------
         id : str
@@ -203,6 +221,12 @@ class EstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Estimate Charge Status`
+        - `Missing Captured Transaction`
+        - `Missing Customer`
+        - `Missing Payment Intent`
+
         Parameters
         ----------
         id : str
@@ -234,6 +258,13 @@ class EstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Estimate Charge Status`
+        - `Missing Authorized Transaction`
+        - `Missing Customer`
+        - `Missing Payment Intent`
+        - `Payment Already Captured`
+
         Parameters
         ----------
         id : str
@@ -351,6 +382,10 @@ class AsyncEstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Conflicting EstimateCharge exists`
+        - `Missing Service Eligibility Amount`
+
         Parameters
         ----------
         patient_id : str
@@ -400,6 +435,13 @@ class AsyncEstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Estimate Charge Status`
+        - `Missing Customer`
+        - `Missing Customer Payment Method`
+        - `Payment Already Captured`
+        - `Payment has been Voided`
+
         Parameters
         ----------
         id : str
@@ -439,6 +481,13 @@ class AsyncEstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Estimate Charge Status`
+        - `Missing Customer`
+        - `Missing Customer Payment Method`
+        - `Payment Already Captured`
+        - `Payment has been Voided`
+
         Parameters
         ----------
         id : str
@@ -478,6 +527,12 @@ class AsyncEstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Estimate Charge Status`
+        - `Missing Captured Transaction`
+        - `Missing Customer`
+        - `Missing Payment Intent`
+
         Parameters
         ----------
         id : str
@@ -517,6 +572,13 @@ class AsyncEstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Estimate Charge Status`
+        - `Missing Authorized Transaction`
+        - `Missing Customer`
+        - `Missing Payment Intent`
+        - `Payment Already Captured`
+
         Parameters
         ----------
         id : str

{usebridge_api-0.1.2 → usebridge_api-0.1.3}/src/usebridge_api/billing/estimate_charges/raw_client.py

@@ -107,6 +107,10 @@ class RawEstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Conflicting EstimateCharge exists`
+        - `Missing Service Eligibility Amount`
+
         Parameters
         ----------
         patient_id : str
@@ -158,6 +162,13 @@ class RawEstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Estimate Charge Status`
+        - `Missing Customer`
+        - `Missing Customer Payment Method`
+        - `Payment Already Captured`
+        - `Payment has been Voided`
+
         Parameters
         ----------
         id : str
@@ -199,6 +210,13 @@ class RawEstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Estimate Charge Status`
+        - `Missing Customer`
+        - `Missing Customer Payment Method`
+        - `Payment Already Captured`
+        - `Payment has been Voided`
+
         Parameters
         ----------
         id : str
@@ -240,6 +258,12 @@ class RawEstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Estimate Charge Status`
+        - `Missing Captured Transaction`
+        - `Missing Customer`
+        - `Missing Payment Intent`
+
         Parameters
         ----------
         id : str
@@ -281,6 +305,13 @@ class RawEstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Estimate Charge Status`
+        - `Missing Authorized Transaction`
+        - `Missing Customer`
+        - `Missing Payment Intent`
+        - `Payment Already Captured`
+
         Parameters
         ----------
         id : str
@@ -401,6 +432,10 @@ class AsyncRawEstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Conflicting EstimateCharge exists`
+        - `Missing Service Eligibility Amount`
+
         Parameters
         ----------
         patient_id : str
@@ -452,6 +487,13 @@ class AsyncRawEstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Estimate Charge Status`
+        - `Missing Customer`
+        - `Missing Customer Payment Method`
+        - `Payment Already Captured`
+        - `Payment has been Voided`
+
         Parameters
         ----------
         id : str
@@ -493,6 +535,13 @@ class AsyncRawEstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Estimate Charge Status`
+        - `Missing Customer`
+        - `Missing Customer Payment Method`
+        - `Payment Already Captured`
+        - `Payment has been Voided`
+
         Parameters
         ----------
         id : str
@@ -534,6 +583,12 @@ class AsyncRawEstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Estimate Charge Status`
+        - `Missing Captured Transaction`
+        - `Missing Customer`
+        - `Missing Payment Intent`
+
         Parameters
         ----------
         id : str
@@ -575,6 +630,13 @@ class AsyncRawEstimateChargesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Estimate Charge Status`
+        - `Missing Authorized Transaction`
+        - `Missing Customer`
+        - `Missing Payment Intent`
+        - `Payment Already Captured`
+
         Parameters
         ----------
         id : str

{usebridge_api-0.1.2 → usebridge_api-0.1.3}/src/usebridge_api/billing/fees/client.py

@@ -101,6 +101,9 @@ class FeesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Conflicting Fee exists`
+
         Parameters
         ----------
         patient_id : str
@@ -148,6 +151,13 @@ class FeesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Fee Status`
+        - `Missing Customer`
+        - `Missing Customer Payment Method`
+        - `Payment Already Captured`
+        - `Payment has been Voided`
+
         Parameters
         ----------
         id : str
@@ -179,6 +189,12 @@ class FeesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Fee Status`
+        - `Missing Captured Transaction`
+        - `Missing Customer`
+        - `Missing Payment Intent`
+
         Parameters
         ----------
         id : str
@@ -298,6 +314,9 @@ class AsyncFeesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Conflicting Fee exists`
+
         Parameters
         ----------
         patient_id : str
@@ -353,6 +372,13 @@ class AsyncFeesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Fee Status`
+        - `Missing Customer`
+        - `Missing Customer Payment Method`
+        - `Payment Already Captured`
+        - `Payment has been Voided`
+
         Parameters
         ----------
         id : str
@@ -392,6 +418,12 @@ class AsyncFeesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Fee Status`
+        - `Missing Captured Transaction`
+        - `Missing Customer`
+        - `Missing Payment Intent`
+
         Parameters
         ----------
         id : str

{usebridge_api-0.1.2 → usebridge_api-0.1.3}/src/usebridge_api/billing/fees/raw_client.py

@@ -108,6 +108,9 @@ class RawFeesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Conflicting Fee exists`
+
         Parameters
         ----------
         patient_id : str
@@ -165,6 +168,13 @@ class RawFeesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Fee Status`
+        - `Missing Customer`
+        - `Missing Customer Payment Method`
+        - `Payment Already Captured`
+        - `Payment has been Voided`
+
         Parameters
         ----------
         id : str
@@ -206,6 +216,12 @@ class RawFeesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Fee Status`
+        - `Missing Captured Transaction`
+        - `Missing Customer`
+        - `Missing Payment Intent`
+
         Parameters
         ----------
         id : str
@@ -328,6 +344,9 @@ class AsyncRawFeesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Conflicting Fee exists`
+
         Parameters
         ----------
         patient_id : str
@@ -385,6 +404,13 @@ class AsyncRawFeesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Fee Status`
+        - `Missing Customer`
+        - `Missing Customer Payment Method`
+        - `Payment Already Captured`
+        - `Payment has been Voided`
+
         Parameters
         ----------
         id : str
@@ -426,6 +452,12 @@ class AsyncRawFeesClient:
         """
         This endpoint can only be used after setting up the billing integration. Refer to the [billing integration documentation](/documentation/integrations/billing/overview) for more details.
 
+        This endpoint may return a `409` error response with one of these public `message` values:
+        - `Invalid Fee Status`
+        - `Missing Captured Transaction`
+        - `Missing Customer`
+        - `Missing Payment Intent`
+
         Parameters
         ----------
         id : str

{usebridge_api-0.1.2 → usebridge_api-0.1.3}/src/usebridge_api/core/client_wrapper.py

@@ -29,12 +29,12 @@ class BaseClientWrapper:
         import platform
 
         headers: typing.Dict[str, str] = {
-            "User-Agent": "usebridge-api/0.1.2",
+            "User-Agent": "usebridge-api/0.1.3",
             "X-Fern-Language": "Python",
             "X-Fern-Runtime": f"python/{platform.python_version()}",
             "X-Fern-Platform": f"{platform.system().lower()}/{platform.release()}",
             "X-Fern-SDK-Name": "usebridge-api",
-            "X-Fern-SDK-Version": "0.1.2",
+            "X-Fern-SDK-Version": "0.1.3",
             **(self.get_custom_headers() or {}),
         }
         headers["X-API-Key"] = self.api_key