PARTNER API

Partner Inventory API.

A read-only JSON API for independent dealers who want to show FEM machines and attachments on their own website. You keep your customers and your own margin; we keep the listing data accurate. Everything is served over HTTPS from fullyequippedmachinery.com.

Getting a key

Keys are issued by hand. Email sales@fullyequippedmachinery.com with your dealership name, the website you will publish on, and whether you also want attachment pricing. We will send a key that looks like femk_live_….

Treat the key as a password. Call the API from your server, never from browser JavaScript — a key in front-end code is a key you have published. If a key is exposed, tell us and we will revoke it and issue a new one. We cannot read your key back to you; only a one-way hash of it is stored.

Authentication

Send the key as a bearer token on every request:

curl -H "Authorization: Bearer femk_live_…" \
  https://fullyequippedmachinery.com/api/partners/v1/machines

Keys are not accepted in query strings. Query strings end up in access logs, browser history and Referer headers, which is how keys leak.

Endpoints

`GET /machines`

Every FEM machine currently available, with specifications, installed equipment, location, retail pricing in CAD and USD, and absolute photo URLs. Machines that have sold are removed from the response rather than flagged, so a listing driven by this endpoint disappears instead of going stale.

{
  "count": 4,
  "generated_at": "2026-08-11T09:30:00.000Z",
  "machines": [
    {
      "id": "1",
      "fem_url": "https://fullyequippedmachinery.com/equipment/…",
      "year": 2021,
      "make": "Hitachi",
      "model": "ZX135USK-6",
      "hours": 2950.3,
      "ton_class": "13.5 Ton",
      "status": "available",
      "location": "Surrey BC",
      "price": { "basis": "retail", "cad": 159000, "usd": 112900 },
      "specifications": { "equipmentType": "Excavator", "…": "…" },
      "installed_equipment": ["Hydraulic quick coupler", "…"],
      "shipping": null,
      "photos": [
        { "url": "https://…/api/catalog-media/1/0", "alt": "…", "kind": "finished_photo", "sort": 0 }
      ]
    }
  ]
}

`GET /machines/{id}`

A single machine, for refreshing one listing without re-pulling the catalogue. Returns 404 if the unit is not currently available.

`GET /machines/pricing`

Your margin. Confidential. What you earn on a machine sale, if a rate has been agreed with you. Requires the pricing scope.

You list machines at FEM's retail price, so this is never a display number — it is your economics on a completed sale, and it is returned two ways because it settles two ways. dealer_net is what you pay FEM if you fulfil the sale. margin is what FEM pays you as commission if we fulfil it. They are the same spread from either end, so one agreed rate covers both and you do not have to decide who ships before you can quote.

{
  "pricing_agreed": true,
  "discount_percent": <your agreed rate>,
  "machines": [
    {
      "id": "1",
      "make": "Hitachi",
      "model": "ZX135USK-6",
      "retail":     { "cad": 159000, "usd": 112900 },
      "dealer_net": { "cad": ..., "usd": ... },
      "margin":     { "cad": ..., "usd": ... }
    }
  ]
}

Retail is shown because it is already public. Your rate is set in your dealer agreement, not here.

Like all pricing endpoints, this one sends no CORS headers, is not readable from a browser, and is served no-store. Machine and attachment rates are negotiated separately — you may have one and not the other.

`GET /attachments`

The published attachment product line — buckets, thumbs, couplers, breakers and tilt-rotators — grouped into families, each with its SKUs, carrier class and list price. This endpoint carries list price only and is safe to render on a public page.

`GET /attachments/pricing`

Your cost. Confidential. Returns your dealer-net price and margin per SKU alongside list, if a discount has been agreed with you. Requires the pricing scope on your key. Same two-sided settlement as machine pricing: dealer_net if you fulfil, margin if we do.

This endpoint is for your quoting and purchasing systems. It sends no CORS headers and is not reachable from a browser on your domain, and it is served no-store so nothing caches it. If no discount has been agreed yet you will get "pricing_agreed": false and list prices — never a zero-discount price presented as wholesale. Do not render these numbers on a public page.

`GET /me`

Confirms your key works and reports its scopes and rate-limit budget. Useful as a health check.

Photos

Photo URLs point back at FEM and should be hotlinked, not downloaded and re-hosted. Every image is served through a reviewed manifest, so if a photo is corrected or withdrawn, your site picks up the change automatically. A copy on your server would not.

Caching and rate limits

Cache responses for five minutes. Listing responses are sent with Cache-Control: private, max-age=300 and are the freshest we promise. Keys are limited to 1,200 requests per hour; every response carries X-RateLimit-Limit and X-RateLimit-Remaining, and exceeding it returns 429. Cache properly and you will not come close.

Errors

Errors return a JSON body of the form { "error": { "code": "…", "message": "…" } } with codes missing_credential and invalid_credential (401), insufficient_scope (403), not_found (404), rate_limited (429) and unavailable (503). A 503 means we could not validate our own catalogue and are refusing to serve a partial one — retry shortly.

Building it with AI

No developer? An AI assistant can build this integration for you. The prompt below is written for that — it carries the endpoints, the response shapes and the safety rules, so the tool does not put your key somewhere public, misprice your listings, or invent inventory that does not exist.

Copy it, replace the two <<< FILL THIS IN >>> lines with what your site is built with and where it is hosted, then paste it into ChatGPT, Claude, Cursor, Copilot, Lovable, Replit — whichever tool you use.

Leave the placeholder FEM_API_KEY in place. Do not paste your real key into a chat window. The prompt already tells the assistant to read the key from an environment variable and to show you where to put it on your platform.

Download as .txt

I am an independent equipment dealer. I want to display Fully Equipped
Machinery's used excavator inventory and attachment product line on my own
website, using their Partner Inventory API. Please build this integration for
me.

MY SETUP
- My website is built with: <<< FILL THIS IN: e.g. WordPress, Shopify, Wix,
  Squarespace, Next.js, plain HTML, custom PHP >>>
- My site is hosted on: <<< FILL THIS IN: e.g. GoDaddy, SiteGround, Vercel,
  Netlify, my own server >>>

Before writing any code, ask me anything you need to know about my setup, and
tell me plainly if my platform cannot do what this integration requires.

=== THE API ===

Base URL:  https://fullyequippedmachinery.com/api/partners/v1

Authentication: every request needs this header, where FEM_API_KEY is a secret
key Fully Equipped Machinery issued to me and I will supply separately:

    Authorization: Bearer FEM_API_KEY

The key is NOT accepted in a query string. It must be sent as a header.

ENDPOINTS I WANT TO USE

  GET /machines
      Every used machine currently available, at Fully Equipped Machinery's
      retail price. This is the main one. Returns:
      {
        "count": 4,
        "generated_at": "2026-08-12T00:00:00.000Z",
        "machines": [
          {
            "id": "1",
            "fem_url": "https://fullyequippedmachinery.com/equipment/...",
            "year": 2021,
            "make": "Hitachi",
            "model": "ZX135USK-6",
            "hours": 2950.3,
            "ton_class": "13.5 Ton",
            "status": "available",
            "location": "Surrey BC",
            "price": { "basis": "retail", "cad": 159000, "usd": 112900 },
            "specifications": {
              "equipmentType": "Excavator",
              "auxHydraulics": "Yes - lines plumbed to arm end",
              "engineManufacturer": "Isuzu",
              "engine": "AR-4JJ1X (Isuzu 4JJ1)",
              "engineFamily": "Pending verification",
              "power": "78.5 kW (105 hp)",
              "emissions": "US EPA Tier 4 Final"
            },
            "installed_equipment": ["Hydraulic quick coupler", "Hydraulic thumb"],
            "shipping": null,
            "photos": [
              {
                "url": "https://fullyequippedmachinery.com/api/catalog-media/1/0",
                "alt": "Hitachi ZX135USK-6 - photo 1",
                "kind": "finished_photo",
                "sort": 0
              }
            ]
          }
        ]
      }

  GET /machines/{id}
      One machine by its id. Returns 404 if that unit is no longer available.

  GET /attachments
      Attachment product line - buckets, thumbs, couplers, breakers,
      tilt-rotators - grouped into families, each with its SKUs at list price.
      Returns:
      {
        "count": 42,
        "sku_count": 225,
        "families": [
          {
            "id": "excavator-buckets-digging-bucket",
            "name": "Digging Bucket",
            "segment": "excavator",
            "category": "Buckets",
            "description": "...",
            "variants": [
              {
                "sku": "FEMCUB1015",
                "label": "10-15T",
                "carrier_class": "10-15T",
                "price": { "basis": "retail", "cad": 6298, "usd": 4999 }
              }
            ]
          }
        ]
      }

  GET /me
      Confirms my key works and reports its permissions. Use this first to
      verify the connection before building anything else.

ENDPOINTS TO IGNORE
There are also /machines/pricing and /attachments/pricing endpoints. They
return my confidential cost and commission. DO NOT call them from my website
and DO NOT build anything that displays them. They are for my back office only.

=== HARD RULES - THESE ARE NOT OPTIONAL ===

1. THE API KEY MUST NEVER REACH THE BROWSER.
   Call the API from my server, never from client-side JavaScript. Do not put
   the key in a React component, an inline <script>, a data attribute, or any
   file the browser downloads. Anyone can read those, and a leaked key gets
   revoked.
   - Store the key in an environment variable or my platform's secret store.
   - If my platform genuinely cannot make server-side requests, STOP and tell
     me that plainly instead of putting the key in the browser. Suggest a
     workaround such as a scheduled job that writes the data to a static file.

2. DISPLAY THE RETAIL PRICE EXACTLY AS RETURNED.
   Use the `price.cad` and `price.usd` values as they come. Do not add a
   markup, do not recalculate, do not round. My margin is handled separately
   between me and Fully Equipped Machinery; the price on my website must match
   theirs.

3. CACHE FOR 5 MINUTES. DO NOT POLL IN A LOOP.
   Cache each response for 300 seconds and reuse it. My key is limited to 1200
   requests per hour and every response includes X-RateLimit-Remaining. A page
   that calls the API on every visitor load will blow through the limit.

4. HOTLINK THE PHOTOS. DO NOT DOWNLOAD AND RE-HOST THEM.
   Use the photo `url` values directly in my <img> tags. They are already
   absolute URLs. If Fully Equipped Machinery corrects or withdraws a photo,
   hotlinking means my site picks up the change automatically.

5. NEVER INVENT INVENTORY.
   Only show machines the API actually returns. If the API returns 4 machines,
   show 4. Do not use placeholder or sample machines anywhere in the live site.
   Sold machines disappear from the response - that is intentional, and my page
   must handle the list shrinking.

6. FAIL QUIETLY AND VISIBLY TO ME, NOT TO MY CUSTOMERS.
   If the API is unreachable or returns an error, show the last cached data if
   available, otherwise hide the section entirely. Never show a raw error, a
   stack trace, or an empty broken grid to a visitor. Log the error where I can
   find it.

=== WHAT I WANT BUILT ===

a) A server-side function that fetches from the API with my key, with the
   5-minute cache and sensible error handling.

b) An inventory listing page showing all available machines as cards: primary
   photo, year, make, model, hours, ton class, location, and retail price.

c) A detail page or modal for a single machine: the full photo gallery,
   specifications, and installed equipment.

d) An attachments page grouped by family, with each family's SKUs, carrier
   class and list price in a table.

e) An inquiry form on each listing that sends the enquiry TO ME, with the
   machine's id, year, make and model attached so I know what they are asking
   about. Leads are mine; do not send them to Fully Equipped Machinery.

f) A "Sourced by Fully Equipped Machinery" credit on any page showing this
   inventory. This is required by my agreement with them.

=== HOW TO PROCEED ===

1. Tell me what you need to know about my site before you start.
2. Show me where to put the API key on my specific platform, step by step, as
   if I am not a developer.
3. Give me the complete code, file by file, with the full path of each file and
   whether I am creating it or editing it.
4. Give me a way to test the connection first - a single call to /me that
   prints the result - so I can confirm the key works before building pages.
5. Tell me exactly how to verify each piece works once installed.

Explain each step in plain language. Assume I can copy and paste files and
follow instructions, but that I am not a programmer and cannot debug code on
my own.

Scroll inside the box to read it all. Replace the two lines marked <<< FILL THIS IN >>> before you paste it into your AI tool.

Ask it to get the /me test working first. Once your dealership name comes back, add the machine listing, then the detail pages, then attachments. If something breaks, paste the exact error back to the assistant.

Terms of use

Access is granted on these terms, and a key may be revoked if they are not met:

Listings sourced from this API must be attributed to Fully Equipped Machinery.
List machines and attachments at the retail price the API returns. Your rate is your margin, not a price to advertise.
Dealer-net pricing and margin are confidential. They may be used to quote, buy and settle, and may not be published, rendered on a web page, or shared outside your dealership.
Do not republish FEM inventory to third-party marketplaces or auction sites without written permission.
Availability and pricing are not a guarantee of sale. Confirm with FEM before committing to a customer.
Do not share your key, and do not use it from browser-side code.

Contact

Integration questions and key requests: sales@fullyequippedmachinery.com or 1 888-334-6467.

Browse inventory Browse attachments Return home