Content Enrichment API / Approval Links
Reject approval image upload
PageMore page actions
POST /v2/project/content/rejectApprovalImageUpload
Reject one pending photo upload: the upload's feedback item is rejected and the photo is never served. The page's photo list is not touched and the stored file is kept. The upload is checked when it is locked: one whose stored photo record is incomplete and cannot be read answers 400 INVALID_STATUS_TRANSITION (contact YGO support), and then an upload that was already decided answers 400 INVALID_STATUS_TRANSITION. Works after the hotel approved. The reviewer is recorded as the user's ID, or project:<project id> for a project API key.
Example request
curl -X POST 'https://api.ygo.ai/v2/project/content/rejectApprovalImageUpload' \
-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",
"FeedbackID": "01a0f1c9-3e8a-7c12-b4d5-8e9f0a1b2c3d"
}'Authorization
Authorization: Bearer <key>
Project-scoped API key
Headers
X-Project-IDstring (uuid) requiredProject UUID. Required for all project-scoped endpoints.
Request body required
application/json object RejectApprovalImageUploadRequest
The upload to reject and its hotel.
HotelIDstring (uuid) requiredUUID of the hotel. Required, a valid non-nil UUID, and a live member of the calling project.
FeedbackIDstring (uuid) requiredUUID of the upload: its
IDfrom listApprovalImageUploads, the id of its feedback item. Required, a valid non-nil UUID.
Example request: Reject one pending upload
{
"HotelID": "019d9c2e-0ef8-7458-b0fa-8bed7182eb30",
"FeedbackID": "01a0f1c9-3e8a-7c12-b4d5-8e9f0a1b2c3d"
}Responses
200 OK
The rejected upload, Status rejected with its ReviewedAt.
Headers
X-Trace-IDstringRequest trace ID for debugging (OpenTelemetry). Include this ID when contacting support about specific requests.
Body
application/json object RejectApprovalImageUploadResponse
Single-object response envelope wrapping the decided upload.
Dataobject ApprovalImageUpload requiredOne photo a hotel contact uploaded on the approval page.
10 fields
IDstring (uuid) requiredUUID of the upload: the id of its feedback item. Pass it as
FeedbackIDto acceptApprovalImageUpload or rejectApprovalImageUpload.HotelIDstring (uuid) requiredUUID of the hotel the photo was uploaded for.
URLstring (uri) requiredWhere the photo is served from.
Widthinteger requiredWidth 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.
Heightinteger requiredHeight 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.
FileSizeinteger requiredSize 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.
Formatstring requiredFile 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
jpegorpng.Statusstring requiredState of the upload:
pendinguntil a reviewer decides,acceptedonce it is on the page's photo list,rejectedwhen it was refused and is never served.CreatedAtstring (date-time) requiredWhen the photo was uploaded (RFC3339).
ReviewedAtstring (date-time)When a reviewer accepted or rejected the upload (RFC3339). Omitted while it is pending.
Example response: The photo is refused and never served
{
"Data": {
"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": "rejected",
"CreatedAt": "2026-10-12T09:14:03.512874Z",
"ReviewedAt": "2026-10-12T11:02:39.660142Z"
}
}400 Bad Request
Bad Request - the request body or the X-Project-ID header failed validation, or the upload cannot be decided (INVALID_STATUS_TRANSITION: its stored photo record is incomplete, or it was already decided).
Headers
X-Trace-IDstringRequest trace ID for debugging (OpenTelemetry). Include this ID when contacting support about specific requests.
Body
application/json object ErrorResponse
Standard v2 error response wrapper.
Errorobject ErrorDetail requiredError detail containing a machine-readable code and human-readable message.
3 fields
Codestring requiredMachine-readable error code for programmatic handling.
Messagestring requiredHuman-readable error message.
Fieldsarray of object FieldErrorField-level validation errors. Only present for VALIDATION_ERROR responses.
4 fields
Fieldstring requiredPath 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.
Messagestring requiredHuman-readable validation error message for this field.
CodestringMachine-readable reason the field failed validation. Optional; clients should fall back to Message when it is absent or unrecognized.
Paramsmap of string to anyMachine-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 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"
}
]
}
}Example response: FeedbackID missing or not a valid UUID
{
"Error": {
"Code": "VALIDATION_ERROR",
"Message": "Validation failed",
"Fields": [
{
"Field": "FeedbackID",
"Message": "FeedbackID must be a valid UUID"
}
]
}
}Example response: The upload's stored photo record is incomplete and cannot be read
{
"Error": {
"Code": "INVALID_STATUS_TRANSITION",
"Message": "This upload cannot be reviewed: its photo record is incomplete. Please contact YGO support."
}
}Example response: The upload was already accepted or rejected
{
"Error": {
"Code": "INVALID_STATUS_TRANSITION",
"Message": "This photo was already reviewed."
}
}401 Unauthorized
Unauthorized - Invalid or missing bearer token.
Headers
X-Trace-IDstringRequest trace ID for debugging (OpenTelemetry). Include this ID when contacting support about specific requests.
Body
application/json object ErrorResponse
Standard v2 error response wrapper.
Errorobject ErrorDetail requiredError detail containing a machine-readable code and human-readable message.
3 fields
Codestring requiredMachine-readable error code for programmatic handling.
Messagestring requiredHuman-readable error message.
Fieldsarray of object FieldErrorField-level validation errors. Only present for VALIDATION_ERROR responses.
4 fields
Fieldstring requiredPath 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.
Messagestring requiredHuman-readable validation error message for this field.
CodestringMachine-readable reason the field failed validation. Optional; clients should fall back to Message when it is absent or unrecognized.
Paramsmap of string to anyMachine-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 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:write permission this endpoint requires.
Headers
X-Trace-IDstringRequest trace ID for debugging (OpenTelemetry). Include this ID when contacting support about specific requests.
Body
application/json object ErrorResponse
Standard v2 error response wrapper.
Errorobject ErrorDetail requiredError detail containing a machine-readable code and human-readable message.
3 fields
Codestring requiredMachine-readable error code for programmatic handling.
Messagestring requiredHuman-readable error message.
Fieldsarray of object FieldErrorField-level validation errors. Only present for VALIDATION_ERROR responses.
4 fields
Fieldstring requiredPath 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.
Messagestring requiredHuman-readable validation error message for this field.
CodestringMachine-readable reason the field failed validation. Optional; clients should fall back to Message when it is absent or unrecognized.
Paramsmap of string to anyMachine-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 response: Missing required scope
{
"Error": {
"Code": "INSUFFICIENT_SCOPE",
"Message": "token lacks scope content.authoring:write"
}
}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, the hotel or the upload is not reachable for this caller.
Headers
X-Trace-IDstringRequest trace ID for debugging (OpenTelemetry). Include this ID when contacting support about specific requests.
Body
application/json object ErrorResponse
Standard v2 error response wrapper.
Errorobject ErrorDetail requiredError detail containing a machine-readable code and human-readable message.
3 fields
Codestring requiredMachine-readable error code for programmatic handling.
Messagestring requiredHuman-readable error message.
Fieldsarray of object FieldErrorField-level validation errors. Only present for VALIDATION_ERROR responses.
4 fields
Fieldstring requiredPath 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.
Messagestring requiredHuman-readable validation error message for this field.
CodestringMachine-readable reason the field failed validation. Optional; clients should fall back to Message when it is absent or unrecognized.
Paramsmap of string to anyMachine-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 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"
}
}Example response: No upload of this hotel in this project has this id
{
"Error": {
"Code": "NOT_FOUND",
"Message": "Upload 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-IDstringRequest trace ID for debugging (OpenTelemetry). Include this ID when contacting support about specific requests.
Retry-AfterintegerNumber of seconds to wait before retrying the request. Present on 429 responses.
Body
application/json object ErrorResponse
Standard v2 error response wrapper.
Errorobject ErrorDetail requiredError detail containing a machine-readable code and human-readable message.
3 fields
Codestring requiredMachine-readable error code for programmatic handling.
Messagestring requiredHuman-readable error message.
Fieldsarray of object FieldErrorField-level validation errors. Only present for VALIDATION_ERROR responses.
4 fields
Fieldstring requiredPath 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.
Messagestring requiredHuman-readable validation error message for this field.
CodestringMachine-readable reason the field failed validation. Optional; clients should fall back to Message when it is absent or unrecognized.
Paramsmap of string to anyMachine-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 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-IDstringRequest trace ID for debugging (OpenTelemetry). Include this ID when contacting support about specific requests.
Body
application/json object ErrorResponse
Standard v2 error response wrapper.
Errorobject ErrorDetail requiredError detail containing a machine-readable code and human-readable message.
3 fields
Codestring requiredMachine-readable error code for programmatic handling.
Messagestring requiredHuman-readable error message.
Fieldsarray of object FieldErrorField-level validation errors. Only present for VALIDATION_ERROR responses.
4 fields
Fieldstring requiredPath 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.
Messagestring requiredHuman-readable validation error message for this field.
CodestringMachine-readable reason the field failed validation. Optional; clients should fall back to Message when it is absent or unrecognized.
Paramsmap of string to anyMachine-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 response: The decision could not be stored
{
"Error": {
"Code": "INTERNAL_ERROR",
"Message": "Failed to review the upload"
}
}Example response: Hotel membership could not be verified
{
"Error": {
"Code": "INTERNAL_ERROR",
"Message": "Failed to verify hotel"
}
}