スキル一覧に戻る
Johnsonbros

housecall-pro-api-helper

by Johnsonbros

This is johnson bros plumbing & drain cleanings website

0🍴 0📅 2026年1月25日
GitHubで見るManusで実行

SKILL.md


name: housecall-pro-api-helper description: Helps with HouseCall Pro API integration, including building curl/HTTP requests, authentication setup, debugging API calls, understanding endpoints (customers, jobs, checklists, estimates), pagination, query parameters, and interpreting the housecall.v1.yaml OpenAPI spec. Use when the user mentions HouseCall Pro, needs to call HouseCall Pro APIs, troubleshoot API errors, or work with HouseCall Pro authentication. allowed-tools: Read, Grep, Bash, Write

⚡ aOa REQUIRED: Before using Grep tool, use aoa grep <term> via Bash instead. It's 10-100x faster and provides semantic search.

aoa grep <term>        # Use this, NOT Grep tool
aoa grep "a b c"       # Multi-term OR search
aoa grep -a a,b,c      # Multi-term AND search
aoa find <pattern>     # Use this for file discovery

HouseCall Pro API Helper

Specialized assistant for working with the HouseCall Pro v1 REST API.

Quick Start

Set your API key and make a test request:

POSIX/Linux/macOS:

export HOUSECALL_API_KEY="your-api-key"
curl --fail --include \
  "https://api.housecallpro.com/customers?page=1&page_size=10" \
  -H "Authorization: Token $HOUSECALL_API_KEY"

Windows PowerShell:

$Env:HOUSECALL_API_KEY="your-api-key"
curl.exe --fail --include `
  "https://api.housecallpro.com/customers?page=1&page_size=10" `
  -H "Authorization: Token $Env:HOUSECALL_API_KEY"

Core Concepts

Base URL: https://api.housecallpro.com

Authentication: Authorization: Token <api-key> (NOT Bearer)

Key Types:

  • Application API Key (preferred for most endpoints)
  • Company API Key (some endpoints require this)
  • OAuth Token (rare, not commonly used)

Pagination: Use page (default 1) and page_size (default 10)

Arrays in queries: Encode as param[]=value (repeat for each item)

Common Endpoints

EndpointPurposeKey Parameters
GET /customersSearch/list customersq, page, page_size, location_ids[]
GET /jobsList jobswork_status[], employee_ids[], customer_id
GET /checklistsGet checklistsjob_uuids[], estimate_uuids[]

Workflow

  1. Identify auth scheme - Check which key type the endpoint accepts
  2. Set Authorization header - Use Token <api-key> format
  3. Build URL - Base + endpoint + query params with proper encoding
  4. Test request - Use --fail --include to see status/headers
  5. Debug if needed - Check key type, param encoding, headers

Important Notes

  • Header is Authorization: Token <key> (NOT Bearer)
  • Match key type to endpoint's security requirements
  • location_ids ignored when X-Company-Id header is set
  • For POST/PUT/PATCH: use Content-Type: application/json

Additional Resources

Troubleshooting

401/403 errors: Verify you're using the correct key type (Application vs Company)

Array params not working: Ensure format is param[]=value repeated per item

Pagination issues: Check response metadata (total_pages, total_items) to navigate results

スコア

総合スコア

40/100

リポジトリの品質指標に基づく評価

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

0/10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

レビュー

💬

レビュー機能は近日公開予定です