From 5fc0a11b4abcfec6f187dcc85cb3b3c2caf3b683 Mon Sep 17 00:00:00 2001 From: Vlada Dusek Date: Mon, 19 Oct 2026 20:33:19 +0200 Subject: [PATCH 1/3] docs: note that Standby removes the API token before forwarding --- sources/platform/actors/running/actor_standby.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/sources/platform/actors/running/actor_standby.md b/sources/platform/actors/running/actor_standby.md index 01103fb740..c0557cbca4 100644 --- a/sources/platform/actors/running/actor_standby.md +++ b/sources/platform/actors/running/actor_standby.md @@ -47,6 +47,8 @@ This approach can be useful if you cannot modify the request headers. https://rag-web-browser.apify.actor/search?query=apify&token=my_apify_token ``` +The platform removes the token from the request before forwarding it, so the token doesn't reach the Actor's code. If the Actor reads the `Authorization` header for its own authentication, send your Apify token in the `X-Apify-Authorization` header instead. + :::tip Scoped tokens You can use [scoped tokens](/integrations/api#limited-permissions) to send standby requests. This is useful for allowing third-party services to interact with your Actor without granting access to your entire account. From d243e1b4a8dcc125660d689a8c22e330b73643d7 Mon Sep 17 00:00:00 2001 From: Vlada Dusek Date: Tue, 20 Oct 2026 08:51:16 +0200 Subject: [PATCH 2/3] docs: point Standby Actors to the APIFY_TOKEN env var --- sources/platform/actors/running/actor_standby.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/sources/platform/actors/running/actor_standby.md b/sources/platform/actors/running/actor_standby.md index c0557cbca4..ebb4e68455 100644 --- a/sources/platform/actors/running/actor_standby.md +++ b/sources/platform/actors/running/actor_standby.md @@ -49,6 +49,8 @@ This approach can be useful if you cannot modify the request headers. The platform removes the token from the request before forwarding it, so the token doesn't reach the Actor's code. If the Actor reads the `Authorization` header for its own authentication, send your Apify token in the `X-Apify-Authorization` header instead. +To call the Apify API from the Actor's code, use the `APIFY_TOKEN` [environment variable](../development/programming_interface/environment_variables.md#system-environment-variables), the same as in a normal Actor run. + :::tip Scoped tokens You can use [scoped tokens](/integrations/api#limited-permissions) to send standby requests. This is useful for allowing third-party services to interact with your Actor without granting access to your entire account. From 4abc3d81395de46bdd1b26affe60586bbf7074e2 Mon Sep 17 00:00:00 2001 From: Vlada Dusek Date: Tue, 20 Oct 2026 08:54:58 +0200 Subject: [PATCH 3/3] docs: address the APIFY_TOKEN note to Standby Actor developers --- sources/platform/actors/running/actor_standby.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sources/platform/actors/running/actor_standby.md b/sources/platform/actors/running/actor_standby.md index ebb4e68455..92d0cad383 100644 --- a/sources/platform/actors/running/actor_standby.md +++ b/sources/platform/actors/running/actor_standby.md @@ -49,7 +49,7 @@ This approach can be useful if you cannot modify the request headers. The platform removes the token from the request before forwarding it, so the token doesn't reach the Actor's code. If the Actor reads the `Authorization` header for its own authentication, send your Apify token in the `X-Apify-Authorization` header instead. -To call the Apify API from the Actor's code, use the `APIFY_TOKEN` [environment variable](../development/programming_interface/environment_variables.md#system-environment-variables), the same as in a normal Actor run. +If you're developing a Standby Actor, use the token from the `APIFY_TOKEN` [environment variable](../development/programming_interface/environment_variables.md#system-environment-variables) to call the Apify API, as in any other Actor. :::tip Scoped tokens You can use [scoped tokens](/integrations/api#limited-permissions) to send standby requests. This is useful for allowing third-party services to interact with your Actor without granting access to your entire account.