# Astera 10.1 - Additional Notes

### Functionality and Features of Astera Data Stack

#### API Publishing

Astera Data Stack lets users design an API flow, which opens with *Request* and *Response* objects already present in the flow. These can then be used in a pipeline to the application of the user.

<figure><img src="/files/WtbEpyZ2g4k09aVJSi5v" alt=""><figcaption></figcaption></figure>

A simple, configured API flow can look like this:

<figure><img src="/files/0jsbStXhaigUeN0lQqfO" alt=""><figcaption></figcaption></figure>

#### API Consumption

{% hint style="info" %}
**Note:** API Consumption is not a new module, it is already present in Astera Data Stack, but it has also been integrated into Astera Data Stack.
{% endhint %}

When it comes to the Consumption of APIs, Astera lets users configure an *API Connection*, its corresponding *API Client* object, along with an API Browser to maintain various imported or custom *API Collections*.

<figure><img src="/files/vtFSdQ541T8V7xfvX3XO" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/6u8Tva7AWlIWimh57uIT" alt=""><figcaption></figcaption></figure>

Astera Data Stack also makes use of various *HTTP methods* for Consumption such as *GET, POST, PUT, DELETE,* and *PATCH.*

More information related to *HTTP Methods* can be found [here](/astera-data-stack-v10/api-flow/api-consumption/consume/method-operations.md).

Apart from that, the product also offers Pagination functionalities, details for which can be found [here](https://docs.astera.com/projects/data-services/en/latest/consume/pagination.html).

**Enhancements to API Consumption**

**Pagination**

* Automated *Read till End* Options for Page Number, Offset-limit Paginations.
* Cursor Pagination using body fields.
* Pagination support added for POST Requests

**OAuth2**

* OAuth2 token caching and auto-refresh.

**New features of API Consumption**

**OAuth2 and E-Tag**

* OAuth 2 Grant Flow: Authorization Code with PKCE
* E-tags for request caching and concurrency control

**C-API Connectors**

* Create and manage Custom C-API Connectors

CAPI connectors library includes:

* Zendesk Support
* Zendesk Sales CRM
* HubSpot CRM
* Box API

**Other New Features**

* Auto-redirect API calls.
* Use of Default browser for authentication as an alternative to Embedded Browser.
* Import postman API collection.

#### Server Browser Functionalities

The *Server Browser* in Astera Data Stack lets the user manage and publish APIs once they have been deployed.

A wide range of functionalities are offered in the deployment of APIs, including setting authentication and security functions.

Within the Server Browser, user roles can be assigned, and specific resources can be provided to each role, respective to their area of application. The Server Browser also has the feature to auto-generate a swagger Url.

<figure><img src="/files/rDneBh9US7AIkpGOp043" alt=""><figcaption></figcaption></figure>

#### API Monitoring and Logging

Once the APIs have been deployed, they can also be viewed in a dashboard present in Astera Data Stack.

<figure><img src="/files/PfXdRGwMLOFU6MrjwEQw" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/FxGu8aydGZYUEdRCWt5J" alt=""><figcaption></figcaption></figure>

Finally, users can also utilize Astera for logging and tracing.

<figure><img src="/files/clFiXULlSBW6gf2isqY3" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/GwZZcc8ZRsQ41Pt6EpUM" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.astera.com/astera-data-stack-v10/release-notes/astera-10.1-additional-notes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.