Skip to content

Update search-job.md #5205

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Update search-job.md #5205

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
83aca6a
Update search-job.md
JV0812 Mar 25, 2025
eb2b763
Update docs/api/search-job.md
JV0812 Mar 28, 2025
e6423bb
Update docs/api/search-job.md
JV0812 Mar 28, 2025
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
2 changes: 1 addition & 1 deletion docs/api/search-job.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ An `HTTP 301 Moved error` suggests that the wrong endpoint was specified.

While the search job is running you need to request the job status based on the search job ID. The API keeps the search job alive by either polling for status every 20 to 30 seconds or gathering results. If the search job is not kept alive by API requests, it is canceled. When a search job is canceled for inactivity, you will get a 404 status.

You must enable cookies for subsequent requests to the search job. A 404 status (Page Not Found) on a follow-up request may be due to a cookie not accompanying the request.
You must include the `ACCESSID:ACCESSKEY` pair in every Search Job API request. A 404 status (Page Not Found) on a follow-up request may occur if the request is missing a required cookie or if the `ACCESSID:ACCESSKEY` pair is incorrect or omitted.

There's a query timeout after eight hours, even if the API is polling and making requests. If you are running very few queries, you may be able to go a little longer, but you can expect most of your queries to end after eight hours.

Expand Down