MyGadgetRepairs API

Name: MyGadgetRepairs API
Brand: MyGadgetRepairs API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMCustomer SupportapiKey31 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the MyGadgetRepairs API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MyGadgetRepairs API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with MyGadgetRepairs API.

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

GET STARTED

Start building with MyGadgetRepairs API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use MyGadgetRepairs API for, with concrete tasks.

★ 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.

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.

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.

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.

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.

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

31 endpoints — jentic publishes the only available openapi specification for mygadgetrepairs api, keeping it validated and agent-ready.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

MyGadgetRepairs API keys are stored encrypted in the Jentic vault (MAXsystem). Agents call shop operations through Jentic and the Authorization header is injected at execution time — the raw key never reaches agent context, prompts, or logs.

Intent-based discovery

Agents search by intent (e.g., 'open a phone repair ticket') and Jentic returns matching operations such as POST /tickets and the upload flow with their JSON Schemas, so the agent can chain customer lookup, ticket creation, and photo upload without reading docs.

Time to first call

Direct MyGadgetRepairs integration: 3-5 days for header auth, two-step upload handling, and reference data caching. Through Jentic: under 2 hours — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

GitHub REST API

GitHub Issues can mirror repair tickets for engineering teams that prefer issue-tracker workflows alongside MyGadgetRepairs.

Use GitHub Issues to track internal R&D or warranty escalations linked from a MyGadgetRepairs ticket ID.

Complementary

Stripe API

Stripe handles online deposits and remote payments that settle into the MyGadgetRepairs ticket ledger.

Use Stripe for online repair deposits before the device arrives, then mark the corresponding MyGadgetRepairs ticket as paid.

Complementary

HubSpot CRM Contacts API

HubSpot Contacts provides a marketing and sales CRM layer over MyGadgetRepairs' shop-floor customer data.

Sync MyGadgetRepairs customers into HubSpot Contacts for follow-up campaigns, NPS surveys, and repeat-business automation.

FAQs

Specific to using MyGadgetRepairs API through Jentic.

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 at https://app.jentic.com/sign-up.

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.