English
EspañolEnglishPortuguêsFilipino
Get free API key
Peru · pe_oece_tenders_search
OpenAPI

Search oece · tenders

GET https://api.latinfo.dev/pe/oece/tenders/search

Search the published description index. Results are candidates, not confirmed identity matches. Confirm the country and identifier before fetching a profile. An empty list is not proof of absence.

Source contract

Publisher
OECE, Peru
Coverage
Published OCDS procurement processes in the imported official snapshot.
Record meaning
A full OCDS process by OCID; the seven index fields are a search projection, not the HTTP response schema.
Identifier
Lookup by ocid as a string, preserving leading zeros. Accepted syntax and normalization are defined by the contract below.
Accepted pattern
.*
Cardinality
one
License
Reuse permission has not been verified. Public access is not a reuse license.

Known limitations

  • Natural-person parties are removed by the API; document files remain external publisher links.
  • Use the OCDS OpenAPI response schema. Process/budget amounts are not automatically supplier contract values.
  • amount in the search index has no independently declared currency. The full OCDS amount/currency objects are authoritative.

Machine-readable source contract · Source documentation

Authentication required. REST requests use a Latinfo API key. The interactive console builds the authorization header and does not store the key.

Parameters

qstringqueryrequired

Name query, 3–200 characters.

Request example

curl https://api.latinfo.dev/pe/oece/tenders/search?q=q \
  -H "Authorization: Bearer $LATINFO_API_KEY"

Responses

200Published source records. Missing data is not a clearance or a negative finding.

Response headers

X-Latinfo-Imported-At

Import time, not the date of the government observation.

X-Source-Updated-At

Publisher update time, when known.

X-Latest-Observation-At

Latest date in returned records, when known.

X-Freshness-Status

string

CURRENT · DELAYED · STALE · UNKNOWN
X-Credits-Cost

Actual credits charged for this request.

X-Source-Generation

Opaque immutable source generation. Follow the guarded next-page Link when collecting a history.

Content-Type: application/json

Response fields

[].id string
[].description string

Published description.

[].estado string
Response schema
{
  "type": "array",
  "items": {
    "type": "object",
    "properties": {
      "id": {
        "type": "string"
      },
      "description": {
        "type": "string",
        "description": "Published description.",
        "x-latinfo-meaning": "text"
      },
      "estado": {
        "type": "string"
      }
    }
  }
}
400Invalid identifier or query. Correct the input before retrying.
No response body documented.
401Missing or invalid API key. Authenticate before retrying.
No response body documented.
404No published record, or identifier outside the legal-entity scope. Not proof that the company does not exist.
No response body documented.
429Rate or credit limit exceeded. Inspect the response and rate-limit headers before retrying.
No response body documented.
503Source unavailable. Report unavailable, not an empty result.
No response body documented.
Example JSON

Illustrative schema example. This is not a live response.

[
  {
    "id": "string",
    "description": "string",
    "estado": "string"
  }
]

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.

Esc