What is provided to the client to identify the authenticated session in subsequent API calls after authenticating to the Cisco DNA Center API?

Upon successful authentication, the Cisco DNA Center API provides an authentication token (typically a JWT or similar string) that the client must include in the header of all subsequent API calls to maintain the authenticated session and access protected resources. This token acts as a proof of identity without re-sending credentials.

While X.509 certificates can be used for client authentication in some APIs, Cisco DNA Center typically uses token-based authentication for session management after initial login.

Session cookies are more common in web browser-based interactions for session management, but API clients typically use explicit tokens in headers.

Sending the username and password with every API call is highly insecure and inefficient, and not how session management is handled after initial authentication.