List Photos Uploaded by a Yelp User
View all Yelp Business, Reviews & Restaurant Data endpoints →Retrieve a page of photos uploaded by one Yelp contributor. The required user parameter accepts a 22-character Yelp user ID or a Yelp profile URL. page accepts 1 through 1000 and has a documented default of 1; page_size accepts 1 through 50 and has a documented default of 20. This endpoint exposes no documented sort, caption-search or business-filter parameter. The endpoint documentation describes each uploaded photo with its caption, date and the business it was taken at. No response was observed for this endpoint, and the supplied success example is an empty object ({}). The caption, date and business association are documented capabilities, not verified JSON fields: exact keys, image URL fields, date format, pagination metadata and missing-value behavior are unconfirmed. Record any missing business association as unresolved. A returned page is not proof of a complete upload history, and access to photo metadata does not grant permission to reuse images or establish that the contributor visited a location.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/yelp/user-photos API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/yelp/user-photos?key=<API_KEY>&user=CHV3OXUzMbMDZ5A07UGO5A'
Query Result
Use Cases
- Create a contributor-requested photo metadata inventory with captions, dates and business associations where returned, without assuming permission to download or republish the images.
- For an approved cohort, study how photo contributions are distributed across business categories using separately resolved category data, not inferred travel histories.
- Review the captions on a limited set of a contributor's uploads for a user-requested content audit, preserving missing captions rather than inventing replacements.
- Prepare a photo-to-business reconciliation queue that keeps unresolved associations explicit instead of assigning a business from location guesses.
Frequently asked questions
Does this retrieve a user's uploads or every photo of a business?
This endpoint is documented to retrieve photos uploaded by the Yelp user identified by user. It is not a business-wide photo listing, and it has no documented business-filter parameter.
What user identifiers can I pass for uploaded photos?
The required user parameter accepts a 22-character Yelp user ID or a Yelp profile URL. It selects the contributor whose uploads you want to inspect.
What pagination controls are available for user photos?
page accepts 1 through 1000 and defaults to 1 according to the documentation. page_size accepts 1 through 50 and defaults to 20. These bounds do not guarantee that every page is populated or that all uploads are accessible.
Are caption, date, image URL and business fields verified?
Captions, dates and the associated business are described in the documentation, but no endpoint response was observed and the supplied success example is {}. Exact JSON keys, image URL fields, date format and missing-value behavior are unconfirmed.
May I reuse photos or infer a contributor's visits from the results?
Retrieving metadata does not grant image-reuse rights. A documented association between a photo and a business is also not proof of a physical visit; avoid precise travel or sensitive-location inference.