Skip to content

Commit e15fe0c

Browse files
authored
Inform client-filtering doesn't apply to test-command
1 parent 754ea20 commit e15fe0c

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

src/content/docs/fundamentals/api/how-to/restrict-tokens.mdx

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,16 @@ Client IP address restrictions control which IP addresses can make API requests
1717

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

20+
> [!NOTE]
21+
> The client IP address filtering does not apply for the test command
22+
> I.e. this can be done from ANY client
23+
> ```
24+
> curl -X GET "https://api.cloudflare.com/client/v4/user/tokens/verify" \
25+
> -H "Authorization: Bearer <your-token>" \
26+
> -H "Content-Type:application/json"
27+
> ```
28+
29+
2030
## Time to live (TTL) constraints
2131
2232
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.

0 commit comments

Comments
 (0)