Get business-authored posts and announcements
View all Yelp Business, Reviews & Restaurant Data endpoints →Retrieve a Yelp business's own posts and announcements by supplying its alias, 22-character business ID or Yelp business URL in the required business parameter. This operation has no documented page, limit or date-filter parameter. It retrieves business-authored updates rather than customer reviews. The documentation describes posts and announcements with photos, links and likes. No populated response was independently verified for this operation, and the available example is an empty object. These are documented content attributes, not confirmed JSON property names or guarantees of populated fields. The response envelope, ordering, posting timestamps, promotion validity dates, completeness and behavior for businesses without posts are not established by the available evidence. Use returned content, when available, as an editorial review queue. Do not treat a promotion or operational announcement as current without checking its applicability; if no validity date is supplied, do not infer one. Likes indicate the documented engagement concept, not a verified count of customers or purchases. Keep business-authored content separate from customer feedback and respect permissions for associated media.
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/business-posts API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/yelp/business-posts?key=<API_KEY>&business=tonys-pizza-napoletana-san-francisco'
Query Result
Use Cases
- Create a business-announcement review queue that remains separate from a customer-review moderation queue.
- Support a permitted competitor-monitoring workflow by inspecting a selected business's posts and associated photos or links when returned.
- Flag local-business updates for an editor to verify promotional terms and operational relevance before publication.
- Record the content returned for each retrieval with application-side observation times, without treating those times as post publication dates or a complete historical archive.
Frequently asked questions
Are these posts customer reviews or the business's own announcements?
This operation is documented for the business's own posts and announcements. It is not a customer-review endpoint. Keep the two content types separate in your application.
Which business input is required for posts?
Provide business as a Yelp alias, a 22-character business ID or a Yelp business URL. The documented example alias is tonys-pizza-napoletana-san-francisco. The input selects one listing.
What post attributes are documented, and were they verified?
The documentation describes posts and announcements with photos, links and likes. No populated response was independently verified, and the available example is empty. Exact property names, the response envelope and whether particular values are present remain unconfirmed.
Can I request a page, a date range or a maximum number of posts?
No page, date-range or limit parameter is documented for this operation; business is its only input. The available evidence does not establish chronological ordering or complete post-history coverage.
Does a returned promotional post prove an offer is still valid?
No. Inspect the announcement and verify current applicability before relying on it. Promotion validity dates were not verified, and an absent date must not be interpreted as an indefinitely valid offer.
What does an empty response tell me about a business's announcements?
The available empty example does not establish how a business with no posts is represented. Do not use it to assert that an empty response always means no announcements exist, or that the endpoint provides a complete archive.