A keyword search on /trending answered server_error on every source. Fixed and verified on all twelve. Titles and descriptions no longer carry HTML entities such as " or &, and the docs console has two keyword examples to try.
A customer reported that GET /trending?source=pinterest&keyword=... returned server_error while the same request without the keyword worked. The cause was ours: the keyword filter reused one bound placeholder for several columns, which the database driver refuses, so every keyword search on every source failed the same way. It now binds one placeholder per column.
- Verified on every source. rss, facebook, x, tiktok, instagram, pinterest, bluesky, douyin, reddit, mastodon, tumblr and hackernews all answer 200 with a keyword.
- Text is text. Several scrapers stored what the network's HTML carried, so a title could arrive as "Yes Space". The API decodes entities before it answers, on every source.
- Docs. The try-it console on /api/v1/docs.php has two keyword examples. One note for readers: the default time range is 24 hours, and a network we scrape on a slower cadence can be empty in that window. Use time_range=7d or 30d when a result is empty.
If your integration retried keyword searches and gave up on them, switch them back on. Nothing changed in the parameters.