/get/resort_type/{id} - Get resort type by ID

Overview

The /get/resort_type/{id} endpoint retrieves detailed information about a specific resort type category by its ID.

Purpose

• Fetch resort type information including title and metadata
• Get list of resorts belonging to this type
• Access resort type images
• Retrieve automatic categorization data

Endpoint

GET /get/resort_type/{id}

Parameters

Path parameters

id (string, required)

The resort type's WordPress ID. Can be provided with or without the "1_" prefix.

Formats:

• {wp_id} - WordPress ID only (e.g., "456")
• 1_{wp_id} - Legacy format with site prefix (e.g., "1_456")

Examples:

• id=456 - Resort type with WordPress ID 456
• id=1_456 - Same resort type using legacy format (prefix is stripped)

Validation: Must be numeric or in format "1{number}". The "1" prefix is automatically removed if present.

---

Query parameters

sourceFields (string, optional)

Return only specific fields from the _source object using dot notation (comma-separated).

Purpose: Optimize response payload size by requesting only needed fields

Examples:

• sourceFields=title,resorts
• sourceFields=title,images,automatic
• sourceFields=title,type

---

Response format

Success response structure

{
  "_index": "fnugg_blog",
  "_type": "resort_type",
  "_id": "1_456",
  "_version": 1,
  "found": true,
  "_source": {
    "id": 456,
    "title": "Alpint",
    "type": "resort_type",
    "resorts": [14, 12, 89, 102, 73],
    "images": [
      {
        "url": "https://example.com/alpine-skiing.jpg",
        "caption": "Alpint skiløping",
        "width": 1920,
        "height": 1080
      }
    ],
    "automatic": "alpine"
  }
}

Error response (not found)

{
  "error": "Resort type with ID '999' was not found.",
  "error_key": "resort_type_not_found",
  "id": "999"
}

---

Response fields

Top level fields

• _index (string): Index name, always "fnugg_blog"
• _type (string): Type name, always "resort_type"
• _id (string): Resort type's ID in format "1_{wp_id}"
• _version (integer): Document version, always 1
• found (boolean): Whether resort type was found, always true on success
• _source (object): The resort type data object

_source fields

Basic information

• id (integer): Resort type's WordPress ID (without "1_" prefix)
• title (string): Resort type name/category (e.g., "Alpint", "Langrenn", "Familie")
• type (string): Content type, always "resort_type"

Related Data

• resorts (array	string): Array of resort site_ids belonging to this type, or empty string "" if no resorts

  • When no resorts: empty string "" (not empty array)

Media

• images (array): Resort type representative images
  • Each object may contain: url (string), caption (string), width (integer), height (integer)

Categorization

• automatic (string): Automatic categorization identifier/slug (e.g., "alpine", "cross_country", "family")
  • Used for programmatic filtering and categorization

---

Example requests

Get complete resort type data

GET /get/resort_type/456

Returns all fields for resort type with WordPress ID 456.

---

Get resort type with legacy ID format

GET /get/resort_type/1_456

Returns same result as above (the "1_" prefix is automatically stripped).

---

Get resort type with specific fields only

GET /get/resort_type/456?sourceFields=title,resorts

Returns only title and list of resort IDs.

---

Get resort type basic info

GET /get/resort_type/456?sourceFields=title,automatic,images

Returns basic information with categorization and images.

---

Example resort types

Common resort type categories in the Norwegian ski resort context:

• Alpint - Alpine/downhill skiing resorts (automatic: "alpine")
• Langrenn - Cross-country skiing areas (automatic: "cross_country")
• Familie - Family-friendly resorts (automatic: "family")
• Terrengpark - Terrain park focused resorts (automatic: "park")
• Offpiste - Off-piste/backcountry skiing (automatic: "offpiste")

---

Use Cases

1. Filter resorts by type: Use the resorts array to get all resorts of a specific type
2. Category navigation: Use sourceFields=title,automatic for filtering UI
3. Resort type statistics: Combine with resort data using the resorts array
4. Display resort type pages: Use complete data for category landing pages
5. Faceted search: Use automatic field value for search filtering
6. Resort categorization: Show which types each resort belongs to

---

Notes

• The id parameter accepts both formats: 456 or 1_456 (legacy format)
• The "1_" prefix is always stripped if provided, as all resort types belong to site_id 1
• Resort types not found will return a 200 status with error object
• The resorts field contains site_ids that can be used with /get/resort/{id} or /search?include=...
• Note: When no resorts belong to a type, resorts is an empty string "" rather than an empty array []
• A single resort can belong to multiple resort types (e.g., both "Alpint" and "Familie")
• The images array may be empty if the resort type has no representative images
• The automatic field provides a programmatic identifier for filtering (e.g., used in faceted search)
• Resort type titles are typically in Norwegian (e.g., "Alpint" for alpine skiing)
• The sourceFields parameter uses dot notation to access nested fields
• Use resort types with the search endpoint: /search?facet=resort_type:Alpint