Summary

Fixes #2582.

The startExtract and extract methods in the v2 JS SDK did not accept webhook configuration in their TypeScript type definitions, even though the Firecrawl API supports webhooks for extract jobs and other async methods (crawl, batchScrape) already include it.

• Added webhook?: string | WebhookConfig | null to prepareExtractPayload() parameter type
• Forward webhook to the request body, matching the pattern used in crawl.ts (line 39) and batch.ts (line 37)
• Types flow automatically to startExtract() and extract() via Parameters<typeof prepareExtractPayload>[0]

Usage after fix:

const result = await firecrawl.startExtract({
  urls: ['https://example.com'],
  schema: mySchema,
  prompt: 'Extract data',
  webhook: {
    url: 'https://example.com/webhook',
    metadata: { jobId: '123' },
    events: ['completed', 'failed'],
  },
});

Test plan

• Verified type signature matches CrawlOptions.webhook and BatchScrapeOptions.webhook patterns
• Verified webhook is forwarded to request body using the same if (args.webhook != null) guard as crawl.ts and batch.ts

Summary by cubic

Adds webhook support to startExtract and extract in the v2 firecrawl JS SDK so extract jobs can send callbacks. Aligns extract with crawl and batchScrape.

• Bug Fixes
  • Accepts webhook?: string | WebhookConfig | null in prepareExtractPayload, flowing to startExtract/extract.
  • Forwards webhook to the request body when provided.

^{Written for commit a49b967. Summary will update on new commits.}