Search deals that Pelando users have posted.

Returns community postings, NOT a catalogue: one merchant per posting, free-text titles, and only products someone chose to post. There is no product database behind this — even mainstream terms can legitimately return nothing.

Pelando's search is token-based and loose ("iphone 16 pro" matches "iPhone 14 Pro ... 16"), so each result carries a relevance block. With drop_irrelevant the weak matches are moved to related rather than deleted, so nothing is hidden from you.

Only include_expired and sort are server-side. Every other filter is applied locally after fetching, so a narrow filter with a small size may return few rows even when more exist upstream.

Browse Pelando's own feeds, optionally scoped to one community.

community must be one of the 11 canonical slugs — there is no finer taxonomy on the site. For electronics use tech-lover or mundo-gamer. An unknown slug is rejected here rather than sent, because the API silently ignores it and returns the global feed instead.

Fetch one deal by UUID or by slug.

A slug works directly, so a URL the user pasted (pelando.com.br/d/<slug>) can be handed over with just the last path segment.

Read a deal's comment thread — where the crowd corrects a bad posting.

The thread is the only place a fake discount gets explained; there is no report or flag field in Pelando's data. Note the upstream endpoint has no pagination and returns the whole tree at once, so limit truncates locally and truncated tells you when that happened.

Judge whether the community believes a deal is genuine.

This is what Pelando has that a price comparator does not. It reads the crowd's vote (temperature, which goes NEGATIVE when users think a discount is fake or the price was inflated beforehand), the comment reactions, the poster's reputation, the deal's age and status, and any condition declared in the title.

Returns a verdict WITH its evidence attached, never a bare score — present the reasoning to the user rather than the label alone. It judges community sentiment, not merchant truth: it cannot verify that the price is real or still available.

Look up a merchant: its live activity counts and its top coupons.

Matching is loose and substring-based upstream — "amazon" also returns "Amaro" — so results are ranked here by how closely the name matches, but the caller should still check the name before acting on the first row.

promotion_count tells you how many active promotions a store has, but there is no endpoint anywhere that lists them. To see a store's deals, search a product term and filter by store.

Fetch a store's coupon codes.

only_valid_codes drops entries whose code is prose rather than a redeemable code — the field has been seen holding instructions like "Resgatar cupom abaixo do produto".

Coupons expire silently. Every code is reported with the date it was posted so its age is visible; none of them is guaranteed to still work.

List Pelando's 11 communities — the site's only browse taxonomy.

There is no category system beside this: deals carry a bare numeric categoryId with no label anywhere in the data. tech-lover and mundo-gamer are the electronics ones.

Liveness check. Returns server name, version, and runtime config.