# API Token Authentication

**URL:** <https://developer.sailpoint.com/discuss/t/api-token-authentication/60182>\
**Category:** Connectivity Documentation Feedback\
**Tags:** va-con-docs\
**Created:** [June 2, 2024, 11:31am UTC](https://developer.sailpoint.com/discuss/t/api-token-authentication/60182 "2024-06-02T11:31:52Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![mdewallnc](https://avatars.discourse-cdn.com/v4/letter/m/e19b73/32.png) [@mdewallnc](https://developer.sailpoint.com/discuss/u/mdewallnc)\
**Post date:** [June 21, 2024, 10:03pm UTC](https://developer.sailpoint.com/discuss/t/api-token-authentication/60182/4 "2024-06-21T22:03:04Z")

</div>

Hi Ryan, thanks for quick response. Seems related to this person’s thread:

> [@WebService source fails when using accesstoken variable in HTTP Operations header](https://developer.sailpoint.com/discuss/t/webservice-source-fails-when-using-accesstoken-variable-in-http-operations-header/17561/2):
>
> Hi @dmcconnell_epsilon, I don’t see any direct issues based on the description you posted. But here are few things I would try to get better insights on what went wrong, You can take a look at the VA log and revise the [log level](https://community.sailpoint.com/t5/IdentityNow-Articles/Enabling-Connector-Logging-in-IdentityNow/ta-p/188107) to print everything (DEBUG/TRACE) to see if it prints the entire request for further debugging. Try the curl alternative which practically does the same thing, curl --location --request POST '\<Your\_endpoint\>' \ --header 'x-api-key: $application.accesstoken$' \ --hea…

The documentation I’m citing, it doesn’t say how the API key it can be used, I think that would be helpful.

Later in the documentation, it does hint at how some of these tokens are used (HTTP Header Section) but there some other secrets are referenced, not the API token.

On top of everything, it doesn’t actually work (I had to use the cert secret password like the last poster mentioned), which makes it really frustrating, because even if you found the right name for that variable in the docs somewhere, it doesn’t actually work. So it seems to be compound issue of missing documentation and a bug on top of it.

At least on the page I’m mentioned, it should be stated somewhere, "this can be referenced in later connection setups as $application.whatever$, which can be placed into HTTP Headers, POST bodies, etc.

---

_[View the full topic](https://developer.sailpoint.com/discuss/t/api-token-authentication/60182)._
