@@ -123,12 +123,10 @@ If you already have a Splunk Cloud Platform account and a Splunk Observability C
123123
124124 .. code-block :: bash
125125
126- curl --location
127- ' https://admin.splunk.com/<enter-stack-name>/adminconfig/v2/observability/sso-pairing' \
128- --header ' Content-Type: application/json' \
129- --header ' Authorization: Bearer <enter-splunk-admin-api-token>' \
130- --header ' o11y-access-token' : ' <enter-o11y-api-token>'
131-
126+ curl -X POST ' https://admin.splunk.com/<enter-stack-name>/adminconfig/v2/observability/sso-pairing' \
127+ -H " Content-Type: application/json" \
128+ -H " Authorization: Bearer <enter-splunk-admin-api-token>" \
129+ -H " o11y-access-token: <enter-o11y-api-token>"
132130
133131 Whether you used the command-line interface or API endpoints, the pairing command returns a pairing id:
134132
@@ -150,11 +148,11 @@ If you already have a Splunk Cloud Platform account and a Splunk Observability C
150148
151149 .. code-block :: bash
152150
153- curl --location --request GET
154- ' https://admin.splunk.com/<enter-stack-name>/adminconfig/v2/observability/sso-pairing/<enter-pairing-id> ' \
155- --header ' Content-Type: application/json ' \
156- --header ' Authorization: Bearer <enter-splunk-admin- api-token>'
157- --header ' o11y-access-token ' : ' <enter-o11y-api-token> '
151+ curl -X GET ' https://admin.splunk.com/<enter-stack-name>/adminconfig/v2/observability/sso-pairing/<enter-pairing-id> ' \
152+ -H " Content-Type: application/json " \
153+ -H " Authorization: Bearer <enter-splunk-admin-api-token> " \
154+ -H " o11y-access-token: <enter-o11y- api-token>"
155+
158156
159157 5. The system returns a status message showing whether or not the pairing was a success. Statuses are SUCCESS, FAILED, or IN_PROGRESS.
160158
0 commit comments