CtrlK
BlogDocsLog inGet started
Tessl Logo

juicebox-common-errors

Diagnose and fix Juicebox API errors. Trigger: "juicebox error", "fix juicebox", "debug juicebox".

61

Quality

53%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/saas-packs/juicebox-pack/skills/juicebox-common-errors/SKILL.md
SKILL.md
Quality
Evals
Security

Juicebox Common Errors

Overview

Juicebox provides AI-powered people search and analysis for recruiting and research workflows. API integrations cover search queries, profile enrichment, dataset operations, and quota management. Common errors include dataset format mismatches when uploading CSVs, analysis timeouts on large candidate pools, and quota exhaustion on free or starter plans. The quota system counts individual profile enrichments separately from search queries, which often surprises new integrators. This reference covers HTTP errors, business logic failures, and recovery strategies for reliable Juicebox integrations.

Error Reference

CodeMessageCauseFix
400Invalid query formatMalformed search query or empty filtersEnsure query is non-empty; validate filter field names
401invalid_api_keyAPI key missing or revokedVerify key at app.juicebox.ai > Settings > API
403quota_exceededPlan search limit reachedCheck quota in dashboard; upgrade plan or wait for reset
404Profile not foundCandidate removed or profile unavailableRe-run search to find updated profile data
408Analysis timeoutComplex query exceeded 60s limitReduce dataset size or narrow search filters
413Dataset too largeUpload exceeds 50MB or 100K row limitSplit dataset into smaller chunks before upload
422Invalid dataset formatCSV headers don't match expected schemaUse template from Juicebox docs; required: name, title, company
429Rate limitedExceeded 30 requests/minuteCheck Retry-After header; implement exponential backoff

Error Handler

interface JuiceboxError {
  code: number;
  message: string;
  category: "auth" | "rate_limit" | "validation" | "timeout";
}

function classifyJuiceboxError(status: number, body: string): JuiceboxError {
  if (status === 401 || status === 403) {
    return { code: status, message: body, category: "auth" };
  }
  if (status === 429) {
    return { code: 429, message: "Rate limited", category: "rate_limit" };
  }
  if (status === 408) {
    return { code: 408, message: body, category: "timeout" };
  }
  return { code: status, message: body, category: "validation" };
}

Debugging Guide

Authentication Errors

Juicebox API keys are passed via Authorization: Bearer header. Keys are scoped per workspace. If you receive 401, verify the key has not been rotated at app.juicebox.ai > Settings. A 403 indicates quota exhaustion, not a permissions issue -- check your plan's remaining searches.

Rate Limit Errors

The API enforces 30 requests/minute per key. Batch profile enrichment calls where possible. Use the Retry-After response header to determine wait time. For bulk operations, use the dataset upload endpoint instead of individual search queries.

Validation Errors

Dataset uploads require CSV format with headers matching the Juicebox schema: name, title, company are required columns. Optional enrichment columns include email, linkedin_url, and location. Files over 50MB or 100K rows are rejected -- split into chunks. Analysis queries that exceed 60 seconds timeout with 408; narrow filters by adding location, title, or company constraints to reduce result set size.

Error Handling

ScenarioPatternRecovery
Quota exceeded mid-batch403 after N successful callsTrack remaining quota via response headers; pause and resume
Dataset upload rejectedInvalid CSV formatDownload template, reformat, and retry
Analysis timeoutLarge candidate poolAdd location/title/company filters to narrow scope
Profile data stale404 on enrichmentRe-run search query to get current profile URLs
Rate limit during bulk search429 on sequential callsSwitch to dataset upload for bulk operations

Quick Diagnostic

# Verify API connectivity and key validity
curl -s -o /dev/null -w "%{http_code}" \
  -H "Authorization: Bearer $JUICEBOX_API_KEY" \
  https://api.juicebox.ai/v1/health

Resources

  • Juicebox Documentation
  • Juicebox API Reference

Next Steps

See juicebox-debug-bundle.

Repository
jeremylongshore/claude-code-plugins-plus-skills
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.