anaplan-sdk 0.2.6__tar.gz → 0.2.8__tar.gz

{anaplan_sdk-0.2.6 → anaplan_sdk-0.2.8}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: anaplan-sdk
-Version: 0.2.6
+Version: 0.2.8
 Summary: Provides pythonic access to the Anaplan API
 Project-URL: Homepage, https://vinzenzklass.github.io/anaplan-sdk/
 Project-URL: Repository, https://github.com/VinzenzKlass/anaplan-sdk
@@ -22,6 +22,7 @@ Description-Content-Type: text/markdown
 <h1 align="center" style="font-size: 3rem; font-weight: 400; margin: -15px 0">
 Anaplan SDK
 </h1>
+
 <p align="center" style="margin-top: 15px">
 <a href="https://pepy.tech/project/anaplan-sdk">
 <img align="center" src="https://static.pepy.tech/badge/anaplan-sdk/month" alt="Downloads Badge"/>
@@ -30,15 +31,15 @@ Anaplan SDK
 
 ---
 
-Anaplan SDK is an independent, unofficial project providing pythonic access to
-the [Anaplan Integration API v2](https://anaplan.docs.apiary.io/). This Project aims to provide high-level abstractions
-over the API, so you can deal with python objects and simple functions rather than implementation details like HTTP
-Requests, Authentication, JSON Parsing, Compression, Chunking and so on.
+Anaplan SDK is an independent, unofficial project providing pythonic access to Anaplan. Anaplan SDK provides high-level
+abstractions over the various Anaplan APIs, so you can focus on you requirements rather than spend time on
+implementation details like authentication, error handling, chunking, compression and data formatting.
 
 This Projects supports
-the [Bulk API](https://help.anaplan.com/use-the-bulk-apis-93218e5e-00e5-406e-8361-09ab861889a7),
-the [Transactional API](https://help.anaplan.com/use-the-transactional-apis-cc1c1e91-39fc-4272-a4b5-16bc91e9c313) and
-the [ALM API](https://help.anaplan.com/application-lifecycle-management-api-2565cfa6-e0c2-4e24-884e-d0df957184d6),
+the [Bulk APIs](https://help.anaplan.com/use-the-bulk-apis-93218e5e-00e5-406e-8361-09ab861889a7),
+the [Transactional APIs](https://help.anaplan.com/use-the-transactional-apis-cc1c1e91-39fc-4272-a4b5-16bc91e9c313) and
+the [ALM APsI](https://help.anaplan.com/application-lifecycle-management-api-2565cfa6-e0c2-4e24-884e-d0df957184d6),
+the [Audit APIs](https://auditservice.docs.apiary.io/#),
 providing both synchronous and asynchronous Clients.
 
 Visit [Anaplan SDK](https://vinzenzklass.github.io/anaplan-sdk/) for documentation.

{anaplan_sdk-0.2.6 → anaplan_sdk-0.2.8}/README.md

@@ -5,6 +5,7 @@
 <h1 align="center" style="font-size: 3rem; font-weight: 400; margin: -15px 0">
 Anaplan SDK
 </h1>
+
 <p align="center" style="margin-top: 15px">
 <a href="https://pepy.tech/project/anaplan-sdk">
 <img align="center" src="https://static.pepy.tech/badge/anaplan-sdk/month" alt="Downloads Badge"/>
@@ -13,15 +14,15 @@ Anaplan SDK
 
 ---
 
-Anaplan SDK is an independent, unofficial project providing pythonic access to
-the [Anaplan Integration API v2](https://anaplan.docs.apiary.io/). This Project aims to provide high-level abstractions
-over the API, so you can deal with python objects and simple functions rather than implementation details like HTTP
-Requests, Authentication, JSON Parsing, Compression, Chunking and so on.
+Anaplan SDK is an independent, unofficial project providing pythonic access to Anaplan. Anaplan SDK provides high-level
+abstractions over the various Anaplan APIs, so you can focus on you requirements rather than spend time on
+implementation details like authentication, error handling, chunking, compression and data formatting.
 
 This Projects supports
-the [Bulk API](https://help.anaplan.com/use-the-bulk-apis-93218e5e-00e5-406e-8361-09ab861889a7),
-the [Transactional API](https://help.anaplan.com/use-the-transactional-apis-cc1c1e91-39fc-4272-a4b5-16bc91e9c313) and
-the [ALM API](https://help.anaplan.com/application-lifecycle-management-api-2565cfa6-e0c2-4e24-884e-d0df957184d6),
+the [Bulk APIs](https://help.anaplan.com/use-the-bulk-apis-93218e5e-00e5-406e-8361-09ab861889a7),
+the [Transactional APIs](https://help.anaplan.com/use-the-transactional-apis-cc1c1e91-39fc-4272-a4b5-16bc91e9c313) and
+the [ALM APsI](https://help.anaplan.com/application-lifecycle-management-api-2565cfa6-e0c2-4e24-884e-d0df957184d6),
+the [Audit APIs](https://auditservice.docs.apiary.io/#),
 providing both synchronous and asynchronous Clients.
 
 Visit [Anaplan SDK](https://vinzenzklass.github.io/anaplan-sdk/) for documentation.

anaplan_sdk-0.2.8/anaplan_sdk/_async_clients/__init__.py

@@ -0,0 +1,6 @@
+from ._alm import _AsyncAlmClient
+from ._audit import _AsyncAuditClient
+from ._bulk import AsyncClient
+from ._transactional import _AsyncTransactionalClient
+
+__all__ = ["AsyncClient", "_AsyncAlmClient", "_AsyncAuditClient", "_AsyncTransactionalClient"]

{anaplan_sdk-0.2.6 → anaplan_sdk-0.2.8}/anaplan_sdk/_async_clients/_audit.py

@@ -10,7 +10,7 @@ from anaplan_sdk._base import _AsyncBaseClient
 Event = Literal["all", "byok", "user_activity"]
 
 
-class _AuditClient(_AsyncBaseClient):
+class _AsyncAuditClient(_AsyncBaseClient):
     def __init__(self, client: httpx.AsyncClient, retry_count: int) -> None:
         self._client = client
         self._limit = 10_000
@@ -49,11 +49,18 @@ class _AuditClient(_AsyncBaseClient):
         ).get("response", [])
 
     async def get_events(self, days_into_past: int = 30, event_type: Event = "all") -> list:
+        """
+        Get audit events from Anaplan Audit API.
+        :param days_into_past: The nuber of days into the past to get events for. The API provides
+        data for up to 30 days.
+        :param event_type: The type of events to get.
+        :return: A list of audit events.
+        """
         total = await self._get_total(days_into_past, event_type)
         if total == 0:
             return []
         if total <= 10_000:
-            return await self._get_result_page(total)
+            return await self._get_result_page(days_into_past, event_type)
 
         return list(
             chain.from_iterable(

{anaplan_sdk-0.2.6 → anaplan_sdk-0.2.8}/anaplan_sdk/_async_clients/_bulk.py

@@ -17,7 +17,7 @@ from anaplan_sdk.exceptions import AnaplanActionError, InvalidIdentifierExceptio
 from anaplan_sdk.models import Action, Export, File, Import, Model, Process, Workspace
 
 from ._alm import _AsyncAlmClient
-from ._audit import _AuditClient
+from ._audit import _AsyncAuditClient
 from ._transactional import _AsyncTransactionalClient
 
 logging.getLogger("httpx").setLevel(logging.CRITICAL)
@@ -110,7 +110,7 @@ class AsyncClient(_AsyncBaseClient):
         self._alm_client = (
             _AsyncAlmClient(self._client, model_id, self._retry_count) if model_id else None
         )
-        self.audit = _AuditClient(self._client, self._retry_count)
+        self.audit = _AsyncAuditClient(self._client, self._retry_count)
         self.status_poll_delay = status_poll_delay
         self.upload_chunk_size = upload_chunk_size
         self.allow_file_creation = allow_file_creation
@@ -381,7 +381,7 @@ class AsyncClient(_AsyncBaseClient):
 
     async def export_and_download(self, action_id: int) -> bytes:
         """
-        Convenience wrapper around `run_action()` a     nd `get_file()` to run an export action and
+        Convenience wrapper around `run_action()` and `get_file()` to run an export action and
         download the exported content in one call.
         :param action_id: The identifier of the action to run.
         :return: The content of the exported file.
@@ -389,6 +389,16 @@ class AsyncClient(_AsyncBaseClient):
         await self.run_action(action_id)
         return await self.get_file(action_id)
 
+    async def list_task_status(self, action_id: int) -> list:
+        """
+        Retrieves the status of all tasks spawned by the specified action.
+        :param action_id: The identifier of the action that was invoked.
+        :return: The list of tasks spawned by the action.
+        """
+        return (await self._get(f"{self._url}/{action_url(action_id)}/{action_id}/tasks")).get(
+            "tasks", []
+        )
+
     async def get_task_status(
         self, action_id: int, task_id: str
     ) -> dict[str, float | int | str | list | dict | bool]:

anaplan_sdk-0.2.8/anaplan_sdk/_clients/__init__.py

@@ -0,0 +1,6 @@
+from ._alm import _AlmClient
+from ._audit import _AuditClient
+from ._bulk import Client
+from ._transactional import _TransactionalClient
+
+__all__ = ["Client", "_AlmClient", "_AuditClient", "_TransactionalClient"]

{anaplan_sdk-0.2.6 → anaplan_sdk-0.2.8}/anaplan_sdk/_clients/_audit.py

@@ -49,11 +49,18 @@ class _AuditClient(_BaseClient):
         ).get("response", [])
 
     def get_events(self, days_into_past: int = 30, event_type: Event = "all") -> list:
+        """
+        Get audit events from Anaplan Audit API.
+        :param days_into_past: The nuber of days into the past to get events for. The API provides
+        data for up to 30 days.
+        :param event_type: The type of events to get.
+        :return: A list of audit events.
+        """
         total = self._get_total(days_into_past, event_type)
         if total == 0:
             return []
         if total <= 10_000:
-            return self._get_result_page(total)
+            return self._get_result_page(days_into_past, event_type)
 
         from concurrent.futures import ThreadPoolExecutor
 

{anaplan_sdk-0.2.6 → anaplan_sdk-0.2.8}/anaplan_sdk/_clients/_bulk.py

@@ -382,6 +382,14 @@ class Client(_BaseClient):
         self.run_action(action_id)
         return self.get_file(action_id)
 
+    def list_task_status(self, action_id: int) -> list:
+        """
+        Retrieves the status of all tasks spawned by the specified action.
+        :param action_id: The identifier of the action that was invoked.
+        :return: The list of tasks spawned by the action.
+        """
+        return self._get(f"{self._url}/{action_url(action_id)}/{action_id}/tasks").get("tasks", [])
+
     def get_task_status(
         self, action_id: int, task_id: str
     ) -> dict[str, float | int | str | list | dict | bool]:

{anaplan_sdk-0.2.6 → anaplan_sdk-0.2.8}/docs/anaplan_explained.md

@@ -1,19 +1,18 @@
-This section tries to explain Anaplan specific concepts and design choices to Developers to enable a better
-understanding of the API. It is less interesting for people
-already familiar with Anaplan.
+This section tries to explain Anaplan specific concepts and design choices to Developers. It is less interesting for
+people already familiar with Anaplan. Most of this page applies to the Bulk API, but some concepts are also
+applicable to the Transactional API. To understand how Anaplan handles data, you are going to have to wrap your head
+around some fundamental concepts, as well as gain a basic understanding of some Anaplan specific terminology.
 
-To understand how Anaplan handles data, you are going to have to wrap your head around some fundamental concepts, as
-well as gain a basic understanding of some Anaplan specific terminology. To truly understand the Anaplan API and why the
-dataflows and structures are the way they are, obtaining a well-founded understanding of how Anaplan handles data, is
-essential.
-
-This page list tries to condense the fundamentals of using the Anaplan Bulk API. The transactional API is different
-in many ways.
-
-
-<p align="center" style="margin: 40px 0 40px 0;">
+The basic high-level view of any Anaplan Integration looks like this:
+<p align="center" style="margin: 20px 0 40px 0;">
     <img src="../img/anaplan-overview.webp" alt='Anaplan high-level view' style="border-radius: 15px">
 </p>
+!!! tip "TLDR"
+    You upload contents to files. Import Actions import the content from these files into Lists and Modules. Export
+    Actions export the content of Lists and Modules to files. You can download these files. Processes are just sequences
+    of actions. Anything that references the same file must not be run concurrently.
+
+
 
 ## Basic Concepts
 
@@ -26,7 +25,7 @@ in many ways.
     - Exports - 116000000000 IDs.
     - Processes - 118000000000 IDs.
     - Other Actions - 117000000000 IDs.
-  
+
 - Imports read data from a file and load it into a module. Exports conversely load data from a module to a file. The
   file id of the resulting file is identical to the export id. "Other Actions" move things around in Anaplan and can
   also delete data etc. Processes are simply a sequence of the other three.

{anaplan_sdk-0.2.6/docs → anaplan_sdk-0.2.8/docs/api}/alm_client.md

@@ -1,5 +1,5 @@
 !!! note
     This Class is not meant to be instantiated directly, but rather accessed through the `alm` Property on an
-    instance of [Client](client.md). For more details, see the [Guide](alm.md).
+    instance of [Client](client.md). For more details, see the [Guide](../guides/alm.md).
 
 ::: anaplan_sdk._clients._AlmClient

{anaplan_sdk-0.2.6/docs → anaplan_sdk-0.2.8/docs/api}/async_alm_client.md

@@ -1,5 +1,5 @@
 !!! note
     This Class is not meant to be instantiated directly, but rather accessed through the `alm` Property on an
-    instance of [Client](client.md). For more details, see the [Guide](alm.md).
+    instance of [Client](client.md). For more details, see the [Guide](../guides/alm.md).
 
 ::: anaplan_sdk._async_clients._AsyncAlmClient

anaplan_sdk-0.2.8/docs/api/async_audit_client.md

@@ -0,0 +1,5 @@
+!!! note
+    This Class is not meant to be instantiated directly, but rather accessed through the `audit` Property on an
+    instance of [Client](client.md). For more details, see the [Guide](../guides/audit.md).
+
+::: anaplan_sdk._async_clients._AsyncAuditClient

{anaplan_sdk-0.2.6/docs → anaplan_sdk-0.2.8/docs/api}/async_transactional_client.md

@@ -1,5 +1,5 @@
 !!! note
     This Class is not meant to be instantiated directly, but rather accessed through the `alm` Property on an
-    instance of [AsyncClient](async_client.md). For more details, see the [Guide](transactional.md).
+    instance of [AsyncClient](async_client.md). For more details, see the [Guide](../guides/transactional.md).
 
 ::: anaplan_sdk._async_clients._alm._AsyncAlmClient

anaplan_sdk-0.2.8/docs/api/audit_client.md

@@ -0,0 +1,5 @@
+!!! note
+    This Class is not meant to be instantiated directly, but rather accessed through the `audit` Property on an
+    instance of [Client](client.md). For more details, see the [Guide](../guides/audit.md).
+
+::: anaplan_sdk._clients._AuditClient

{anaplan_sdk-0.2.6/docs → anaplan_sdk-0.2.8/docs/api}/transactional_client.md

@@ -1,5 +1,5 @@
 !!! note
     This Class is not meant to be instantiated directly, but rather accessed through the `transactional` Property on an
-    instance of [Client](client.md). For more details, see the [Guide](transactional.md).
+    instance of [Client](client.md). For more details, see the [Guide](../guides/transactional.md).
 
 ::: anaplan_sdk._clients._TransactionalClient

{anaplan_sdk-0.2.6/docs → anaplan_sdk-0.2.8/docs/guides}/alm.md

@@ -1,5 +1,3 @@
-## Intro
-
 The purpose of the Application Lifecycle Management (ALM) API is to make model change management more scalable,
 automatable, and integrate with other systems.
 
@@ -80,5 +78,5 @@ revisions, syncs = await asyncio.gather(alm.get_revisions(), alm.get_sync_tasks(
 ///
  
 !!! note
-      While you can instantiate a [Client](client.md) without the workspace or model parameters, trying to access
-      the [Transactional Client](transactional_client.md) on an instance without the `model_id` will raise a `ValueError`.
+      While you can instantiate a [Client](../api/client.md) without the workspace or model parameters, trying to access
+      the [Transactional Client](../api/transactional_client.md) on an instance without the `model_id` will raise a `ValueError`.

anaplan_sdk-0.2.8/docs/guides/audit.md

@@ -0,0 +1,42 @@
+You can use the Audit API to get fine-grained information about the changes made to any model, usage, user sign-ins,
+most frequently visited pages and much more. The Audit API exposes most the logs collected by Anaplan.
+
+For details refer to
+[the Documentation](https://auditservice.docs.apiary.io/#).
+
+## Usage
+
+The method for the Audit API reside in a different namespace for better API navigability and
+comprehensiveness, but are accessible through the same client for convenience. For e.g., you can call
+the `.get_events()` method like so:
+
+/// tab | Synchronous
+
+```python
+import anaplan_sdk
+
+anaplan = anaplan_sdk.Client(
+    workspace_id="AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA",
+    model_id="11111111111111111111111111111111",
+    certificate="~/certs/anaplan.pem",
+    private_key="~/keys/anaplan.pem",
+)
+events = anaplan.audit.get_events()
+```
+
+///
+/// tab | Asynchronous
+
+```python
+import anaplan_sdk
+
+anaplan = anaplan_sdk.AsyncClient(
+    workspace_id="AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA",
+    model_id="11111111111111111111111111111111",
+    certificate="~/certs/anaplan.pem",
+    private_key="~/keys/anaplan.pem",
+)
+events = await anaplan.audit.get_events()
+```
+
+///

{anaplan_sdk-0.2.6/docs → anaplan_sdk-0.2.8/docs/guides}/bulk.md

@@ -1,106 +1,172 @@
-!!! tip "Client Settings"
-      Anaplan SDK comes with a set of default options that are efficient for most use cases and general purpose. Mainly, it
-      will compress all data before uploading and leverage Concurrency to speed up- and downloads. with a chunk size of 25MB.
-      However, you can tune the client to better suit your needs. For more information,
-      see [Client Parameters](client.md#anaplan_sdk.Client.__init__).
-
-## Intro
-
 When using this SDK you would never know it, but the workflow of performing an import of data into or export from
 Anaplan is actually quite involved. To give you the full context and allow you to make informed choices, let's take a
 look at the individual steps, how to perform them individually and how one can put these together to use the Bulk API to
 the greatest efficiency.
 
-Assuming you already know all the relevant Id's, the steps are:
+!!! tip "Client Settings"
+    Anaplan SDK comes with a set of default options that are efficient for most use cases and general purpose. Mainly, it
+    will compress all data before uploading and leverage Concurrency to speed up- and downloads, with a chunk size of 25MB.
+    However, you can configure the client to better fit your needs. For more information,
+    see [Client Parameters](../api/client.md#anaplan_sdk.Client.__init__).
+
+## Basic Usage
 
-/// tab | Import
+### Instantiate a Client
 
-1. Chunk your content. There is no enforced hard limit on chunk sizes, but there is a strong Recommendation to not
-   exceed 50 MB and in practice you would be seeking to keep them smaller still. This SDK's default chunk size is 25 MB.
-2. Set the chunk count, if you don't know this number ahead of time, set it to -1.
-3. Upload all chunks
-4. Mark the upload as complete. Only necessary if you set the count to -1 in step 2.
-5. Trigger the import action. This will return a Task Id for the task you just spawned.
-6. Poll the task status until the tasks completes.
-7. Validate the task outcome.
+Clients are instantiated with the workspace, model and authentication information. There are two primary means of
+Authentication.
+
+#### Basic Authentication
+
+Basic Authentication is unsuitable for Production. Anaplan password policies force password changes every 30, 60 or 90
+days, depending on tenant settings, making this approach annoying to maintain and error-prone and is thus not
+recommended for production.
+
+/// tab | Synchronous
+
+```python
+import anaplan_sdk
+
+anaplan = anaplan_sdk.Client(
+    workspace_id="AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA",
+    model_id="11111111111111111111111111111111",
+    user_email="admin@company.com",
+    password="my_super_secret_password",
+)
+```
 
 ///
 
-/// tab | Export
+/// tab | Asynchronous
+
+```python
+import anaplan_sdk
 
-1. Run the export.
-2. Poll the task status until the tasks completes.
-3. Get the file info and retrieve the chunk count.
-4. Download all chunks.
-5. Merge the chunks.
+anaplan = anaplan_sdk.AsyncClient(
+    workspace_id="AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA",
+    model_id="11111111111111111111111111111111",
+    user_email="admin@company.com",
+    password="my_super_secret_password",
+)
+```
 
 ///
 
-With this SDK, all of the above is condensed to:
+#### Certificate Authentication
 
 /// tab | Synchronous
 
 ```python
+import anaplan_sdk
+
 anaplan = anaplan_sdk.Client(
     workspace_id="AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA",
     model_id="11111111111111111111111111111111",
     certificate="~/certs/anaplan.pem",
     private_key="~/keys/anaplan.pem",
+    private_key_password="my_super_secret_password",
 )
-anaplan.upload_and_import(113000000000, b"Hello World!", 118000000000)
-export_content = anaplan.export_and_download(116000000000)
+
 ```
 
 ///
 /// tab | Asynchronous
 
 ```python
+import anaplan_sdk
+
 anaplan = anaplan_sdk.AsyncClient(
     workspace_id="AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA",
     model_id="11111111111111111111111111111111",
     certificate="~/certs/anaplan.pem",
     private_key="~/keys/anaplan.pem",
+    private_key_password="my_super_secret_password",
 )
-_, export_content = await gather(
-    anaplan.upload_and_import(113000000000, b"Hello World!", 118000000000),
-    anaplan.export_and_download(116000000000),
-)
+
+```
+
+///
+
+### Importing data
+
+/// tab | Synchronous
+
+```python
+anaplan.upload_file(113000000000, b"Hello Anaplan")
+anaplan.run_action(112000000000)
+
+# Or in short:
+anaplan.upload_and_import(113000000000, b"Hello Anaplan", 112000000000)
 ```
 
-Here we can safely run the import and export concurrently, as they have no overlap in the files the reference. If they
-did, this would be a terrible idea. See [this Chapter](bulk_vs_transactional.md/#the-bad) for details on this.
+///
+/// tab | Asynchronous
+
+```python
+await anaplan.upload_file(113000000000, b"Hello Anaplan")
+await anaplan.run_action(112000000000)
+
+# Or in short:
+await anaplan.upload_and_import(113000000000, b"Hello Anaplan", 112000000000)
+
+```
 
 ///
 
-This standard case will typically cover most of your needs. Let's now look at some more involved examples, where you
-may need some more control over the underlying files and actions to achieve a more efficient exchange.
+### Exporting data
+
+/// tab | Synchronous
+
+```python
+anaplan.run_action(116000000000)
+content = anaplan.get_file(116000000000)
+
+# Or in short:
+content = anaplan.export_and_download(116000000000)
+```
+
+///
+/// tab | Asynchronous
+
+```python
+await anaplan.run_action(116000000000)
+content = await anaplan.get_file(116000000000)
+
+# Or in short:
+content = await anaplan.export_and_download(116000000000)
+```
+
+///
 
 ## Applications
 
 ### One source with multiple Actions
 
-One of the most common patterns you'll find working with Anaplan is the *upload content -> import into list -> import
-into module*. As a hand-wavy TL;DR, you can think of Lists as collections of Metadata and Modules as Tables holding the
-actual data. Importing into a list, you must provide a unique identifier, which will be stored in the list alongside
-some additional information about this record you can add, and the module will then hold all the records for each id.
-Since uploading the content the module and the list share twice would be redundant and inefficient, we want to group
-those.
+One of the most common patterns you'll find working with Anaplan is:
+
+1. Upload content
+2. Import into a list
+3. Import into a module
 
-The easiest way to do this is to have your model builder create two actions that reference the same file, one importing
-into the list and the other one importing into the module and then put them into a process. This would again just look
-like this:
+The recommended way to do this is to have your model builder create two actions that reference the same file, one
+importing into the list and the other one importing into the module and then wrap them into a process. This would again
+just look like this:
 
 /// tab | Synchronous
 
 ```python
-anaplan.upload_and_import(113000000000, b"Hello World!", 118000000000)
+anaplan.upload_and_import(
+    file_id=113000000000, content=b"Hello World!", action_id=118000000000
+)
 ```
 
 ///
 /// tab | Asynchronous
 
 ```python
-await anaplan.upload_and_import(113000000000, b"Hello World!", 118000000000)
+await anaplan.upload_and_import(
+    file_id=113000000000, content=b"Hello World!", action_id=118000000000
+)
 ```
 
 ///
@@ -159,7 +225,7 @@ await anaplan.run_action(118000000000)
 If you have a file that is larger than your available RAM, or you are consuming chunks from i.e. a queue until it is
 exhausted and thus cannot know the number of expected chunks ahead of time, you can use the `upload_file_stream` method.
 You can pass an Iterator - in this case a Generator - that yields the chunks to this method, and it will handle the
-rest. The `upload_file_stream` method on the [AsyncClient](async_client.md#anaplan_sdk.AsyncClient.upload_file_stream)
+rest. The `upload_file_stream` method on the [AsyncClient](../api/async_client.md#anaplan_sdk.AsyncClient.upload_file_stream)
 accepts both `AsyncIterator[bytes | str]` and `Iterator[str | bytes]`.
 
 This will work nicely with i.e. [`scan_parquet()`](https://docs.pola.rs/user-guide/io/parquet/#scan)
@@ -205,14 +271,13 @@ This will allow you to upload files of arbitrary size without running into memor
 small enough to fit into memory. It will work equally well with any other source that can be read in chunks and
 especially well with sources that can be read lazily or return the results sets in chunks by default.
 
-
 You can in the same way use the `get_file_stream` method to download files in chunks.
 
 /// tab | Synchronous
 
 ```python
 for chunk in anaplan.get_file_stream(113000000040):
-   ...  # do something with the chunk
+    ...  # do something with the chunk
 ```
 
 ///