Recommended active tenders for a supplier RUC
GET
https://api.latinfo.dev/pe/oece/tenders/recomendadas/{ruc}
Returns active public procurement opportunities matched to the supplier profile inferred from its RUC and historical procurement activity.
Evidence-first response
Latinfo identifies the originating government dataset and preserves source evidence and freshness when the publisher exposes them. Verify material decisions with that institution.
Authentication required. REST requests use a Latinfo API key. The interactive console builds the authorization header and does not store the key.
Parameters
rucstringpathrequiredPeruvian legal-entity RUC (11 digits, starts with 20)
Example: 20100047218
Request example
curl https://api.latinfo.dev/pe/oece/tenders/recomendadas/20100047218 \
-H "Authorization: Bearer $LATINFO_API_KEY"
Responses
200Recommended active tenders
Content-Type:
application/json400Invalid RUC format
No response body documented.
401Missing or invalid API key
No response body documented.
429Rate limit exceeded
No response body documented.
Example JSON
{
"ruc": "20100047218",
"count": 15,
"recos": [
{
"ocid": "ocds-dgv273-seacev3-1227219",
"score": 0.844,
"title": "string",
"deadline": "2026-07-01"
}
]
}
Provenance and limitations
Coverage varies by country and public source. A missing field is not evidence that the underlying fact does not exist. Public registries may be delayed or contain source errors; inspect the returned evidence and source date before relying on a result.