-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Open
Labels
🐞 BugSomething isn't workingSomething isn't working🩺 Needs TriageNeeds attention of maintainersNeeds attention of maintainers
Description
crawl4ai version
latest
Expected Behavior
I successfully build a crawler request with BrowserConfig and CrawlerConfig with CSSExtraction, etc.
Now I want to build a webhook strategy to not wait for the crawler response so I used this from the documentation https://docs.crawl4ai.com/core/docker-deployment/#job-queue-webhook-api
Current Behavior
The request body of /crawl/job does not accept BrowserConfig and CrawlerConfig as /crawl does. How can I define them?
Is this reproducible?
Yes
Inputs Causing the Bug
const crawler_config_payload: CrawlerRunConfig = {
type: 'CrawlerRunConfig',
params: {...}
}
const crawl_payload = {
urls: searchURLs,
browser_config: browser_config_payload,
crawler_config: crawler_config_payload,
}
const response: {
results: {
extracted_content: string
}[]
} = await $fetch(`${config.crawl4AiUrl}/crawl/job`, {
method: 'post',
body: crawl_payload,
})
Steps to Reproduce
Code snippets
OS
macOS
Python version
DOcker
Browser
No response
Browser version
No response
Error logs & Screenshots (if applicable)
No response
Metadata
Metadata
Assignees
Labels
🐞 BugSomething isn't workingSomething isn't working🩺 Needs TriageNeeds attention of maintainersNeeds attention of maintainers