planvortex 0.13.0__tar.gz → 0.14.0__tar.gz

{planvortex-0.13.0 → planvortex-0.14.0}/CHANGELOG.md

@@ -4,6 +4,33 @@ All notable changes to this package are documented here. The format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.14.0] - 2026-10-07
+
+### Added
+
+- **LinkedIn personal profiles.** Connecting LinkedIn now returns the personal profile of whoever
+  authorizes as well as the pages they manage, and the profile can be enabled like any other
+  account. It publishes in that person's name and has statistics, but **no comment inbox**:
+  LinkedIn does not let any app read the comments on a member's posts, so every `comments` call on
+  a profile raises error 2600. `Account` now types `extra_data["is_personal_profile"]` (`True` on
+  the profile, `False` on a page, absent on pages connected before profiles existed), and
+  `accounts.list(..., capability="comments")` leaves profiles out.
+- **`visibility` and `made_for_kids` on publications**, today on YouTube only: who can see the
+  video when it goes out (`public`, `unlisted` or `private`; absent is `public`) and whether it
+  is made for kids (COPPA; absent is `false`). Both are typed on `PublicationInput` and on
+  `Publication`. They are the user's choice, so ask them if your software publishes for someone. A
+  value the network does not take does not fail the request: the publication is created in
+  `withErrors` with code 2500 (visibility) or 2501 (not a boolean). On every other network the
+  fields are deleted on save; ask `catalog.social_capabilities()` for `visibility` and
+  `made_for_kids` rather than checking for YouTube.
+- **`publication_warnings` on `Publication`**: what still has to be done by hand on the network
+  for a publication that did go out. Same shape as `publication_errors`, but it is not a failure:
+  the publication stays `sended` and **must not be retried**, or it goes out twice. Today the only
+  code is 2400: YouTube accepted the video but left it as a draft or private, and `data.studio_url`
+  is the YouTube Studio page where it is finished.
+- Error 2600 is raised as a `PublicationError`, the same class as 945 ("this network has no
+  comments"), of which it is the per-account version. It used to fall back to the base class.
+
 ## [0.13.0] - 2026-10-03
 
 ### Added

{planvortex-0.13.0 → planvortex-0.14.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: planvortex
-Version: 0.13.0
+Version: 0.14.0
 Summary: Official Python client for the PlanVortex API
 Project-URL: Homepage, https://planvortex.com/en/developers
 Project-URL: Documentation, https://taliasoftworks.github.io/PlanVortexPython/
@@ -280,7 +280,7 @@ memorising numbers:
 | 601-612 | `user` | `UserError` |
 | 700-716 | `account` | `AccountError` |
 | 800-810 | `file` | `FileError` |
-| 900-996 | `publication` | `PublicationError` |
+| 900-996, 2600-2699 | `publication` | `PublicationError` |
 | 1000-1003 | `general` | `PlanVortexError` |
 | 1100-1111 | `organization` | `OrganizationError` |
 | 1200-1207 | `role` | `PlanVortexError` |

{planvortex-0.13.0 → planvortex-0.14.0}/README.md

@@ -250,7 +250,7 @@ memorising numbers:
 | 601-612 | `user` | `UserError` |
 | 700-716 | `account` | `AccountError` |
 | 800-810 | `file` | `FileError` |
-| 900-996 | `publication` | `PublicationError` |
+| 900-996, 2600-2699 | `publication` | `PublicationError` |
 | 1000-1003 | `general` | `PlanVortexError` |
 | 1100-1111 | `organization` | `OrganizationError` |
 | 1200-1207 | `role` | `PlanVortexError` |

{planvortex-0.13.0 → planvortex-0.14.0}/openapi/planvortex.openapi.json

@@ -273,7 +273,7 @@
           {
             "name": "capability",
             "in": "query",
-            "description": "Only accounts whose network can do this. It is the same matrix `GET /social_capabilities` publishes, applied server-side: the way to ask for 'the accounts I can publish with' without keeping your own table of which network does what.",
+            "description": "Only accounts whose network can do this. It is the same matrix `GET /social_capabilities` publishes, applied server-side: the way to ask for 'the accounts I can publish with' without keeping your own table of which network does what.\n\n`comments` also looks at each account, not only at its network: a LinkedIn **personal profile** is left out, because only LinkedIn pages have a comment inbox. `total` counts the same way.",
             "required": false,
             "explode": true,
             "schema": {
@@ -5627,7 +5627,9 @@
                     "comments": true,
                     "destinations": false,
                     "link": false,
-                    "reply_control": false
+                    "reply_control": false,
+                    "visibility": false,
+                    "made_for_kids": false
                   },
                   "google_business": {
                     "publications": false,
@@ -5638,7 +5640,9 @@
                     "comments": true,
                     "destinations": false,
                     "link": false,
-                    "reply_control": false
+                    "reply_control": false,
+                    "visibility": false,
+                    "made_for_kids": false
                   },
                   "pinterest": {
                     "publications": true,
@@ -5649,7 +5653,9 @@
                     "comments": false,
                     "destinations": true,
                     "link": true,
-                    "reply_control": false
+                    "reply_control": false,
+                    "visibility": false,
+                    "made_for_kids": false
                   },
                   "threads": {
                     "publications": true,
@@ -5660,7 +5666,9 @@
                     "comments": true,
                     "destinations": false,
                     "link": false,
-                    "reply_control": true
+                    "reply_control": true,
+                    "visibility": false,
+                    "made_for_kids": false
                   }
                 }
               }
@@ -12602,7 +12610,7 @@
     "schemas": {
       "Account": {
         "type": "object",
-        "description": "A social account connected to an organization.\n\nOn `discord`, on `telegram` and on `slack` an account is a **channel**, not a profile: publishing to two Discord channels of the same server — or to two Telegram channels of the same brand, or to `#anuncios` and `#general` of the same Slack workspace — costs two accounts of the plan.\n\n`error_code` other than `0` means the connection is broken — an expired token, a permission taken away — and the account has to be connected again. On `telegram` nothing expires, because there is no account token: what breaks the connection is the bot being removed from the channel or losing its permission to post there (error 968). On `slack` the bot token does not expire either: what breaks it is the app being removed from the channel (error 980) or the channel being archived or deleted (error 985).",
+        "description": "A social account connected to an organization.\n\nOn `discord`, on `telegram` and on `slack` an account is a **channel**, not a profile: publishing to two Discord channels of the same server — or to two Telegram channels of the same brand, or to `#anuncios` and `#general` of the same Slack workspace — costs two accounts of the plan.\n\nOn `linkedin` one authorization brings two kinds of account: the **personal profile** of whoever authorizes and each **page** they manage. Both publish and both have statistics, but only pages have a comment inbox: LinkedIn does not let any app read the comments on a member's posts, so on a profile every comment endpoint returns error `2600`. `extra_data.is_personal_profile` tells them apart.\n\n`error_code` other than `0` means the connection is broken — an expired token, a permission taken away — and the account has to be connected again. On `telegram` nothing expires, because there is no account token: what breaks the connection is the bot being removed from the channel or losing its permission to post there (error 968). On `slack` the bot token does not expire either: what breaks it is the app being removed from the channel (error 980) or the channel being archived or deleted (error 985).",
         "required": [
           "_id",
           "id_organization",
@@ -12668,6 +12676,17 @@
           "private_message_link": {
             "type": "string",
             "description": "A link that opens a private chat with this account (`m.me`, `ig.me`, `wa.me`). Absent on every other network."
+          },
+          "extra_data": {
+            "type": "object",
+            "description": "What only makes sense on this account's network. Only the keys documented here are part of the contract: anything else in the object can change without notice.",
+            "properties": {
+              "is_personal_profile": {
+                "type": "boolean",
+                "description": "`linkedin` only. `true` on the personal profile of whoever authorized, `false` on a page. A profile publishes and has statistics but no comment inbox (error `2600`). Pages connected before personal profiles existed do not carry it, so treat absent as a page."
+              }
+            },
+            "additionalProperties": true
           }
         }
       },
@@ -15259,6 +15278,14 @@
           "reply_control": {
             "type": "boolean",
             "description": "The publication can say **who can reply** to it (`reply_control`): anyone, the account's followers, the profiles it follows or the profiles mentioned in the text. It is set when the publication goes out and cannot be changed afterwards. On a network that answers `false` the field is deleted on save, so do not offer it. Today only `threads`."
+          },
+          "visibility": {
+            "type": "boolean",
+            "description": "The publication can say **who can see it** when it goes out (`visibility`): public, unlisted or private. On a network that answers `false` the field is deleted on save, so do not offer it. Today only `youtube`."
+          },
+          "made_for_kids": {
+            "type": "boolean",
+            "description": "The publication can say whether it is **made for kids** (`made_for_kids`, COPPA). On a network that answers `false` the field is deleted on save, so do not offer it. Today only `youtube`."
           }
         },
         "required": [
@@ -15270,7 +15297,9 @@
           "comments",
           "destinations",
           "link",
-          "reply_control"
+          "reply_control",
+          "visibility",
+          "made_for_kids"
         ]
       },
       "CommentsWebhookChange": {
@@ -15957,6 +15986,29 @@
                 }
               }
             }
+          },
+          "publication_warnings": {
+            "type": "array",
+            "description": "What still has to be done **by hand on the network** for a publication that DID go out. Same shape as `publication_errors`, and an empty array when there is nothing to do.\n\nIt is a separate field because these are not failures: the publication stays in state `sended` and must **not** be retried, because retrying would publish it twice. Like `publication_errors`, it belongs to the last attempt.\n\nToday there is one code. **2400** (YouTube): YouTube accepted the upload but did not make the video public, so YouTube Studio shows it as a draft or private until someone sets its audience and visibility there. The upload does not fail when this happens; PlanVortex reads the video back right after uploading it to find out. `data` carries `requested_privacy_status`, `privacy_status` (what YouTube actually left), `upload_status`, `made_for_kids` and `studio_url`, the YouTube Studio page where it is finished.",
+            "items": {
+              "type": "object",
+              "required": [
+                "code",
+                "message"
+              ],
+              "properties": {
+                "code": {
+                  "type": "integer"
+                },
+                "message": {
+                  "type": "string"
+                },
+                "data": {
+                  "type": "object",
+                  "additionalProperties": true
+                }
+              }
+            }
           }
         }
       },
@@ -16221,7 +16273,7 @@
           },
           "code": {
             "type": "integer",
-            "description": "PlanVortex error code. Ranges: 500-554 auth, tokens, client apps and connect sessions · 601-612 user · 700-716 social accounts · 800-810 files · 900-996 publications · 1000-1003 general · 1100-1111 organizations · 1200-1207 roles · 1300-1308 client plan · 1400-1408 organization plan · 1500-1512 messaging · 1600-1601 contacts · 1900-1906 payments · 2000-2099 products · 2100-2199 AI plans · 2200-2299 integrations."
+            "description": "PlanVortex error code. Ranges: 500-554 auth, tokens, client apps and connect sessions · 601-612 user · 700-716 social accounts · 800-810 files · 900-996 publications · 1000-1003 general · 1100-1111 organizations · 1200-1207 roles · 1300-1308 client plan · 1400-1408 organization plan · 1500-1512 messaging · 1600-1601 contacts · 1900-1906 payments · 2000-2099 products · 2100-2199 AI plans · 2200-2299 integrations · 2600-2699 comments, the ones that no longer fit in 945-948."
           },
           "data": {
             "additionalProperties": true,
@@ -17792,6 +17844,19 @@
             ],
             "description": "**Who can reply** to the publication, on the networks that answer `reply_control: true` in `GET /social_capabilities` (today `threads`). Absent means the network's default, which is anyone. It is set when the publication goes out and cannot be changed afterwards.\n\n**On every other network the field is deleted on save**, like `link`."
           },
+          "visibility": {
+            "type": "string",
+            "enum": [
+              "public",
+              "unlisted",
+              "private"
+            ],
+            "description": "**Who can see the publication** when it goes out, on the networks that answer `visibility: true` in `GET /social_capabilities` (today `youtube`). Absent means `public`. It is set when the publication goes out.\n\n**On every other network the field is deleted on save**, like `reply_control`."
+          },
+          "made_for_kids": {
+            "type": "boolean",
+            "description": "Whether the video is **made for kids** (COPPA), on the networks that answer `made_for_kids: true` in `GET /social_capabilities` (today `youtube`). Absent means `false`.\n\n**On every other network the field is deleted on save**, like `reply_control`."
+          },
           "publication_type": {
             "type": "string",
             "enum": [
@@ -17855,6 +17920,29 @@
               }
             }
           },
+          "publication_warnings": {
+            "type": "array",
+            "description": "What still has to be done **by hand on the network** for a publication that DID go out. Same shape as `publication_errors`, and an empty array when there is nothing to do.\n\nIt is a separate field because these are not failures: the publication stays in state `sended` and must **not** be retried, because retrying would publish it twice. Like `publication_errors`, it belongs to the last attempt.\n\nToday there is one code. **2400** (YouTube): YouTube accepted the upload but did not make the video public, so YouTube Studio shows it as a draft or private until someone sets its audience and visibility there. The upload does not fail when this happens; PlanVortex reads the video back right after uploading it to find out. `data` carries `requested_privacy_status`, `privacy_status` (what YouTube actually left), `upload_status`, `made_for_kids` and `studio_url`, the YouTube Studio page where it is finished.",
+            "items": {
+              "type": "object",
+              "required": [
+                "code",
+                "message"
+              ],
+              "properties": {
+                "code": {
+                  "type": "integer"
+                },
+                "message": {
+                  "type": "string"
+                },
+                "data": {
+                  "type": "object",
+                  "additionalProperties": true
+                }
+              }
+            }
+          },
           "retries": {
             "type": "integer",
             "description": "Manual retries already spent on a failed publication, against the `max_retries` published by `GET /publication_limits`. Only `POST .../retry` increases it; updating the publication resets it to 0."
@@ -18216,6 +18304,19 @@
             ],
             "description": "**Who can reply** to the publication. Only on the networks that answer `reply_control: true` in `GET /social_capabilities` (today `threads`), and **deleted** on every other one.\n\n- `everyone`: anyone. It is the network's default, and what applies when the field is omitted.\n- `followers_only`: only the account's followers.\n- `accounts_you_follow`: only the profiles the account follows.\n- `mentioned_only`: only the profiles mentioned in the text.\n\n**It is set when the publication goes out and cannot be changed afterwards**: Threads has no way to change it on a published post through its API. A value the network does not accept does not fail the request: the publication is still created, in state `withErrors` with `publication_errors[].code = 997`, whose `data` carries the `allowed` values. It is checked when the publication is **created**, so a scheduled post does not fail at 3 a.m. over a value that was already wrong.\n\nOn an update: omit it to keep what was there, send `null` or `\"\"` to go back to the network's default."
           },
+          "visibility": {
+            "type": "string",
+            "enum": [
+              "public",
+              "unlisted",
+              "private"
+            ],
+            "description": "**Who can see the publication** when it goes out. Only on the networks that answer `visibility: true` in `GET /social_capabilities` (today `youtube`), and **deleted** on every other one.\n\n- `public`: anyone. It is what applies when the field is omitted.\n- `unlisted`: only people with the link. It does not show on the channel or in search.\n- `private`: only the channel owner and the people they invite from YouTube Studio.\n\nYouTube's policies require this to be **the user's choice**: if your software publishes on behalf of someone, ask them. A value the network does not accept does not fail the request: the publication is still created, in state `withErrors` with `publication_errors[].code = 2500`, whose `data` carries the `allowed` values. It is checked when the publication is **created**, so a scheduled video does not fail at 3 a.m. over a value that was already wrong.\n\nIf YouTube does not leave the video with the visibility that was asked for, the publication still ends up `sended` (the video is on the channel) and carries a warning in `publication_warnings` with `code = 2400`.\n\nOn an update: omit it to keep what was there, send `null` or `\"\"` to go back to `public`."
+          },
+          "made_for_kids": {
+            "type": "boolean",
+            "description": "Whether the video is **made for kids**. Only on the networks that answer `made_for_kids: true` in `GET /social_capabilities` (today `youtube`), and **deleted** on every other one. Absent means `false`.\n\nThe law (COPPA) and YouTube's policies require a video directed at children to be uploaded with `true`, and it is the **user's** call: if your software publishes on behalf of someone, ask them. YouTube then turns off features such as comments and personalised ads on that video.\n\nIt must be a JSON boolean. Anything else (`\"yes\"`, `\"no\"`, `1`) is not guessed: the publication is still created, in state `withErrors` with `publication_errors[].code = 2501`.\n\nOn an update: omit it to keep what was there, send `null` or `\"\"` to go back to `false`."
+          },
           "files": {
             "type": "array",
             "description": "Identifiers of uploads previously created through the uploads endpoints, attached to this publication.\n\n**On Slack the files travel inside the message**, not as publications of their own: up to 10 attachments counting images and videos together (`publication_errors[].code = 982` over it), each one under the `max_file_size_mb.slack` ceiling (code 983), and anything the upload itself refuses comes back as code 986.\n\n**On Pinterest a pin is an image or a video, never text alone** (code 922 with neither), and it is of one kind only: two to five images make a carousel — outside that range, code 990 — images and videos are not mixed and there is no more than one video (code 916). The weight ceilings are two orders of magnitude apart, so `max_file_size_mb.pinterest` is the **image** one (~20 MB) while a video is allowed far more; over either, code 996 with `data.max_mb`.",
@@ -19130,7 +19231,7 @@
         }
       },
       "CommentsCommentError": {
-        "description": "The request failed. The body carries the PlanVortex error code in `code`:\n\n| Code | Meaning |\n| --- | --- |\n| `516` | Comments require a paid plan. Every endpoint here returns this on the free plan. |\n| `700` | The account is not connected — no valid token, or nothing to ask the network about. |\n| `936` | The publication was never sent, so it has no thread to read. |\n| `940` | The client's monthly X credits are exhausted. Only X. |\n| `945` | This network has no comments (TikTok, WhatsApp). Carries `social_network` in `data`. |\n| `946` | The network has comments but does not allow **this action**: hiding on LinkedIn or Google Business, deleting someone else's on Instagram or X, deleting a review. Carries `social_network` and `action` in `data`. See `GET /social_comment_actions`. |\n| `947` | The comment no longer exists on the network. What is stored is a photograph; the network always wins. Carries `external_id` in `data`. |\n| `948` | The reply is empty or longer than the network allows. Carries the limit in `data.max`; the same number is published in `comment_characters` of `GET /social_limits`. |\n| `951` | The Google Business listing is not verified, so it cannot reply to its reviews. It is the state of the customer's profile, not of your token. |\n| `952` | PlanVortex's Google Cloud project has no approved access to the Google Business API yet. Until it does, reviews cannot be read or replied to. |\n| `965` | This Telegram channel has no linked discussion group, so it has no comments. The network gate says `true`; what is missing is a setting of **that channel**, which its owner fixes in two taps. Carries `chat_id` in `data`. |\n| `969` | The PlanVortex bot is not allowed to delete messages in this Telegram discussion group. The network allows it; this installation does not. Carries `chat_id` in `data`. |\n| `970` | Telegram is rate limiting the bot and the wait was longer than PlanVortex is willing to hold the request for. Carries `retry_after_seconds` in `data`: retry after it. |\n| `1101` | Invalid organization. |\n| `1501` | The comment's account could not be resolved. |",
+        "description": "The request failed. The body carries the PlanVortex error code in `code`:\n\n| Code | Meaning |\n| --- | --- |\n| `516` | Comments require a paid plan. Every endpoint here returns this on the free plan. |\n| `700` | The account is not connected — no valid token, or nothing to ask the network about. |\n| `936` | The publication was never sent, so it has no thread to read. |\n| `940` | The client's monthly X credits are exhausted. Only X. |\n| `945` | This network has no comments (TikTok, WhatsApp). Carries `social_network` in `data`. |\n| `946` | The network has comments but does not allow **this action**: hiding on LinkedIn or Google Business, deleting someone else's on Instagram or X, deleting a review. Carries `social_network` and `action` in `data`. See `GET /social_comment_actions`. |\n| `947` | The comment no longer exists on the network. What is stored is a photograph; the network always wins. Carries `external_id` in `data`. |\n| `948` | The reply is empty or longer than the network allows. Carries the limit in `data.max`; the same number is published in `comment_characters` of `GET /social_limits`. |\n| `951` | The Google Business listing is not verified, so it cannot reply to its reviews. It is the state of the customer's profile, not of your token. |\n| `952` | PlanVortex's Google Cloud project has no approved access to the Google Business API yet. Until it does, reviews cannot be read or replied to. |\n| `965` | This Telegram channel has no linked discussion group, so it has no comments. The network gate says `true`; what is missing is a setting of **that channel**, which its owner fixes in two taps. Carries `chat_id` in `data`. |\n| `969` | The PlanVortex bot is not allowed to delete messages in this Telegram discussion group. The network allows it; this installation does not. Carries `chat_id` in `data`. |\n| `970` | Telegram is rate limiting the bot and the wait was longer than PlanVortex is willing to hold the request for. Carries `retry_after_seconds` in `data`: retry after it. |\n| `1101` | Invalid organization. |\n| `1501` | The comment's account could not be resolved. |\n| `2600` | The network has comments but **this account** has none: a LinkedIn personal profile. LinkedIn does not let any app read a member's comments, so only pages have an inbox. Carries `social_network` and `id_account` in `data`. |",
         "content": {
           "application/json": {
             "schema": {

{planvortex-0.13.0 → planvortex-0.14.0}/pyproject.toml

@@ -9,7 +9,7 @@ name = "planvortex"
 # entonces `project.version` desapareceria del pyproject y el paso del workflow de release que
 # compara el tag con la version —que lo lee con `tomllib`— dejaria de encontrarla. Se quedan las dos
 # y las ata `tests/test_packaging.py`, que falla si se separan.
-version = "0.13.0"
+version = "0.14.0"
 description = "Official Python client for the PlanVortex API"
 readme = "README.md"
 requires-python = ">=3.10"

{planvortex-0.13.0 → planvortex-0.14.0}/src/planvortex/_core/errors.py

@@ -56,6 +56,10 @@ PLANVORTEX_ERROR_RANGES: tuple[ErrorRange, ...] = (
     ErrorRange(2000, 2099, "product"),
     ErrorRange(2100, 2199, "ai_plan"),
     ErrorRange(2200, 2299, "integration"),
+    # Los COMENTARIOS siguen aqui porque sus 945-948 se llenaron, y van con ellos a `publication`:
+    # el 2600 (esta cuenta no tiene bandeja, un perfil personal de LinkedIn) es la version por
+    # cuenta del 945, y separarlos daria dos clases para el mismo «aqui no hay comentarios».
+    ErrorRange(2600, 2699, "publication"),
 )
 
 # El `code` que lleva un error que NO trae codigo del servidor: un fallo de red, un timeout, un 502
@@ -139,6 +143,10 @@ class PublicationError(PlanVortexError):
     the channel, and Pinterest's (987-996), which start the same way: 987, the publication does not
     say which board it goes to. One of them is not a failure: 991 is Pinterest throttling the
     application, it arrives as a 429 with ``Retry-After`` and the answer is to wait.
+
+    Also 2600-2699, the comment codes that did not fit after 945-948: 2600 is the per-account
+    version of 945, an account with no comment inbox on a network that has one (a LinkedIn
+    personal profile).
     """
 
 

{planvortex-0.13.0 → planvortex-0.14.0}/src/planvortex/_generated/models.py

@@ -17,6 +17,18 @@ if sys.version_info >= (3, 11):
 else:  # pragma: no cover - la rama la elige el interprete, no un test
     from typing_extensions import NotRequired, TypedDict
 
+
+class ExtraData(TypedDict):
+    """
+    What only makes sense on this account's network. Only the keys documented here are part of the contract: anything else in the object can change without notice.
+    """
+
+    is_personal_profile: NotRequired[bool]
+    """
+    `linkedin` only. `true` on the personal profile of whoever authorized, `false` on a page. A profile publishes and has statistics but no comment inbox (error `2600`). Pages connected before personal profiles existed do not carry it, so treat absent as a page.
+    """
+
+
 AccountsMetricList: TypeAlias = list[
     Literal[
         "page_total_actions",
@@ -1003,6 +1015,14 @@ class CommentsSocialCapabilities(TypedDict):
     """
     The publication can say **who can reply** to it (`reply_control`): anyone, the account's followers, the profiles it follows or the profiles mentioned in the text. It is set when the publication goes out and cannot be changed afterwards. On a network that answers `false` the field is deleted on save, so do not offer it. Today only `threads`.
     """
+    visibility: bool
+    """
+    The publication can say **who can see it** when it goes out (`visibility`): public, unlisted or private. On a network that answers `false` the field is deleted on save, so do not offer it. Today only `youtube`.
+    """
+    made_for_kids: bool
+    """
+    The publication can say whether it is **made for kids** (`made_for_kids`, COPPA). On a network that answers `false` the field is deleted on save, so do not offer it. Today only `youtube`.
+    """
 
 
 ContactChannel: TypeAlias = Literal[
@@ -1123,6 +1143,12 @@ class PublicationError(TypedDict):
     data: NotRequired[dict[str, Any]]
 
 
+class PublicationWarning(TypedDict):
+    code: int
+    message: str
+    data: NotRequired[dict[str, Any]]
+
+
 class DashboardDashboardRange(TypedDict):
     """
     The range that was actually used, plus the previous period of exactly the same length. The previous one is not "last month": comparing 30 days against a calendar month would move the delta with the calendar.
@@ -1186,7 +1212,7 @@ class Error1(TypedDict):
     """
     code: int
     """
-    PlanVortex error code. Ranges: 500-554 auth, tokens, client apps and connect sessions · 601-612 user · 700-716 social accounts · 800-810 files · 900-996 publications · 1000-1003 general · 1100-1111 organizations · 1200-1207 roles · 1300-1308 client plan · 1400-1408 organization plan · 1500-1512 messaging · 1600-1601 contacts · 1900-1906 payments · 2000-2099 products · 2100-2199 AI plans · 2200-2299 integrations.
+    PlanVortex error code. Ranges: 500-554 auth, tokens, client apps and connect sessions · 601-612 user · 700-716 social accounts · 800-810 files · 900-996 publications · 1000-1003 general · 1100-1111 organizations · 1200-1207 roles · 1300-1308 client plan · 1400-1408 organization plan · 1500-1512 messaging · 1600-1601 contacts · 1900-1906 payments · 2000-2099 products · 2100-2199 AI plans · 2200-2299 integrations · 2600-2699 comments, the ones that no longer fit in 945-948.
     """
     data: NotRequired[dict[str, Any]]
     """
@@ -2172,6 +2198,30 @@ class PublicationsPublicationInput(TypedDict):
 
     On an update: omit it to keep what was there, send `null` or `""` to go back to the network's default.
     """
+    visibility: NotRequired[Literal["public", "unlisted", "private"]]
+    """
+    **Who can see the publication** when it goes out. Only on the networks that answer `visibility: true` in `GET /social_capabilities` (today `youtube`), and **deleted** on every other one.
+
+    - `public`: anyone. It is what applies when the field is omitted.
+    - `unlisted`: only people with the link. It does not show on the channel or in search.
+    - `private`: only the channel owner and the people they invite from YouTube Studio.
+
+    YouTube's policies require this to be **the user's choice**: if your software publishes on behalf of someone, ask them. A value the network does not accept does not fail the request: the publication is still created, in state `withErrors` with `publication_errors[].code = 2500`, whose `data` carries the `allowed` values. It is checked when the publication is **created**, so a scheduled video does not fail at 3 a.m. over a value that was already wrong.
+
+    If YouTube does not leave the video with the visibility that was asked for, the publication still ends up `sended` (the video is on the channel) and carries a warning in `publication_warnings` with `code = 2400`.
+
+    On an update: omit it to keep what was there, send `null` or `""` to go back to `public`.
+    """
+    made_for_kids: NotRequired[bool]
+    """
+    Whether the video is **made for kids**. Only on the networks that answer `made_for_kids: true` in `GET /social_capabilities` (today `youtube`), and **deleted** on every other one. Absent means `false`.
+
+    The law (COPPA) and YouTube's policies require a video directed at children to be uploaded with `true`, and it is the **user's** call: if your software publishes on behalf of someone, ask them. YouTube then turns off features such as comments and personalised ads on that video.
+
+    It must be a JSON boolean. Anything else (`"yes"`, `"no"`, `1`) is not guessed: the publication is still created, in state `withErrors` with `publication_errors[].code = 2501`.
+
+    On an update: omit it to keep what was there, send `null` or `""` to go back to `false`.
+    """
     files: NotRequired[list[str]]
     """
     Identifiers of uploads previously created through the uploads endpoints, attached to this publication.
@@ -2399,6 +2449,8 @@ class Account(TypedDict):
 
     On `discord`, on `telegram` and on `slack` an account is a **channel**, not a profile: publishing to two Discord channels of the same server — or to two Telegram channels of the same brand, or to `#anuncios` and `#general` of the same Slack workspace — costs two accounts of the plan.
 
+    On `linkedin` one authorization brings two kinds of account: the **personal profile** of whoever authorizes and each **page** they manage. Both publish and both have statistics, but only pages have a comment inbox: LinkedIn does not let any app read the comments on a member's posts, so on a profile every comment endpoint returns error `2600`. `extra_data.is_personal_profile` tells them apart.
+
     `error_code` other than `0` means the connection is broken — an expired token, a permission taken away — and the account has to be connected again. On `telegram` nothing expires, because there is no account token: what breaks the connection is the bot being removed from the channel or losing its permission to post there (error 968). On `slack` the bot token does not expire either: what breaks it is the app being removed from the channel (error 980) or the channel being archived or deleted (error 985).
     """
 
@@ -2445,6 +2497,10 @@ class Account(TypedDict):
     """
     A link that opens a private chat with this account (`m.me`, `ig.me`, `wa.me`). Absent on every other network.
     """
+    extra_data: NotRequired[ExtraData]
+    """
+    What only makes sense on this account's network. Only the keys documented here are part of the contract: anything else in the object can change without notice.
+    """
 
 
 class AccountsAccountList(TypedDict):
@@ -2993,6 +3049,14 @@ class DashboardDashboardPublicationRef(TypedDict):
     """
     Only on the failed ones. Same shape as in a full `Publication`.
     """
+    publication_warnings: NotRequired[list[PublicationWarning]]
+    """
+    What still has to be done **by hand on the network** for a publication that DID go out. Same shape as `publication_errors`, and an empty array when there is nothing to do.
+
+    It is a separate field because these are not failures: the publication stays in state `sended` and must **not** be retried, because retrying would publish it twice. Like `publication_errors`, it belongs to the last attempt.
+
+    Today there is one code. **2400** (YouTube): YouTube accepted the upload but did not make the video public, so YouTube Studio shows it as a draft or private until someone sets its audience and visibility there. The upload does not fail when this happens; PlanVortex reads the video back right after uploading it to find out. `data` carries `requested_privacy_status`, `privacy_status` (what YouTube actually left), `upload_status`, `made_for_kids` and `studio_url`, the YouTube Studio page where it is finished.
+    """
 
 
 class DashboardPlanUse(TypedDict):
@@ -3375,6 +3439,18 @@ class Publication(TypedDict):
 
     **On every other network the field is deleted on save**, like `link`.
     """
+    visibility: NotRequired[Literal["public", "unlisted", "private"]]
+    """
+    **Who can see the publication** when it goes out, on the networks that answer `visibility: true` in `GET /social_capabilities` (today `youtube`). Absent means `public`. It is set when the publication goes out.
+
+    **On every other network the field is deleted on save**, like `reply_control`.
+    """
+    made_for_kids: NotRequired[bool]
+    """
+    Whether the video is **made for kids** (COPPA), on the networks that answer `made_for_kids: true` in `GET /social_capabilities` (today `youtube`). Absent means `false`.
+
+    **On every other network the field is deleted on save**, like `reply_control`.
+    """
     publication_type: Literal["profile", "page", "group", "reels", "stories", "message"]
     state: Literal["ready", "withErrors", "sended", "draft", "publishing"]
     """
@@ -3397,6 +3473,14 @@ class Publication(TypedDict):
 
     On Instagram, two codes tell you whether a retry makes sense. **998**: Meta rejected the media while processing it (a codec, a duration, a URL it could not download). `data` carries `container_id`, `status_code` and, when Meta gives one, its reason in `status`. Retrying the same file fails the same way: change it first. **999**: Meta had not finished processing the media 10 minutes after it was sent. `data` carries `container_ids` and `minutes`. The file is not the problem, and a retry usually works.
     """
+    publication_warnings: NotRequired[list[PublicationWarning]]
+    """
+    What still has to be done **by hand on the network** for a publication that DID go out. Same shape as `publication_errors`, and an empty array when there is nothing to do.
+
+    It is a separate field because these are not failures: the publication stays in state `sended` and must **not** be retried, because retrying would publish it twice. Like `publication_errors`, it belongs to the last attempt.
+
+    Today there is one code. **2400** (YouTube): YouTube accepted the upload but did not make the video public, so YouTube Studio shows it as a draft or private until someone sets its audience and visibility there. The upload does not fail when this happens; PlanVortex reads the video back right after uploading it to find out. `data` carries `requested_privacy_status`, `privacy_status` (what YouTube actually left), `upload_status`, `made_for_kids` and `studio_url`, the YouTube Studio page where it is finished.
+    """
     retries: int
     """
     Manual retries already spent on a failed publication, against the `max_retries` published by `GET /publication_limits`. Only `POST .../retry` increases it; updating the publication resets it to 0.

{planvortex-0.13.0 → planvortex-0.14.0}/src/planvortex/_shapes.py

@@ -347,6 +347,18 @@ class PublicationInput(TypedDict):
     ``catalog.social_capabilities()`` (today Threads). Omitted, the network's default: anyone. It is
     set when the publication goes out and cannot be changed afterwards; on every other network the
     field is deleted on save."""
+    visibility: NotRequired[Literal["public", "unlisted", "private"]]
+    """**Who can see the publication** when it goes out, on the networks that answer
+    ``visibility: true`` in ``catalog.social_capabilities()`` (today YouTube). Omitted, ``public``.
+    YouTube's policies require it to be the user's choice: if you publish for someone, ask them. A
+    value the network does not take does not raise: the publication is created in ``withErrors``
+    with code 2500. On every other network the field is deleted on save."""
+    made_for_kids: NotRequired[bool]
+    """Whether the video is **made for kids** (COPPA), on the networks that answer
+    ``made_for_kids: true`` in ``catalog.social_capabilities()`` (today YouTube). Omitted, ``False``.
+    It is the user's call, and it must be a real boolean: anything else is not guessed, and the
+    publication is created in ``withErrors`` with code 2501. On every other network the field is
+    deleted on save."""
     name: NotRequired[str]
     """Internal name, for grouping. Never shown on the network."""
     publication_type: NotRequired[Literal["profile", "page", "group", "reels", "stories"]]

{planvortex-0.13.0 → planvortex-0.14.0}/src/planvortex/_version.py

@@ -12,7 +12,7 @@ from __future__ import annotations
 
 import platform
 
-VERSION = "0.13.0"
+VERSION = "0.14.0"
 
 # Sin barra final, y con el `/v1.0.0` dentro: la version de la API es parte de la ruta, no una
 # cabecera, asi que una `base_url` sin ella da 404 en todo.

{planvortex-0.13.0 → planvortex-0.14.0}/src/planvortex/resources/accounts.py

@@ -181,7 +181,9 @@ class AsyncAccountsResource(AsyncResource):
         ``capability`` filters by what the account's network can do — ``publications``, ``messages``,
         ``products``, ``webhooks``, ``persistent_menu``, ``comments`` — applied on the server with
         the same matrix ``catalog.social_capabilities()`` publishes. It is how you ask for "the
-        accounts I can publish with" without keeping a table of your own.
+        accounts I can publish with" without keeping a table of your own. ``comments`` also looks
+        at each account: it leaves out LinkedIn personal profiles, which have no inbox although
+        LinkedIn pages do.
         """
         pagina: Page[Account] = await self._list(
             f"{self._organization_path(id_organization)}/accounts",

{planvortex-0.13.0 → planvortex-0.14.0}/src/planvortex/resources/comments.py

@@ -16,6 +16,10 @@ WHAT TO KNOW BEFORE CALLING ANYTHING HERE:
   :meth:`AsyncCommentsResource.actions`: Instagram, X and Bluesky do not let you delete somebody
   else's, LinkedIn has no "hide" (neither do Discord and Telegram), and Google Business only lets
   you delete **your own reply**.
+- **Nor every ACCOUNT.** A LinkedIn personal profile publishes but has no inbox: LinkedIn does not
+  let any app read the comments on a profile, only on a page. Everything here raises error 2600 on
+  one. Check ``account.get("extra_data", {}).get("is_personal_profile")`` first, or list the accounts with
+  ``capability="comments"``, which already leaves them out.
 - **On Telegram the inbox starts the day the channel was connected.** The Bot API cannot read the
   past: a bot only learns what happens while it is inside, so nothing written before the connection
   exists here and never will. Say so in your interface — an inbox that opens empty on a busy channel

{planvortex-0.13.0 → planvortex-0.14.0}/src/planvortex/resources_sync/accounts.py

@@ -172,7 +172,9 @@ class AccountsResource(Resource):
         ``capability`` filters by what the account's network can do — ``publications``, ``messages``,
         ``products``, ``webhooks``, ``persistent_menu``, ``comments`` — applied on the server with
         the same matrix ``catalog.social_capabilities()`` publishes. It is how you ask for "the
-        accounts I can publish with" without keeping a table of your own.
+        accounts I can publish with" without keeping a table of your own. ``comments`` also looks
+        at each account: it leaves out LinkedIn personal profiles, which have no inbox although
+        LinkedIn pages do.
         """
         pagina: Page[Account] = self._list(
             f"{self._organization_path(id_organization)}/accounts",

{planvortex-0.13.0 → planvortex-0.14.0}/src/planvortex/types.py

@@ -481,6 +481,12 @@ Account: TypeAlias = _models.Account
 On Discord an account is a **channel**, not a profile: publishing to two channels of the same server
 spends two accounts of the plan. ``error_code`` other than ``0`` means the connection broke — expired
 token, permission taken away — and it has to be connected again.
+
+On LinkedIn one authorization brings two kinds of account: the **personal profile** of whoever
+authorizes and each **page** they manage. Both publish and have statistics, but only pages have a
+comment inbox: LinkedIn does not let any app read the comments on a personal profile, so every
+``comments`` call on one raises error 2600. Tell them apart with ``extra_data["is_personal_profile"]``;
+absent means a page (those connected before profiles existed).
 """
 
 AccountMetrics: TypeAlias = _models.AccountsMetricModel

{planvortex-0.13.0 → planvortex-0.14.0}/tests/test_core.py

@@ -355,6 +355,11 @@ def test_cada_rango_del_catalogo_cae_en_su_clase() -> None:
     assert error_class_for_code(546).__name__ == "AuthError"
     assert error_class_for_code(1408).__name__ == "PlanLimitError"
     assert error_class_for_code(2299).__name__ == "IntegrationError"
+    # Los comentarios que no cupieron en 945-948. El 2600 es la version por CUENTA del 945 (un
+    # perfil personal de LinkedIn no tiene bandeja) y sale con la misma clase que el.
+    assert error_class_for_code(945).__name__ == "PublicationError"
+    assert error_class_for_code(2600).__name__ == "PublicationError"
+    assert error_class_for_code(2699).__name__ == "PublicationError"
     # Los siete de las plantillas del planificador. No hay nada que registrar para que caigan aqui:
     # entran por el rango 2100-2199, y eso es justo lo que hay que comprobar en vez de suponerlo.
     for codigo in range(2111, 2118):