> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/developer-guide/consent-javascript-sdk/sdk-functions.md).

# SDK Functions

To get the current status of the **JENTIS Consent JavaScript SDK**, you can use the following client-side (frontend) JavaScript APIs.\
These functions allow you to retrieve the consent state for vendors, IDs, timestamps, and full vendor data directly from the user’s browser.

All functions are accessed via:

```javascript
jentis.consent.engine.<functionName>()
```

### Available Functions

* getVendorConsent – Get consent status for a specific vendor.
* getAllConsents – Retrieve consent status for all vendors.
* getConsentData – Get the custom consent data object for the current page scope.
* getConsentId – Get the current Consent ID for the user.
* getVendorFullData – Get all available vendor information.
* getLastUpdateTime – Get the timestamp of the last consent update.
* setNewVendorConsents – Set consent for one or more vendors.
* setConsentData – Store custom consent data in the JENTIS consent document.
* AcceptAll – Grant consent to all vendors.
* DenyAll – Revoke consent for all vendors.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jentis.com/developer-guide/consent-javascript-sdk/sdk-functions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.