This repository links a git submodule that contains the Vectara proto definitions
needed for grpc calls. In order to properly clone this repository, use the
--recurse-submodules flag in the clone command like following:
git clone --recurse-submodules https://<RepoPath>
Doing this will ensure that the submodule containing proto definitions is fetched as well.
If you have already cloned the repository, without using above flag, then you can run following two commands to fetch the submodule:
git submodule initgit submodule update
Vectara APIs require authentication of some form to work. Following are the two authentication methods that are supported.
- OAuth2
- API Keys
An API User's first step is to obtain a JWT Token. To obtain JWT Token, following steps need to be done.
- Create an App Client in Vectara Console.
- Assign appropriate rights to this App client over a corpus. These rights can be
QRY,IDX,ADMor a combination of these three. - Note down the following three things from App Client page in Console.
- App Client ID
- App Client Secret
- Auth URL (This is available near the top of the page)
- Also note down your Vectara customer ID and the Corpus ID (of the corpus you want to index data to, or query.)
Once you have all the above data, you can use it to obtain a valid JWT Auth token. With this token, you can make API calls to index data, query data and/or perform certain admin tasks such as create corpus, delete corpus, etc.
All of this is demonstrated in the code. For further clarification, please see the code.
Please note that your App Client needs to have sufficient privileges to perform indexing, querying or admin tasks. These privileges can be assigned in Vectara console.
The API Key authentication method is supported with Serving/Querying only.
Use the following link to generate an API Key via Vectara platform. Api Keys
While generating an API Key, make sure that you have assigned the correct corpus to it.