Yente API statements endpoint with an on-premise deployment

Hello,

We are using OpenSanctions via Yente with an on-premise deployment.
For your information, we are very satisfied with it.

We have a question regarding the source of a piece of data returned by the API.
We have an entity that comes back with the topic “export.control”.

Through your website, we were able to trace the origin (the original dataset) of this information.
This is properly retrieved using statements, for example via this URL: https://www.opensanctions.org/statements/)/?offset=0&prop=topics

Is there an endpoint that serves the same purpose via the Yente API?

On OpenSanctions Yente API, I can see the endpoint Statement-based records.

Is this endpoint retrieves the same information of the website statements page?

Why is it not available on my locally deployed Yente API?

Thank you in advance for your help.

Best regards

As far as I understand it, the statements endpoint on api.opensanctions.org is served from the hosted OpenSanctions database, which keeps every property as a separate statement with its source dataset. A self-hosted yente only indexes the aggregated entities (entities.ftm.json per dataset), so it has no statement-level data to serve, and that is probably why the endpoint isn’t there on your instance.

For your export.control case, there are two things you can try locally. First, the entity returned by yente usually lists the source datasets it was merged from, so you can often see which list contributed the topic. Second, the bulk data page documents a statement-based export, with columns like entity_id, prop, value and dataset. If you load that into a database and filter on prop = topics and your entity ID, you get the same view as the statements page on the website.

Note that the statement-based data falls under the bulk data licensing, so check the terms for your commercial use. The maintainers can confirm whether a statements endpoint is planned for yente.