You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sources/platform/actors/running/actor_standby.md
+21-1Lines changed: 21 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Traditional Actors are designed to run a single job and then stop. They're mostl
14
14
However, in some applications, waiting for an Actor to start is not an option. Actor Standby mode solves this problem by letting you have the Actor ready
15
15
in the background, waiting for the incoming HTTP requests. In a sense, the Actor behaves like a real-time web server or standard API server.
16
16
17
-
## How do I know if Standby mode is enabled?
17
+
## How do I know if Standby mode is enabled
18
18
19
19
You will know that the Actor is enabled for Standby mode if you see the **Standby** tab on the Actor's detail page.
20
20
In the tab, you will find the hostname of the server, the description of the Actor's endpoints,
@@ -31,6 +31,26 @@ If you're using an Actor built by someone else, see its Information tab to find
31
31
32
32
Generally speaking, Actors in Standby mode behave as standard HTTP servers. You can use any of the existing [HTTP request methods](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods) like GET, POST, PUT, DELETE, etc. You can pass the input via [HTTP request query string](https://en.wikipedia.org/wiki/Query_string) or via [HTTP request body](https://developer.mozilla.org/en-US/docs/Web/HTTP/Messages#body).
33
33
34
+
## How do I authenticate my requests
35
+
36
+
To authenticate requests to Actor Standby, follow the same process as [authenticating requests to the Apify API](../../integrations/programming/api.md).
37
+
You can provide your [API token](../../integrations/programming/api.md#api-token) in one of two ways:
38
+
39
+
1._Recommended_: Include the token in the `Authorization` header of your request as `Bearer <token>`. This approach is recommended because it prevents your token from being logged in server logs.
0 commit comments