Moving a website to V2

Today a website reads its properties from apiv3.loop.software (network.api) and sends its enquiries and reads its team through V1 at api.loop.software. Everything a website needs is now in V2, at api.loop.software/v2, with one key.

The property data is unchanged: the same fields, with the same names, plus the office's name (teamName). What changes is the key, the addresses, the paging, and a few behaviours, all listed below. The old addresses keep working while you move.

1. Get a V2 key

One client key covers every office in the agency. To show one office's properties, filter with teamIds. A team id outside your key's agency answers 403 Forbidden.

curl "https://apiv3.loop.software/api/sales-properties?fetch=20" \
  -H "x-api-key: 3f2a9c1e-0000-0000-0000-000000000000"

curl "https://api.loop.software/v2/website/sales/properties?limit=20" \
  -H "Authorization: Bearer lp_live_…"

2. Change the addresses

Properties and teams

A property's {id} is the same lifecycle id as today: salesLifecycleId or lettingsLifecycleId in search results.

Enquiries

3. Property search

Parameters. All of today's parameters work as before, with two changes: limit replaces fetch (1 to 100, default 20), and teamIds (team ids) replaces teamAPIList (other teams' keys).

So lat, lng, range, searchText, minBeds, minPrice, maxPrice, minRent, maxRent, propertyTypes, propertyTypeList, letPeriod, webListingStatuses, refId, roleType, sortOrder and the …Only and exclude… switches are unchanged.

The response. Results come in V2's paging envelope. Each item has the same fields as today, plus teamName: the office the property belongs to, alongside its phone and email, so you can route a lead without another call.

{
  "results": [ … ],
  "totalResults": 57, "returnedResults": 20, "more": true,
  "offset": 0, "perPage": 20, "page": 1, "totalPages": 3
}

{
  "data": [
    { "webMarketingStatus": "forSale", "propertyType": "semiDetached",
      "teamName": "Example Estates Harrogate", … }
  ],
  "pagination": { "offset": 0, "limit": 20, "hasMore": true, "total": 57 }
}

Search form ranges

GET /v2/website/sales/properties/search-stats and GET /v2/website/lettings/properties/search-stats return today's figures for your search form's dropdowns, with the same names: totalCount, minPrice, maxPrice and avgPrice (minRent, maxRent and avgRent for lettings), minBedrooms and maxBedrooms. They cover the same properties the search shows, and take teamIds in place of teamAPIList.

V2 adds minBathrooms, maxBathrooms and propertyTypes: the property types you have on the market, with how many of each. Each value is what the search's propertyTypes parameter takes, so a dropdown built from it never offers a type with nothing to show.

{
  "totalCount": 57,
  "minPrice": 125000, "maxPrice": 650000, "avgPrice": 310500.5,
  "minBedrooms": 1, "maxBedrooms": 5,
  "minBathrooms": 1, "maxBathrooms": 3,
  "propertyTypes": [
    { "value": "detached", "name": "Detached House", "count": 20 },
    { "value": "flat", "name": "Flat", "count": 15 },
    { "value": "semiDetached", "name": "Semi-Detached House", "count": 22 }
  ]
}

With nothing on the market, every figure is 0 and propertyTypes is empty. Today's call answers with an empty body.

4. Property pages

GET /v2/website/sales/properties/{id} and GET /v2/website/lettings/properties/{id} return the same fields as today's detail calls, plus teamName.

To look a property up by its website listing id, as today's by-listing calls do, use GET /v2/website/sales/properties/by-listing/{listingId} or GET /v2/website/lettings/properties/by-listing/{listingId}. They return the property exactly as the calls above do.

5. Teams

GET /v2/website/teams lists every active office your key covers, in name order. GET /v2/website/teams/{id} returns one. With a client key, one call gives you every office, where V1 needed a key per office.

curl "https://api.loop.software/team" -H "x-api-key: <first office's key>"
curl "https://api.loop.software/team" -H "x-api-key: <second office's key>"
# …and so on for each office

curl "https://api.loop.software/v2/website/teams" \
  -H "Authorization: Bearer lp_live_…"

Each team has the fields V1's team returns, with the same names, and these changes:

6. Enquiries and valuation requests

Send the same details as today. The field names match what V2 returns when you read an enquiry back. Call the API from your server, never from the browser: anyone who can see the key can use it.

curl -X POST "https://api.loop.software/v2/sales/enquiries" \
  -H "Authorization: Bearer lp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "salesLifecycleListingId": 99120,
    "type": "viewing",
    "firstName": "Sam",
    "lastName": "Example",
    "emailAddress": "[email protected]",
    "preferredTimes": ["2026-11-07T10:00:00Z"]
  }'

$response = wp_remote_post('https://api.loop.software/v2/sales/enquiries', [
    'headers' => [
        'Authorization' => 'Bearer ' . LOOP_API_KEY,
        'Content-Type' => 'application/json',
    ],
    'body' => wp_json_encode([
        'salesLifecycleListingId' => 99120,
        'type' => 'viewing',
        'firstName' => 'Sam',
        'lastName' => 'Example',
        'emailAddress' => '[email protected]',
        'preferredTimes' => ['2026-11-07T10:00:00Z'],
    ]),
]);

if (wp_remote_retrieve_response_code($response) !== 201) {
    // A 400 lists each problem under the field it's about.
}

const res = await fetch("https://api.loop.software/v2/sales/enquiries", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.LOOP_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    salesLifecycleListingId: 99120,
    type: "viewing",
    firstName: "Sam",
    lastName: "Example",
    emailAddress: "[email protected]",
    preferredTimes: ["2026-11-07T10:00:00Z"],
  }),
});

if (res.status !== 201) {
  // A 400 lists each problem under the field it's about.
}

A valuation request with a client key also needs teamId: the office the request is for. It can include propertyType and bedrooms too.

7. Errors

V2 errors come back as ProblemDetails JSON, with a title, a detail and the status.

Checklist

1. Get a client key with the Website preset.
2. Send it as Authorization: Bearer … instead of x-api-key.
3. Change the addresses (step 2).
4. Swap fetch for limit and teamAPIList for teamIds.
5. Read results from data and pagination.
6. Build the search form's ranges and property type list from search-stats.
7. Compare enum values with names, not numbers.
8. Expect 404 for a property page that isn't listed on the website.
9. Move the enquiry forms to the V2 field names, and expect 201.
10. Handle 503 from search as "try again", not as an empty page.