> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.237/mbse-connector-sdk-index/getting-started/passing-the-configuration-parameters-to-mbse-sdk-apis.md).

# Passing Configuration Parameters

* OpsHub Integration Manager assumes that MBSE Connector SDK API implementation will be stateless. MBSE SDK is not required to have a database to persist any data(though, if MBSE SDK implementation wants to use a database to store something, they can do it)
* OpsHub Integration Manager will capture all the required parameters at the time of system configuration. OpsHub will pass all these parameters to the connector MBSE SDK APIs in Request Header for each API call.
* Though if the connector want to cache some data for a session, they can use the session id passed in the header to maintain a cache for that session. This session id will be same for all the API calls for a given system configuration.
  * In the [Initialize API](/v7.237/mbse-connector-sdk-index/mbse-sdk-connector-apis/authentication-apis/session-initialize.md), OpsHub will pass all the parameters captured at the time of system configuration in the request body. MBSE SDK can return any of these parameters in the response, and OpsHub will pass them in the header for all subsequent API calls.
    * If the MBSE SDK implementation wants to keep some data in cache for a session and doesn't want it to be passed as header in every request, it can do so.


---

# 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.opshub.com/v7.237/mbse-connector-sdk-index/getting-started/passing-the-configuration-parameters-to-mbse-sdk-apis.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.