From salesbuildr
Provides Salesbuildr API patterns: api-key header authentication, offset-based pagination (from/size), error handling, and rate limiting (500 req/10min). Use for CRM API integrations.
npx claudepluginhub wyre-technology/msp-claude-plugins --plugin salesbuildrThis skill uses the workspace's default tool permissions.
The Salesbuildr public API provides REST endpoints for managing CRM data. All requests require an API key and follow consistent patterns for pagination and error handling.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Generates or updates index.md listing all files and subdirectories in a target folder with 3-10 word descriptions from file contents. Use for indexing documentation directories.
The Salesbuildr public API provides REST endpoints for managing CRM data. All requests require an API key and follow consistent patterns for pagination and error handling.
Every API request must include the api-key header:
Headers:
api-key: ${SALESBUILDR_API_KEY}
Content-Type: application/json
API keys are generated in the Salesbuildr portal under Settings > API Keys.
https://portal.salesbuildr.com/public-api
All list endpoints use offset-based pagination:
| Parameter | Type | Default | Max | Description |
|---|---|---|---|---|
| from | number | 0 | - | Starting index (0-based offset) |
| size | number | 20 | 100 | Number of results per page |
Example: To get page 2 with 25 results per page:
GET /companies?from=25&size=25
| Status Code | Meaning | Resolution |
|---|---|---|
| 400 | Bad Request | Check request body/parameters |
| 401 | Unauthorized | Verify API key is correct |
| 403 | Forbidden | Check API key permissions |
| 404 | Not Found | Resource doesn't exist |
| 429 | Rate Limited | Wait and retry |
| 500 | Server Error | Retry after delay |
GET /companies?search=acme&from=0&size=25
GET /companies/12345
POST /contacts
Content-Type: application/json
{
"first_name": "John",
"last_name": "Doe",
"email": "john@example.com",
"company_id": 12345
}
PATCH /opportunities/12345
Content-Type: application/json
{
"stage": "proposal",
"value": 15000
}