# Do I Need To Provide Security Context in the Tokens API?

**URL:** <https://community.embeddable.com/t/do-i-need-to-provide-security-context-in-the-tokens-api/173>\
**Category:** FAQs\
**Created:** [March 6, 2026, 3:55pm UTC](https://community.embeddable.com/t/do-i-need-to-provide-security-context-in-the-tokens-api/173 "2026-03-06T15:55:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chris-Embeddable](https://dub1.discourse-cdn.com/flex013/user_avatar/community.embeddable.com/chris-embeddable/32/24_2.png) [@Chris-Embeddable](https://community.embeddable.com/u/Chris-Embeddable)\
**Post date:** [March 6, 2026, 3:55pm UTC](https://community.embeddable.com/t/do-i-need-to-provide-security-context-in-the-tokens-api/173/1 "2026-03-06T15:55:06Z")

</div>

Technically, yes, `securityContext` is a required body value when using the tokens API to retrieve a token. Most users do need it, in order to enforce row level security. If row level security is not a concern, or you are enforcing it in some other way, or you’re testing, you can provide a blank object as the value and the tokens API will return successfully:

```auto
securityContext: {},

```