easydata-api 1.2.0__tar.gz → 1.4.0__tar.gz

{easydata_api-1.2.0 → easydata_api-1.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: easydata-api
-Version: 1.2.0
+Version: 1.4.0
 Summary: Official Python client for the EasyData LinkedIn enrichment API
 Author-email: EasyData Development <dev@easydata.win>
 License-Expression: MIT
@@ -191,10 +191,22 @@ ed.account()                                        # allowance, ceilings, secre
 ed.usage(from_="2026-09-01", to="2026-09-30")       # spend by day and operation
 ```
 
-Operations are attributes: `profiles_enrich`, `profiles_activity`,
-`profiles_posts`, `profiles_comments`, `profiles_reactions`, `companies_enrich`,
-`posts_enrich`, `sales_search_people`, `sales_search_employees`,
-`sales_search_companies`.
+Operations are attributes: `profiles_enrich`, `profiles_enrich_detailed`,
+`profiles_activity`, `profiles_posts`, `profiles_comments`,
+`profiles_reactions`, `companies_enrich`, `posts_enrich`,
+`sales_search_people`, `sales_search_employees`, `sales_search_companies`.
+
+`profiles_enrich_detailed` is `profiles_enrich` plus the optional sections -
+`include_counts=True` for follower and connection counts,
+`include_experience_detail=True` for what each role actually says,
+`include_skill_details=True` for endorsement counts, `include_interests=True`
+for what the person follows, and `include_recommendations=True` for written
+recommendations in both directions. Each is one more request to LinkedIn and
+costs +0.5 per target, charged only when the section answered, and at least one
+of them is required.
+
+The three list sections come back in three states: absent when you did not ask,
+`[]` when you did and the member has none, and populated otherwise.
 
 ## Reference
 

{easydata_api-1.2.0 → easydata_api-1.4.0}/README.md

@@ -170,10 +170,22 @@ ed.account()                                        # allowance, ceilings, secre
 ed.usage(from_="2026-09-01", to="2026-09-30")       # spend by day and operation
 ```
 
-Operations are attributes: `profiles_enrich`, `profiles_activity`,
-`profiles_posts`, `profiles_comments`, `profiles_reactions`, `companies_enrich`,
-`posts_enrich`, `sales_search_people`, `sales_search_employees`,
-`sales_search_companies`.
+Operations are attributes: `profiles_enrich`, `profiles_enrich_detailed`,
+`profiles_activity`, `profiles_posts`, `profiles_comments`,
+`profiles_reactions`, `companies_enrich`, `posts_enrich`,
+`sales_search_people`, `sales_search_employees`, `sales_search_companies`.
+
+`profiles_enrich_detailed` is `profiles_enrich` plus the optional sections -
+`include_counts=True` for follower and connection counts,
+`include_experience_detail=True` for what each role actually says,
+`include_skill_details=True` for endorsement counts, `include_interests=True`
+for what the person follows, and `include_recommendations=True` for written
+recommendations in both directions. Each is one more request to LinkedIn and
+costs +0.5 per target, charged only when the section answered, and at least one
+of them is required.
+
+The three list sections come back in three states: absent when you did not ask,
+`[]` when you did and the member has none, and populated otherwise.
 
 ## Reference
 

{easydata_api-1.2.0 → easydata_api-1.4.0}/easydata_api/client.py

@@ -35,11 +35,12 @@ __all__ = [
 DEFAULT_BASE_URL = "https://api.easydata.win/v1"
 
 #: Every operation, as `attribute name -> path`. The client builds one method
-#: per entry rather than defining ten near-identical methods, because they ARE
-#: identical: one request shape, one response shape, and the operation is the
-#: path. A new operation is a row here.
+#: per entry rather than defining one near-identical method per operation,
+#: because they ARE identical: one request shape, one response shape, and the
+#: operation is the path. A new operation is a row here.
 OPERATIONS: dict[str, str] = {
     "profiles_enrich": "/profiles/enrich",
+    "profiles_enrich_detailed": "/profiles/enrich/detailed",
     "profiles_activity": "/profiles/activity",
     "profiles_posts": "/profiles/posts",
     "profiles_comments": "/profiles/comments",
@@ -315,6 +316,11 @@ class EasyData:
         max_results: int | None = None,
         enrich: bool | None = None,
         find_emails: bool | None = None,
+        include_counts: bool | None = None,
+        include_experience_detail: bool | None = None,
+        include_skill_details: bool | None = None,
+        include_interests: bool | None = None,
+        include_recommendations: bool | None = None,
         include_results: bool | None = None,
         idempotency_key: str | None = None,
     ) -> Batch:
@@ -322,6 +328,22 @@ class EasyData:
 
         A batch of one is a batch. There is no separate single-target path and
         no ceiling to discover between one target and fifty thousand.
+
+        With ``find_emails`` the addresses are looked up after the scraping, so
+        results carrying one arrive minutes later than results that do not. Each
+        entry still appears exactly once, complete, and the batch is not
+        ``completed`` until every one has.
+
+        The five ``include_*`` flags are the optional sections of
+        ``profiles_enrich_detailed`` and are refused with a 400 on anything
+        else. Each is one more request to LinkedIn and costs +0.5 per target,
+        charged only when the section actually answered; at least one of them
+        is required on that operation, because with none set it is
+        ``profiles_enrich``, which returns the same record for less.
+
+        ``skill_details``, ``interests`` and ``recommendations`` come back in
+        three states: absent when you did not ask, ``[]`` when you asked and
+        this member has none, and populated otherwise.
         """
         if not targets:
             raise ValueError("targets is empty: a batch needs at least one target")
@@ -329,7 +351,12 @@ class EasyData:
         body: dict[str, Any] = {"targets": list(targets)}
         _put(body, external_id=external_id, callback_url=callback_url,
              webhook_tag=webhook_tag, max_results=max_results, enrich=enrich,
-             find_emails=find_emails, include_results=include_results)
+             find_emails=find_emails, include_counts=include_counts,
+             include_experience_detail=include_experience_detail,
+             include_skill_details=include_skill_details,
+             include_interests=include_interests,
+             include_recommendations=include_recommendations,
+             include_results=include_results)
 
         data = self._request(
             "POST", path, body=body,
@@ -347,6 +374,12 @@ class EasyData:
         *,
         external_id: str | None = None,
         max_results: int | None = None,
+        find_emails: bool | None = None,
+        include_counts: bool | None = None,
+        include_experience_detail: bool | None = None,
+        include_skill_details: bool | None = None,
+        include_interests: bool | None = None,
+        include_recommendations: bool | None = None,
         idempotency_key: str | None = None,
     ) -> SyncResult:
         """One entity, answered in this response, at twice the credits.
@@ -354,6 +387,12 @@ class EasyData:
         `target`, singular - not a list of one. The bounds are refusals rather
         than downgrades: no `enrich`, no webhooks, and one upstream page for a
         paged operation.
+
+        The optional sections are allowed - a section is one bounded extra
+        request, which is what this path is for - and priced like everything
+        else here, at double: +1 each. So is ``find_emails`` for a profile, at
+        +8: one person is one bounded lookup. It is refused on a search, where
+        it would be one lookup per row inside a single HTTP request.
         """
         if isinstance(target, (list, tuple, set)):
             raise ValueError(
@@ -361,7 +400,12 @@ class EasyData:
             )
 
         body: dict[str, Any] = {"target": target}
-        _put(body, external_id=external_id, max_results=max_results)
+        _put(body, external_id=external_id, max_results=max_results,
+             find_emails=find_emails, include_counts=include_counts,
+             include_experience_detail=include_experience_detail,
+             include_skill_details=include_skill_details,
+             include_interests=include_interests,
+             include_recommendations=include_recommendations)
 
         data = self._request(
             "POST", path + "/sync", body=body,

{easydata_api-1.2.0 → easydata_api-1.4.0}/easydata_api.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: easydata-api
-Version: 1.2.0
+Version: 1.4.0
 Summary: Official Python client for the EasyData LinkedIn enrichment API
 Author-email: EasyData Development <dev@easydata.win>
 License-Expression: MIT
@@ -191,10 +191,22 @@ ed.account()                                        # allowance, ceilings, secre
 ed.usage(from_="2026-09-01", to="2026-09-30")       # spend by day and operation
 ```
 
-Operations are attributes: `profiles_enrich`, `profiles_activity`,
-`profiles_posts`, `profiles_comments`, `profiles_reactions`, `companies_enrich`,
-`posts_enrich`, `sales_search_people`, `sales_search_employees`,
-`sales_search_companies`.
+Operations are attributes: `profiles_enrich`, `profiles_enrich_detailed`,
+`profiles_activity`, `profiles_posts`, `profiles_comments`,
+`profiles_reactions`, `companies_enrich`, `posts_enrich`,
+`sales_search_people`, `sales_search_employees`, `sales_search_companies`.
+
+`profiles_enrich_detailed` is `profiles_enrich` plus the optional sections -
+`include_counts=True` for follower and connection counts,
+`include_experience_detail=True` for what each role actually says,
+`include_skill_details=True` for endorsement counts, `include_interests=True`
+for what the person follows, and `include_recommendations=True` for written
+recommendations in both directions. Each is one more request to LinkedIn and
+costs +0.5 per target, charged only when the section answered, and at least one
+of them is required.
+
+The three list sections come back in three states: absent when you did not ask,
+`[]` when you did and the member has none, and populated otherwise.
 
 ## Reference
 

{easydata_api-1.2.0 → easydata_api-1.4.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "easydata-api"
-version = "1.2.0"
+version = "1.4.0"
 description = "Official Python client for the EasyData LinkedIn enrichment API"
 readme = "README.md"
 requires-python = ">=3.10"