Yelp User Compliments API | Community Recognition

Retrieve a page of public compliments received by one Yelp contributor. The required user input accepts a 22-character Yelp user ID or a Yelp profile URL. Optional page selects a page from 1 to 1000 and defaults to 1; page_size selects 1 to 50 compliments per page and defaults to 20. The documented response content includes each compliment's type, message, date and sender. These are described attributes, not verified JSON field names: this operation has no observed probe response, and its supplied HTTP 200 example is only an empty object. Response nesting, sender subfields, pagination metadata and empty-result behavior are therefore unverified. Compliments represent community recognition, not verified expertise, business endorsements or contact permission.

API Features

Recipient-focused recognition lookup Select one Yelp contributor to request the public compliments they received, rather than reviews they wrote or profiles they follow.

Documented compliment attributes The endpoint documentation describes type, message, date and sender for compliments; concrete JSON keys and sender details remain unverified.

Configurable compliment page length Choose 1 to 50 compliments per page with page_size, using the documented default of 20 when the parameter is omitted.

Numbered recognition pages Request page numbers from 1 to 1000, starting at the documented default of 1, without assuming every page contains results.

Live API Demo

GET /api/project/yelp/user-compliments

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/yelp/user-compliments?key=<API_KEY>&page=1&page_size=20&user=CHV3OXUzMbMDZ5A07UGO5A'

curl -X GET 'https://api.opendata-api.com/api/project/yelp/user-compliments?key=<API_KEY>&page=1&page_size=20&user=CHV3OXUzMbMDZ5A07UGO5A'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Compare the mix of returned compliment types in a limited community-recognition study without treating them as proof of expertise.
Build a user-requested recognition snapshot showing compliment messages and dates while retaining only necessary sender information.
Review available compliment dates for a defined period after confirming the returned date format, without claiming a complete recognition history.
Let a contributor browse received recognition in smaller page-sized batches without enabling unsolicited contact with senders.

Frequently asked questions

Does this endpoint return compliments received or compliments sent?

It is documented to return compliments received by the selected Yelp user. It is not a listing of compliments that user sent to other people.

What can I supply in the user parameter?

Supply a 22-character Yelp user ID or a Yelp profile URL. The user parameter is required.

How do compliment pagination controls work?

page accepts integers from 1 to 1000 and defaults to 1. page_size accepts 1 to 50 compliments per page and defaults to 20. These limits do not establish how many compliments a particular user has.

Which compliment response fields have been verified?

Type, message, date and sender are documented attributes only. No probe response was observed for this endpoint, and the supplied success example is an empty object, so exact JSON keys, nesting and empty-result handling are not verified.

Can compliments establish expertise or permission to contact a sender?

No. Treat them as community-recognition signals, not verified expertise or business endorsements. A sender appearing in a public compliment does not provide permission for unsolicited contact.

Related operations

Guides

View Subscription Plans →

Get compliments received by a Yelp user