API docs
Book a demo

Content Enrichment API / Approval Links

List approval image uploads

Page

POST /v2/project/content/listApprovalImageUploads

List one member hotel's photo uploads in every state but withdrawn (an upload the hotel undid), newest first, at most 200. Each upload carries its photo and its ID, the id of its feedback item, so a client can show the photo beside the item that listHotelFeedback returns. Pass the ID of a pending upload as FeedbackID to acceptApprovalImageUpload or rejectApprovalImageUpload.

Example request

curl -X POST 'https://api.ygo.ai/v2/project/content/listApprovalImageUploads' \
  -H "Authorization: Bearer $YGO_API_KEY" \
  -H "X-Project-ID: $YGO_PROJECT_ID" \
  -H "Content-Type: application/json" \
  -d '{
  "HotelID": "019d9c2e-0ef8-7458-b0fa-8bed7182eb30"
}'

Authorization

Authorization: Bearer <key>

Project-scoped API key

Headers

  • X-Project-ID string (uuid) required

    Project UUID. Required for all project-scoped endpoints.

    Example
    $YGO_PROJECT_ID

Request body required

application/json object ListApprovalImageUploadsRequest

The hotel whose uploads to list.

  • HotelID string (uuid) required

    UUID of the hotel. Required, a valid non-nil UUID, and a live member of the calling project.

    Example
    019d9c2e-0ef8-7458-b0fa-8bed7182eb30
Example request: List one hotel's photo uploads
{
  "HotelID": "019d9c2e-0ef8-7458-b0fa-8bed7182eb30"
}

Responses

200 OK

The hotel's uploads, newest first. Uploads is always an array, empty when there are none.

Headers

  • X-Trace-ID string

    Request trace ID for debugging (OpenTelemetry). Include this ID when contacting support about specific requests.

    Example
    abc123def456ghi789

Body

application/json object ListApprovalImageUploadsResponse

Single-object response envelope wrapping the hotel's uploads.

  • Data object ApprovalImageUploadList required

    The hotel's photo uploads.

    1 field
    • Uploads array of object ApprovalImageUpload required

      The uploads in every state but withdrawn, newest first, at most 200. Always present; empty when the hotel has none.

      Each item

      One photo a hotel contact uploaded on the approval page.

      10 fields
      • ID string (uuid) required

        UUID of the upload: the id of its feedback item. Pass it as FeedbackID to acceptApprovalImageUpload or rejectApprovalImageUpload.

        Example
        01a0f1c9-3e8a-7c12-b4d5-8e9f0a1b2c3d
      • HotelID string (uuid) required

        UUID of the hotel the photo was uploaded for.

        Example
        019d9c2e-0ef8-7458-b0fa-8bed7182eb30
      • URL string (uri) required

        Where the photo is served from.

        Example
        https://ucarecdn.com/8f14e45f-ceea-467a-9575-7d3b1c2a9e10/
      • Width integer required

        Width of the photo in pixels: for a photo recorded as uploaded (uploadImage names its Uploadcare URL), the width the hotel's browser reported (YGO-4317), unverified; 0 when none was sent. Uploads recorded before YGO-4286 (multipart) carry the stored photo's width.

        Example
        1600
      • Height integer required

        Height of the photo in pixels: for a photo recorded as uploaded (uploadImage names its Uploadcare URL), the height the hotel's browser reported (YGO-4317), unverified; 0 when none was sent. Uploads recorded before YGO-4286 (multipart) carry the stored photo's height.

        Example
        1200
      • FileSize integer required

        Size of the photo's file in bytes: 0 for a photo recorded as uploaded (uploadImage names its Uploadcare URL), whose size is not read. Uploads recorded before YGO-4286 (multipart) carry the stored photo's file size.

        Example
        0
      • Format string required

        File type of the photo: empty for a photo recorded as uploaded (uploadImage names its Uploadcare URL), whose type is not read. Uploads recorded before YGO-4286 (multipart) carry jpeg or png.

        Values
        jpeg png
        Example
      • Status string required

        State of the upload: pending until a reviewer decides, accepted once it is on the page's photo list, rejected when it was refused and is never served.

        Values
        pending accepted rejected
        Example
        pending
      • CreatedAt string (date-time) required

        When the photo was uploaded (RFC3339).

        Example
        2026-10-12T09:14:03.512874Z
      • ReviewedAt string (date-time)

        When a reviewer accepted or rejected the upload (RFC3339). Omitted while it is pending.

        Example
        2026-10-12T11:02:39.660142Z
Example response: One pending and one accepted upload
{
  "Data": {
    "Uploads": [
      {
        "ID": "01a0f1c9-3e8a-7c12-b4d5-8e9f0a1b2c3d",
        "HotelID": "019d9c2e-0ef8-7458-b0fa-8bed7182eb30",
        "URL": "https://ucarecdn.com/8f14e45f-ceea-467a-9575-7d3b1c2a9e10/",
        "Width": 1600,
        "Height": 1200,
        "FileSize": 0,
        "Format": "",
        "Status": "pending",
        "CreatedAt": "2026-10-12T09:14:03.512874Z"
      },
      {
        "ID": "01a0e7b4-52c1-7f6d-8a3e-0b9c4d2e1f70",
        "HotelID": "019d9c2e-0ef8-7458-b0fa-8bed7182eb30",
        "URL": "https://ucarecdn.com/3c59dc04-8e4a-4f7c-9c1d-6a2b5e8f0d31/",
        "Width": 1600,
        "Height": 1200,
        "FileSize": 0,
        "Format": "",
        "Status": "accepted",
        "CreatedAt": "2026-10-11T16:40:12.305918Z",
        "ReviewedAt": "2026-10-11T17:05:44.118203Z"
      }
    ]
  }
}
400 Bad Request

Bad Request - the request body or the X-Project-ID header failed validation.

Headers

  • X-Trace-ID string

    Request trace ID for debugging (OpenTelemetry). Include this ID when contacting support about specific requests.

    Example
    abc123def456ghi789

Body

application/json object ErrorResponse

Standard v2 error response wrapper.

  • Error object ErrorDetail required

    Error detail containing a machine-readable code and human-readable message.

    3 fields
    • Code string required

      Machine-readable error code for programmatic handling.

      Example
      VALIDATION_ERROR
    • Message string required

      Human-readable error message.

      Example
      Validation failed
    • Fields array of object FieldError

      Field-level validation errors. Only present for VALIDATION_ERROR responses.

      Each item

      A single field-level validation error.

      4 fields
      • Field string required

        Path of the field that failed validation, as the request sends it: a dotted path for a field inside a nested request object, a bare name for a top-level one.

        Example
        Name
      • Message string required

        Human-readable validation error message for this field.

        Example
        Name is required
      • Code string

        Machine-readable reason the field failed validation. Optional; clients should fall back to Message when it is absent or unrecognized.

        Values
        REQUIRED TOO_LONG TOO_SHORT OUT_OF_RANGE TOO_MANY INVALID_FORMAT NOT_ALLOWED CONFLICT INVALID_ENCODING INSECURE_SCHEME UNSAFE_CONTENT REQUIRED_WHEN_ENABLED
        Example
        TOO_LONG
      • Params map of string to any

        Machine-readable values the message is built from, such as limits or allowed values. Keys are PascalCase; which keys are present depends on Code. Optional.

        Example
        {
          "Max": 200
        }
Example response: X-Project-ID header missing
{
  "Error": {
    "Code": "VALIDATION_ERROR",
    "Message": "X-Project-ID header is required"
  }
}
Example response: Malformed request body
{
  "Error": {
    "Code": "VALIDATION_ERROR",
    "Message": "Invalid request body"
  }
}
Example response: HotelID missing or not a valid UUID
{
  "Error": {
    "Code": "VALIDATION_ERROR",
    "Message": "Validation failed",
    "Fields": [
      {
        "Field": "HotelID",
        "Message": "HotelID must be a valid UUID"
      }
    ]
  }
}
401 Unauthorized

Unauthorized - Invalid or missing bearer token.

Headers

  • X-Trace-ID string

    Request trace ID for debugging (OpenTelemetry). Include this ID when contacting support about specific requests.

    Example
    abc123def456ghi789

Body

application/json object ErrorResponse

Standard v2 error response wrapper.

  • Error object ErrorDetail required

    Error detail containing a machine-readable code and human-readable message.

    3 fields
    • Code string required

      Machine-readable error code for programmatic handling.

      Example
      VALIDATION_ERROR
    • Message string required

      Human-readable error message.

      Example
      Validation failed
    • Fields array of object FieldError

      Field-level validation errors. Only present for VALIDATION_ERROR responses.

      Each item

      A single field-level validation error.

      4 fields
      • Field string required

        Path of the field that failed validation, as the request sends it: a dotted path for a field inside a nested request object, a bare name for a top-level one.

        Example
        Name
      • Message string required

        Human-readable validation error message for this field.

        Example
        Name is required
      • Code string

        Machine-readable reason the field failed validation. Optional; clients should fall back to Message when it is absent or unrecognized.

        Values
        REQUIRED TOO_LONG TOO_SHORT OUT_OF_RANGE TOO_MANY INVALID_FORMAT NOT_ALLOWED CONFLICT INVALID_ENCODING INSECURE_SCHEME UNSAFE_CONTENT REQUIRED_WHEN_ENABLED
        Example
        TOO_LONG
      • Params map of string to any

        Machine-readable values the message is built from, such as limits or allowed values. Keys are PascalCase; which keys are present depends on Code. Optional.

        Example
        {
          "Max": 200
        }
Example response: No Authorization header
{
  "Error": {
    "Code": "UNAUTHORIZED",
    "Message": "Missing bearer token"
  }
}
Example response: The bearer token is not valid
{
  "Error": {
    "Code": "UNAUTHORIZED",
    "Message": "Invalid bearer token"
  }
}
403 Forbidden

Forbidden - the caller is authenticated but may not act on this project. Also returned with code INSUFFICIENT_SCOPE when the API key does not carry the content.authoring:read permission this endpoint requires.

Headers

  • X-Trace-ID string

    Request trace ID for debugging (OpenTelemetry). Include this ID when contacting support about specific requests.

    Example
    abc123def456ghi789

Body

application/json object ErrorResponse

Standard v2 error response wrapper.

  • Error object ErrorDetail required

    Error detail containing a machine-readable code and human-readable message.

    3 fields
    • Code string required

      Machine-readable error code for programmatic handling.

      Example
      VALIDATION_ERROR
    • Message string required

      Human-readable error message.

      Example
      Validation failed
    • Fields array of object FieldError

      Field-level validation errors. Only present for VALIDATION_ERROR responses.

      Each item

      A single field-level validation error.

      4 fields
      • Field string required

        Path of the field that failed validation, as the request sends it: a dotted path for a field inside a nested request object, a bare name for a top-level one.

        Example
        Name
      • Message string required

        Human-readable validation error message for this field.

        Example
        Name is required
      • Code string

        Machine-readable reason the field failed validation. Optional; clients should fall back to Message when it is absent or unrecognized.

        Values
        REQUIRED TOO_LONG TOO_SHORT OUT_OF_RANGE TOO_MANY INVALID_FORMAT NOT_ALLOWED CONFLICT INVALID_ENCODING INSECURE_SCHEME UNSAFE_CONTENT REQUIRED_WHEN_ENABLED
        Example
        TOO_LONG
      • Params map of string to any

        Machine-readable values the message is built from, such as limits or allowed values. Keys are PascalCase; which keys are present depends on Code. Optional.

        Example
        {
          "Max": 200
        }
Example response: Missing required scope
{
  "Error": {
    "Code": "INSUFFICIENT_SCOPE",
    "Message": "token lacks scope content.authoring:read"
  }
}
Example response: The user token has no editor access to the project
{
  "Error": {
    "Code": "FORBIDDEN",
    "Message": "Access denied to project"
  }
}
Example response: The request carries no project scope
{
  "Error": {
    "Code": "FORBIDDEN",
    "Message": "Project access required"
  }
}
404 Not Found

Not Found - the project or the hotel is not reachable for this caller.

Headers

  • X-Trace-ID string

    Request trace ID for debugging (OpenTelemetry). Include this ID when contacting support about specific requests.

    Example
    abc123def456ghi789

Body

application/json object ErrorResponse

Standard v2 error response wrapper.

  • Error object ErrorDetail required

    Error detail containing a machine-readable code and human-readable message.

    3 fields
    • Code string required

      Machine-readable error code for programmatic handling.

      Example
      VALIDATION_ERROR
    • Message string required

      Human-readable error message.

      Example
      Validation failed
    • Fields array of object FieldError

      Field-level validation errors. Only present for VALIDATION_ERROR responses.

      Each item

      A single field-level validation error.

      4 fields
      • Field string required

        Path of the field that failed validation, as the request sends it: a dotted path for a field inside a nested request object, a bare name for a top-level one.

        Example
        Name
      • Message string required

        Human-readable validation error message for this field.

        Example
        Name is required
      • Code string

        Machine-readable reason the field failed validation. Optional; clients should fall back to Message when it is absent or unrecognized.

        Values
        REQUIRED TOO_LONG TOO_SHORT OUT_OF_RANGE TOO_MANY INVALID_FORMAT NOT_ALLOWED CONFLICT INVALID_ENCODING INSECURE_SCHEME UNSAFE_CONTENT REQUIRED_WHEN_ENABLED
        Example
        TOO_LONG
      • Params map of string to any

        Machine-readable values the message is built from, such as limits or allowed values. Keys are PascalCase; which keys are present depends on Code. Optional.

        Example
        {
          "Max": 200
        }
Example response: The project does not exist or was deleted (user tokens)
{
  "Error": {
    "Code": "NOT_FOUND",
    "Message": "Project not found"
  }
}
Example response: The hotel is not a live member of the project
{
  "Error": {
    "Code": "NOT_FOUND",
    "Message": "Hotel not found"
  }
}
429 Too Many Requests

Too Many Requests. The response includes a Retry-After header with the number of seconds to wait before retrying.

Headers

  • X-Trace-ID string

    Request trace ID for debugging (OpenTelemetry). Include this ID when contacting support about specific requests.

    Example
    abc123def456ghi789
  • Retry-After integer

    Number of seconds to wait before retrying the request. Present on 429 responses.

    Example
    39
    Limits
    min 1

Body

application/json object ErrorResponse

Standard v2 error response wrapper.

  • Error object ErrorDetail required

    Error detail containing a machine-readable code and human-readable message.

    3 fields
    • Code string required

      Machine-readable error code for programmatic handling.

      Example
      VALIDATION_ERROR
    • Message string required

      Human-readable error message.

      Example
      Validation failed
    • Fields array of object FieldError

      Field-level validation errors. Only present for VALIDATION_ERROR responses.

      Each item

      A single field-level validation error.

      4 fields
      • Field string required

        Path of the field that failed validation, as the request sends it: a dotted path for a field inside a nested request object, a bare name for a top-level one.

        Example
        Name
      • Message string required

        Human-readable validation error message for this field.

        Example
        Name is required
      • Code string

        Machine-readable reason the field failed validation. Optional; clients should fall back to Message when it is absent or unrecognized.

        Values
        REQUIRED TOO_LONG TOO_SHORT OUT_OF_RANGE TOO_MANY INVALID_FORMAT NOT_ALLOWED CONFLICT INVALID_ENCODING INSECURE_SCHEME UNSAFE_CONTENT REQUIRED_WHEN_ENABLED
        Example
        TOO_LONG
      • Params map of string to any

        Machine-readable values the message is built from, such as limits or allowed values. Keys are PascalCase; which keys are present depends on Code. Optional.

        Example
        {
          "Max": 200
        }
Example response: Limit exceeded
{
  "Error": {
    "Code": "RATE_LIMIT_EXCEEDED",
    "Message": "Rate limit exceeded. Retry after the number of seconds in the Retry-After header."
  }
}
500 Internal Server Error

Internal Server Error - Unexpected server error. Include the X-Trace-ID header value when contacting support.

Headers

  • X-Trace-ID string

    Request trace ID for debugging (OpenTelemetry). Include this ID when contacting support about specific requests.

    Example
    abc123def456ghi789

Body

application/json object ErrorResponse

Standard v2 error response wrapper.

  • Error object ErrorDetail required

    Error detail containing a machine-readable code and human-readable message.

    3 fields
    • Code string required

      Machine-readable error code for programmatic handling.

      Example
      VALIDATION_ERROR
    • Message string required

      Human-readable error message.

      Example
      Validation failed
    • Fields array of object FieldError

      Field-level validation errors. Only present for VALIDATION_ERROR responses.

      Each item

      A single field-level validation error.

      4 fields
      • Field string required

        Path of the field that failed validation, as the request sends it: a dotted path for a field inside a nested request object, a bare name for a top-level one.

        Example
        Name
      • Message string required

        Human-readable validation error message for this field.

        Example
        Name is required
      • Code string

        Machine-readable reason the field failed validation. Optional; clients should fall back to Message when it is absent or unrecognized.

        Values
        REQUIRED TOO_LONG TOO_SHORT OUT_OF_RANGE TOO_MANY INVALID_FORMAT NOT_ALLOWED CONFLICT INVALID_ENCODING INSECURE_SCHEME UNSAFE_CONTENT REQUIRED_WHEN_ENABLED
        Example
        TOO_LONG
      • Params map of string to any

        Machine-readable values the message is built from, such as limits or allowed values. Keys are PascalCase; which keys are present depends on Code. Optional.

        Example
        {
          "Max": 200
        }
Example response: The uploads could not be read
{
  "Error": {
    "Code": "INTERNAL_ERROR",
    "Message": "Failed to list uploads"
  }
}
Example response: Hotel membership could not be verified
{
  "Error": {
    "Code": "INTERNAL_ERROR",
    "Message": "Failed to verify hotel"
  }
}