Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions src/content/docs/fundamentals/api/how-to/restrict-tokens.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,16 @@ Client IP address restrictions control which IP addresses can make API requests

![IP Address filtering options](~/assets/images/fundamentals/api/ip-filter.png)

> [!NOTE]
> The client IP address filtering does not apply for the test command
> I.e. this can be done from ANY client
> ```
> curl -X GET "https://api.cloudflare.com/client/v4/user/tokens/verify" \
> -H "Authorization: Bearer <your-token>" \
> -H "Content-Type:application/json"
> ```


## Time to live (TTL) constraints

By default, tokens do not expire and are long lived. Defining a TTL sets when a token starts being valid and when a token is no longer valid. This is often referred to as `notBefore` and `notAfter`. Setting these timestamps limits the lifetime of the token to the defined period. Not setting the start date or `notBefore` means the token is active as soon as it is created. Not setting the end date or `notAfter` means the token does not expire.
Expand Down