You can use the Mystic CLI to authenticate and store your API credentials in your local directory
~/.pipeline/. Any time you use the SDK to interact with the Mystic API, the SDK will then use these credentials under the hood.
Check your environment
You can either authenticate using the CLI or using environment variables, but you're likely to run into issues if you combine the two. In most cases, you'll be best off using the CLI, however, environment variables are likely to be more convenient if you're running you code on a remote server, for example in a web app.
If using the CLI, check if you have previously added your
PIPELINE_API_TOKENto your environment, and make sure to remove it before authenticating with the CLI.
On Linux/macOS, you can check whether you have set
And if the output from the above command is not empty, you can remove it with:
pipeline cluster login mystic-api API_TOKEN -u https://www.mystic.ai -a
with a valid API token. If you need a new token, you can create one in your dashboard.
You should now find a file at
~/.pipeline/config.yaml, which looks something like:
- alias: mystic-api
Updated about 1 month ago