Endorsing an asset marks it as preferred content. When a search is run with endorsements switched on, any endorsed item that clears the relevance threshold gets pulled to the top of the results, above everything else that matched, regardless of its raw relevance score.
This isn’t a way to force irrelevant content into results. An endorsed asset still has to clear the same relevance bar as anything else. What changes is the ordering once it’s in the pool.
Here’s the same search, once without endorsements and once with:
Without endorsement
Asset | Relevance | Endorsed |
A1 | 0.95 | No |
A2 | 0.80 | Yes |
A3 | 0.75 | No |
A4 | 0.70 | Yes |
With endorsement
Asset | Relevance | Endorsed |
A2 | 0.80 | Yes |
A4 | 0.70 | Yes |
A1 | 0.95 | No |
A3 | 0.75 | No |
A2 and A4 move to the top even though A1 has a higher raw score. Within each group, endorsed and unendorsed, the original relevance ordering still holds.
Endorsing content
You’ll find the endorsement controls in the Manage Assets tab. Endorsements can be applied one at a time or in bulk using filters, so if you want to endorse everything from a particular provider, you don’t need to click through assets individually. The same filters work in reverse when you want to remove endorsements, so cleaning up or reworking your endorsed set is quick as well.
Using endorsements through the API
Endorsements are available through the search endpoint as an optional parameter:
use_endorsement=True
This defaults to false, so nothing changes for existing integrations unless you set it explicitly. Once you do, two things follow:
- Search results are reordered as shown above, with the endorsed group placed ahead of the unendorsed group.
- Any other endpoint that returns content data will start including the endorsed state of that content in its response. If you parse those responses, you may want to account for the new field.
Full detail on the request parameters and response fields is in the updated API documentation.
For further help, contact success@filtered.com