OpenTelemetry Deep Dive: Hands-On with the OTel Collector & Bindplane - Join the live workshop on March 19th at 11 AM ET!Sign Up Now

Configuration

Configure the CLI or REST API to use an API Key to access resources in Bindplane

Using your API Key with the CLI

You can set the API Key value in your configuration by using the bindplane profile command. e.g.

shell
1bindplane profile set default --api-key 4689832f-1725-4eeb-8f9d-3e78cb0155ec

This sets your "default" profile to use the API key you just received. You may also need to set your remote-url to the correct endpoint, for app.bindplane.com users:

shell
1bindplane profile set default --remote-url https://app.bindplane.com

Make sure you are using the default profile

shell
1bindplane profile use default

Now verify you can retrieve resources, say Source Types

shell
1bindplane get source-types

To set named profiles run

shell
1bindplane profile set "onprem" --api-key "xxxx-xxxx-xxxx-xxxx-xxxxxx"

To use custom remote URLs run

shell
1bindplane profile set "onprem" \
2  --remote-url "http://192.168.1.10:3001" \
3  --api-key "xxxx-xxxx-xxxx-xxxx-xxxxxx"

Configure a profile with a user and password

shell
1bindplane profile set "example" \
2 --remote-url "http://192.168.1.10:3001" \
3 --username "user" \
4 --password "pass"
5
6bindplane profile use "example"

Using your API Key with the REST API

You can use your API with the REST API by setting the X-Bindplane-Api-Key header. An example using curl with Bindplane Cloud:

shell
1curl -X GET -H 'X-Bindplane-Api-Key: 4689832f-1725-4eeb-8f9d-3e78cb0155ec' https://app.bindplane.com/v1/source-types