Jenkins API Token 1 (from UI "Add new Token" button):
  User: guilhermesilva
  Token: 1168067a586dbf2545ec65de94c754a8e8
  UUID: (UI-generated, name "ci-scope-2026-09-29")
  Created: 2026-09-29
  Verified: HTTP 200 /me/api/json (2026-09-29 12:16Z)
  Usage: curl -u guilhermesilva:1168067a586dbf2545ec65de94c754a8e8 https://jenkins.salesforce.ipiranga.io/api/json

Jenkins API Token 2 (from POST /generateNewToken):
  User: guilhermesilva
  Token: 11cb05bd0f8d87ff565d09efe46b3b9012
  UUID: dabe0419-75bb-4b03-91bb-fef456f72b86
  Token name: "Token created on 2026-09-29T12:15:48.798095377Z"
  Created: 2026-09-29
  Verified: HTTP 200 /me/api/json (2026-09-29 12:16Z)
  Usage: curl -u guilhermesilva:11cb05bd0f8d87ff565d09efe46b3b9012 https://jenkins.salesforce.ipiranga.io/api/json

Both tokens are persistent — independent of password rotation.
Token 1 (1168...) = primary (named, traceable).
Token 2 (11cb...) = backup.