canonical: https://jentic.com/apis/mygadgetrepairs.com/mygadgetrepairs

# MyGadgetRepairs API

Jentic publishes the only available OpenAPI specification for MyGadgetRepairs API, keeping it validated and agent-ready. The MyGadgetRepairs API powers repair shop management for gadget, phone, and computer repair businesses, covering customers, repair tickets, ticket invoices, products, purchase orders, suppliers, and supporting reference data such as brands, models, and issue types. It exposes 31 endpoints across the /v1 base path, including ticket file upload flows for diagnostic photos and signed work orders. Auth is a header API key on https://api.mygadgetrepairs.com/v1.

## For AI agents

Manage repair shop customers, tickets, invoices, products, and suppliers in a MyGadgetRepairs account using a header API key.

## Scope

Does not handle payment processing, marketing campaigns, or accounting ledgers - use for repair shop ticket and customer management only.

## Capabilities

- Maintain the customer roster across create, read, update, and delete on `/customers/{customerId}`
- Open and progress repair tickets through their lifecycle on /tickets and `/tickets/{ticketId}`
- Attach diagnostic photos and signed forms to a repair ticket via the multipart upload flow
- Pull POS orders, ticket invoices, and tax rates for accounting reconciliation
- Read product catalog, brands, models, suppliers, and issue types as reference data for ticket intake
- List purchase orders and suppliers for parts ordering and inventory replenishment workflows

## Use cases

### Repair Intake Automation

Automate the front-counter intake flow when a customer drops off a device. The integration looks up or creates a customer via /customers, fetches supported brands and models from /brands and /models for the device, then opens a ticket with POST /tickets including the issue type from /issueTypes. This collapses a multi-screen intake into one chained API call and produces a printable ticket in seconds.

Example prompt: Look up the customer by phone via GET /customers, then call POST /tickets with the customerId, brandId, modelId, and issueTypeId for the new repair.

### Photo and Document Upload to Tickets

Capture diagnostic photos and signed authorisation forms against a repair ticket using the two-step upload flow on `/tickets/{ticketId}/upload` and `/tickets/{ticketId}/upload/{uploadId}.` The integration initiates the upload, streams the file, then completes the upload to attach it to the ticket. This is essential for warranty disputes and insurance claims that need photographic evidence on file.

Example prompt: Call POST `/tickets/4421/upload` to initiate the upload, stream the JPEG, then POST `/tickets/4421/upload/{uploadId}` to complete and attach the photo.

### Daily Sales and Invoice Reconciliation

Reconcile a repair shop's daily revenue by pulling POS orders, ticket invoices, payment methods, and tax rates into an accounting system. The integration calls GET /posOrders, GET /ticketInvoices, GET /paymentMethods, and GET /taxRates and writes a journal entry per transaction. This eliminates manual end-of-day exports from the MyGadgetRepairs portal.

Example prompt: Fetch GET /posOrders and GET /ticketInvoices for today's date, join with GET /taxRates, and write each row into the bookkeeping ledger.

### Purchase Order and Supplier Management

Track parts ordering across suppliers using GET /purchaseOrders, GET `/purchaseOrders/{purchaseOrderId}`, and GET /suppliers. The integration surfaces overdue purchase orders to the shop manager and flags suppliers with consistently late deliveries. This turns the catalogue of POs into a procurement signal rather than a static list.

Example prompt: Fetch GET /purchaseOrders, filter to status open and order date older than 14 days, and return the list grouped by supplier from GET /suppliers.

### AI Agent Repair Concierge

An AI agent acts as a repair concierge for a chain of stores. It searches Jentic for MyGadgetRepairs ticket operations, loads the customer and ticket schemas, and chains GET /customers, POST /customers, and POST /tickets to take a customer's natural-language description of their broken device and produce a confirmed ticket. Jentic isolates the API key in the vault so the agent never holds shop credentials.

Example prompt: Search Jentic for 'open a phone repair ticket', load POST /tickets, and create a ticket for a Samsung Galaxy S22 with issue type 'Cracked Screen' for an existing customer looked up by phone number.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/customers` | Create a new shop customer |
| POST | `/tickets` | Open a new repair ticket |
| GET | `/tickets/{ticketId}` | Retrieve a repair ticket by ID |
| POST | `/tickets/{ticketId}/upload` | Initiate an attachment upload on a ticket |
| POST | `/tickets/{ticketId}/upload/{uploadId}` | Complete an attachment upload on a ticket |
| GET | `/ticketInvoices` | List invoices generated for tickets |
| GET | `/posOrders` | List point-of-sale orders |
| GET | `/purchaseOrders` | List parts purchase orders |

## Key resources

- **Customers** — List, create, retrieve, update, and delete shop customers.
- **Tickets** — Open and progress repair tickets, including file uploads for photos and forms.
- **TicketInvoices** — Read invoices generated against repair tickets for accounting reconciliation.
- **PosOrders** — List and inspect point-of-sale orders for retail and accessory sales.
- **Products** — Read product catalog data for ticket and POS line items.
- **PurchaseOrders** — List parts purchase orders against suppliers.
- **Suppliers** — Read supplier directory for procurement workflows.
- **Reference Data** — Read brands, models, issue types, statuses, payment methods, tax rates, custom fields, and users.

## Why Jentic

- **Setup:** Wiring the MyGadgetRepairs API by hand means learning its Authorization header API key auth and stepping through the ticket, upload, and order surface yourself. Through Jentic you install once, import the MyGadgetRepairs API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** MyGadgetRepairs puts the ticket id in the URL path (`/tickets/{ticketId}/upload`), so a rule can pin your agent to one ticket: it can read that ticket and attach uploads to it. You choose the operations it may call, so a call like creating a customer is not included unless you add it.
- **Credential handling:** Your MyGadgetRepairs API key is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'open a phone repair ticket' or 'attach a photo to a ticket', and Jentic returns the matching MyGadgetRepairs operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **GitHub REST API** — GitHub Issues can mirror repair tickets for engineering teams that prefer issue-tracker workflows alongside MyGadgetRepairs.
- **Stripe API** — Stripe handles online deposits and remote payments that settle into the MyGadgetRepairs ticket ledger.
- **HubSpot CRM Contacts API** — HubSpot Contacts provides a marketing and sales CRM layer over MyGadgetRepairs' shop-floor customer data.

## FAQ

### Why is there no official OpenAPI spec for MyGadgetRepairs API?

MyGadgetRepairs does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MyGadgetRepairs API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the MyGadgetRepairs API use?

The MyGadgetRepairs API uses an API key passed in the Authorization request header. Through Jentic, the key is stored in the encrypted credential vault and injected at execution time - agent code never holds the raw shop API key.

### Can I attach photos to a repair ticket with the MyGadgetRepairs API?

Yes. Use the two-step upload flow: POST `/tickets/{ticketId}/upload` to initiate the upload and obtain an uploadId, then POST `/tickets/{ticketId}/upload/{uploadId}` to complete it. The file is then attached to the specified ticket for diagnostic and warranty records.

### How do I open a repair ticket through Jentic?

Search Jentic for 'open a phone repair ticket', load the POST /tickets schema, and execute with the customerId, brandId, modelId, and issueTypeId. The reference IDs come from GET /brands, GET /models, and GET /issueTypes which can be fetched in parallel before the create call.

### What reference data is available in the MyGadgetRepairs API?

The spec exposes seven read-only reference endpoints: GET /issueTypes, GET /statuses, GET /models, GET /brands, GET /paymentMethods, GET /taxRates, and GET `/customFields/{type}.` These power dropdowns in any custom intake or POS UI built on top of the API.

### What are the rate limits for the MyGadgetRepairs API?

The published spec does not document explicit rate limits. Treat the API as rate-limited in production, implement exponential backoff on 429 responses, and contact MyGadgetRepairs for shop-specific limits before running large bulk syncs.

### Can I limit what my agent is allowed to do with the MyGadgetRepairs API?

Yes. Jentic One is self-hosted, so your own rules decide which MyGadgetRepairs operations and credentials the agent may use. Because the ticket id sits in the URL path, such as `/tickets/{ticketId}/upload`, you can pin the agent to a single ticket so it only reads that ticket and attaches uploads to it. You pick the exact operations it may call, so an action like POST /customers to create a customer stays off limits unless you add it.