For authentication with the GitLab REST API, you need to create and provide a Personal Access Token.

You can create and maintain access tokens in your GitLab user's preferences page (eg at https://gitlab.com/-/user_settings/personal_access_tokens) by pressing the “Add new token” button and then selecting the appropriate scopes. api needs to be selected.

The Create Connection.vi expects the value of the previously created token for its Private Token input:

The toolkit comes with a helper VI that reads the access token from a configuration file. This VI only serves as an example of how the private token could be stored and provided.

Read Private Token From Configuration File.vi reads the Personal Access Token from a configuration file located at <LabVIEW Data>\GitLab API\config.ini. The token needs to be stored in the key private-token.

If “Section” is not empty, it is used as the section name in the config file. Otherwise, the section is set to “global”.

The API ships with several examples which you can browse from the Example Finder (“Help → Find Examples…” menu item in the LabVIEW IDE), In the NI Example Finder, browsing the directory structure, navigate to \Hampel Software Engineering\GitLab API where you will find a number of example VIs.

One of the shipping example VIs is List Releases.vi:

The basic pattern is always the same:

1. Create the connection from Server Base URL and the private token
2. Set the repo URL
3. Execute the API request (“List Releases” in this case)
4. Close the connection

As the screenshots show, the VI requires four parameters (much like all other methods):

1. Server Base URL (required)
2. Repo Namespace (optional)
3. Repo Group (optional)
4. Repo Name(required)

The other three parameters make up the URL to the project in GitLab. See the following screenshots for further details: