linq-python 0.16.0__tar.gz → 0.18.0__tar.gz

linq_python-0.18.0/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "0.18.0"
+}

{linq_python-0.16.0 → linq_python-0.18.0}/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## [0.18.0](https://github.com/linq-team/linq-python/compare/v0.17.0...v0.18.0) (2026-07-26)
+
+
+### Features
+
+* regenerate SDKs from updated API spec ([#40](https://github.com/linq-team/linq-python/issues/40)) ([4072b73](https://github.com/linq-team/linq-python/commit/4072b739b5b806b207c0e24ac1cce389524a87dd))
+
+## [0.17.0](https://github.com/linq-team/linq-python/compare/v0.16.0...v0.17.0) (2026-07-26)
+
+
+### Features
+
+* regenerate SDKs from updated API spec ([#38](https://github.com/linq-team/linq-python/issues/38)) ([da4334f](https://github.com/linq-team/linq-python/commit/da4334fd7eb72b89ae1ad17034b27ca92c277980))
+
 ## [0.16.0](https://github.com/linq-team/linq-python/compare/v0.15.1...v0.16.0) (2026-07-24)
 
 

{linq_python-0.16.0 → linq_python-0.18.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: linq-python
-Version: 0.16.0
+Version: 0.18.0
 Summary: The official Python library for the linq-api-v3 API
 Project-URL: Homepage, https://github.com/linq-team/linq-python
 Project-URL: Repository, https://github.com/linq-team/linq-python

{linq_python-0.16.0 → linq_python-0.18.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "linq-python"
-version = "0.16.0"
+version = "0.18.0"
 description = "The official Python library for the linq-api-v3 API"
 dynamic = ["readme"]
 license = "Apache-2.0"

{linq_python-0.16.0 → linq_python-0.18.0}/src/linq/_version.py

@@ -1,4 +1,4 @@
 # File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
 __title__ = "linq"
-__version__ = "0.16.0"  # x-release-please-version
+__version__ = "0.18.0"  # x-release-please-version

{linq_python-0.16.0 → linq_python-0.18.0}/src/linq/resources/chats/chats.py

@@ -300,6 +300,24 @@ class ChatsResource(SyncAPIResource):
         This rule applies only to `POST /v3/chats`. Follow-up messages on an existing
         chat (`POST /v3/chats/{chatId}/messages`) are not subject to this restriction.
 
+        ## Reusing an Existing Chat
+
+        Chats are keyed on the `from` line plus the exact set of `to` handles. Repeating
+        this request with the same `from` and `to` returns the **existing** chat and
+        sends the message into it instead of starting a second conversation.
+
+        A group chat that has a `display_name` is excluded from that matching. To run
+        several parallel groups over the same participants, name each one with
+        `PUT /v3/chats/{chatId}` before creating the next: the following
+        `POST /v3/chats` with the same `to` then returns a new, separate `chat_id`. Two
+        other cases also produce a new chat instead of reusing one — the participant set
+        changed (a participant was added or removed), or the `from` line left the group.
+
+        Whenever the response is a new chat, the first-message rules above apply to that
+        request: no link in the first message, and no `reply_to` or message effect. To
+        send into a chat you already know, use `POST /v3/chats/{chatId}/messages` with
+        its `chat_id`.
+
         Args:
           from_: Sender phone number in E.164 format. Must be a phone number that the
               authenticated partner has permission to send from.
@@ -921,6 +939,24 @@ class AsyncChatsResource(AsyncAPIResource):
         This rule applies only to `POST /v3/chats`. Follow-up messages on an existing
         chat (`POST /v3/chats/{chatId}/messages`) are not subject to this restriction.
 
+        ## Reusing an Existing Chat
+
+        Chats are keyed on the `from` line plus the exact set of `to` handles. Repeating
+        this request with the same `from` and `to` returns the **existing** chat and
+        sends the message into it instead of starting a second conversation.
+
+        A group chat that has a `display_name` is excluded from that matching. To run
+        several parallel groups over the same participants, name each one with
+        `PUT /v3/chats/{chatId}` before creating the next: the following
+        `POST /v3/chats` with the same `to` then returns a new, separate `chat_id`. Two
+        other cases also produce a new chat instead of reusing one — the participant set
+        changed (a participant was added or removed), or the `from` line left the group.
+
+        Whenever the response is a new chat, the first-message rules above apply to that
+        request: no link in the first message, and no `reply_to` or message effect. To
+        send into a chat you already know, use `POST /v3/chats/{chatId}/messages` with
+        its `chat_id`.
+
         Args:
           from_: Sender phone number in E.164 format. Must be a phone number that the
               authenticated partner has permission to send from.

{linq_python-0.16.0 → linq_python-0.18.0}/src/linq/resources/payment_requests.py

@@ -329,7 +329,7 @@ class PaymentRequestsResource(SyncAPIResource):
         *,
         limit: int | Omit = omit,
         offset: int | Omit = omit,
-        status: Literal["requested", "succeeded", "canceled", "expired"] | Omit = omit,
+        status: Literal["requested", "authorized", "succeeded", "canceled", "expired", "declined"] | Omit = omit,
         # Use the following arguments if you need to pass additional parameters to the API that aren't available via kwargs.
         # The extra values given here take precedence over values defined on the client or passed to this method.
         extra_headers: Headers | None = None,
@@ -715,7 +715,7 @@ class AsyncPaymentRequestsResource(AsyncAPIResource):
         *,
         limit: int | Omit = omit,
         offset: int | Omit = omit,
-        status: Literal["requested", "succeeded", "canceled", "expired"] | Omit = omit,
+        status: Literal["requested", "authorized", "succeeded", "canceled", "expired", "declined"] | Omit = omit,
         # Use the following arguments if you need to pass additional parameters to the API that aren't available via kwargs.
         # The extra values given here take precedence over values defined on the client or passed to this method.
         extra_headers: Headers | None = None,

{linq_python-0.16.0 → linq_python-0.18.0}/src/linq/types/payment_request_list_params.py

@@ -14,5 +14,5 @@ class PaymentRequestListParams(TypedDict, total=False):
     offset: int
     """Number of results to skip."""
 
-    status: Literal["requested", "succeeded", "canceled", "expired"]
+    status: Literal["requested", "authorized", "succeeded", "canceled", "expired", "declined"]
     """Filter by lifecycle status."""

{linq_python-0.16.0 → linq_python-0.18.0}/src/linq/types/phone_number_status_updated_webhook_event.py

@@ -77,6 +77,10 @@ class PhoneNumberStatusUpdatedWebhookEvent(BaseModel):
         "payment.succeeded",
         "payment.canceled",
         "payment.expired",
+        "payment.declined",
+        "payment.authorized",
+        "connection.created",
+        "connection.revoked",
     ]
     """The type of event"""
 

{linq_python-0.16.0 → linq_python-0.18.0}/src/linq/types/webhook_event_type.py

@@ -36,4 +36,8 @@ WebhookEventType: TypeAlias = Literal[
     "payment.succeeded",
     "payment.canceled",
     "payment.expired",
+    "payment.declined",
+    "payment.authorized",
+    "connection.created",
+    "connection.revoked",
 ]

{linq_python-0.16.0 → linq_python-0.18.0}/uv.lock

@@ -530,7 +530,7 @@ wheels = [
 
 [[package]]
 name = "linq-python"
-version = "0.15.1"
+version = "0.17.0"
 source = { editable = "." }
 dependencies = [
     { name = "anyio" },

linq_python-0.16.0/.release-please-manifest.json

@@ -1,3 +0,0 @@
-{
-  ".": "0.16.0"
-}