The Webex API utilizes the OAuth 2.0 framework, which employs Bearer tokens for authentication. The standard for presenting a Bearer token in an API request is to use the Authorization HTTP header. The value of this header is constructed with the scheme name, Bearer, followed by a space and the access token itself.

The term Authentication is a general concept, but Authorization is the specific IETF-defined header name (RFC 7235). The Basic scheme is a different method that uses a Base64-encoded username:password string, which is not applicable here as a long-form token is provided.

Cisco Webex for Developers Documentation: The official documentation specifies the use of Bearer tokens for API calls. "To make an API call, you will need an access token. This token is passed with every API call in an HTTP header: Authorization: Bearer ."

Source: Cisco Webex for Developers, "Authentication"

URL: https://developer.webex.com/docs/api/getting-started#authentication

Internet Engineering Task Force (IETF) RFC 6750: This document defines the Bearer Token Usage for OAuth 2.0. Section 2.1 explicitly details the "Authorization Request Header Field" method as the primary way to transmit the token.

Source: IETF RFC 6750, "The OAuth 2.0 Authorization Framework: Bearer Token Usage," Section 2.1

URL: https://tools.ietf.org/html/rfc6750#section-2.1

Internet Engineering Task Force (IETF) RFC 7235: This standard defines the Authorization header field for HTTP/1.1, establishing it as the correct header for carrying authentication credentials.

Source: IETF RFC 7235, "Hypertext Transfer Protocol (HTTP/1.1): Authentication," Section 4.2

URL: https://tools.ietf.org/html/rfc7235#section-4.2