> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/faqs/i-got-the-webhook-error-invalid-session-id-what-should-i-do.md).

# I got the Webhook error "INVALID\_SESSION\_ID". What should I do?

<figure><img src="https://751044238-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi8tH1o5AHthxksYgF6ij%2Fuploads%2FgPxrFRckaVzmWMu7Grko%2Ftest.png?alt=media&amp;token=7f5e98c6-3cc5-4f16-9108-212788c6f93e" alt=""><figcaption></figcaption></figure>

If you got a Webhook error similar to the above stating: INVALID\_SESSION\_ID: Invalid Session ID found in SessionHeader: Illegal Session, this most probably means that SharinPix does not have access to your Salesforce data. Such issues usually come up when the user who previously granted SharinPix access to Salesforce has been deactivated.

Therefore, another **active user** should restore the access to Salesforce by following these steps:

* On your organization, search for **SharinPix Settings** using the App Launcher
* Then once, on the **SharinPix Settings** tab, click on the **Grant** button next to the second line, that is next to **Sharinpix - > Salesforce full API access** as demonstrated below:

<figure><img src="https://751044238-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi8tH1o5AHthxksYgF6ij%2Fuploads%2FJY9EwAA4cZ4LAZeYStG2%2Ftest.png?alt=media&amp;token=ec121bc5-96e1-43bb-8f45-5c7c731b6943" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
**Note:**

In cases where, SharinPix is being configured by a third-party user having a temporary account, it is not recommended that the third-party user restores the access to Salesforce. Here, you should ensure that the grant access to Salesforce has been performed by one of the client's active users and not the third-party user in order to avoid any loss of access if ever the third-party user becomes inactive.
{% endhint %}


---

# 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.sharinpix.com/faqs/i-got-the-webhook-error-invalid-session-id-what-should-i-do.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.
