repairshopr-search

name	repairshopr-search
description	Global search across RepairShopr entities (customers, tickets, invoices, etc.)
license	MIT
compatibility	opencode
metadata	{"audience":"all users","api":"GET /search"}

What I do

I perform a global search across multiple entity types in RepairShopr. I can search customers, contacts, assets, leads, tickets, invoices, estimates, products, purchase orders, vendors, reports, and wiki pages. Results are returned with type indicators.

When to use me

Use this when:

• You need to find something by keyword without knowing the entity type
• Building a universal search box
• Looking up a customer, ticket, or order by name, email, or partial info
• Quick lookup across the entire RepairShopr database

How to use

Required API base URL:

• VITE_REPAIRSHOPR_SUBDOMAIN
• VITE_REPAIRSHOPR_API_KEY

Permissions: Additional permissions required depending on result types (Customers - List/Search for customers/assets/contacts, Leads - List/Search for leads, Invoices - List/Search for invoices, etc.)

Search (GET /search)

• query (string, optional) - Search term. The documentation shows query as integer but that's likely a mistake; use string.

Example call:

const result = await skill({ name: "repairshopr-search" }, {
  query: "John Doe"
})

// Or with partial info
const result2 = await skill({ name: "repairshopr-search" }, {
  query: "555-123"
})

Response includes:

{
  "quick_result": null,
  "results": [
    {
      "table": {
        "_id": 1,
        "_type": "customer",
        "_index": "customers",
        "_source": {
          "table": {
            "firstname": "Walkin",
            "lastname": "Customer",
            "email": "[e-mail]",
            "phones": [...]
          }
        }
      }
    },
    {
      "table": {
        "_type" 
        
      
    
    
  

The results array contains heterogeneous objects; each has a _type field indicating the entity type ("customer", "contact", "asset", "lead", "ticket", "invoice", "estimate", "product", "purchase_order", "vendor", "report", "wiki", etc.). The actual data is nested under _source.

Important

• The search returns mixed types; you must check _type to interpret each result
• Pagination? Not documented; likely returns top results only
• Permissions filter what you can see; you won't see entities you lack access to
• Search likely uses Elasticsearch or similar; supports partial matching

Related skills

• repairshopr-customer-search - Customer-specific search
• repairshopr-ticket - For detailed ticket lookups after finding via search