> ## Documentation Index > Fetch the complete documentation index at: https://docs.usecroma.com/llms.txt > Use this file to discover all available pages before exploring further. # Tribunal Constitucional Rulings Search > Search every resolution the Tribunal Constitucional del Perú has published since 1996: sentencias, autos and sentencias interlocutorias. Free text matches the case file number, the resolution number and the full text. Filter by `type`, `proceeding_type` (`AA` amparo, `HC` hábeas corpus, `HD` hábeas data, `AC` cumplimiento, `AI`/`PI` inconstitucionalidad, `CC` competencial, `Q` queja), `chamber`, `registration_number` (the expediente), `year` and the publication date (`from_date`/`to_date`). Each result links to the document on the court's own site. Served by Croma (`as_of` says how current the data is). **Dataset endpoint**: answers from the whole source in milliseconds and carries `as_of`. ## OpenAPI ````yaml /api-reference/openapi.json post /pe/tribunal-constitucional/rulings-search/v1 openapi: 3.1.0 info: title: Croma Marketplace API version: 1.0.0 description: >- Government-data APIs for Colombia, Peru, Mexico, and global web search. Croma normalizes public-sector data into structured JSON for product teams and AI agents. Every operation is a POST with a JSON body and an organization API key as a bearer token; every operation is an idempotent lookup and accepts an optional `Idempotency-Key` header. Paths carry their major version (`/v1`); the versioning and deprecation policy, including the `Deprecation` and `Sunset` headers a retiring endpoint sends, is at https://docs.usecroma.com/versioning. Rate limits are per organization and reported on every response (`RateLimit-Policy`, `X-RateLimit-*`): https://docs.usecroma.com/rate-limits. termsOfService: https://usecroma.com/en/terms contact: name: Croma support url: https://usecroma.com/en/support email: tomas@usecroma.com servers: - url: https://api.croma.run security: [] paths: /pe/tribunal-constitucional/rulings-search/v1: post: tags: - Peru - Tribunal Constitucional summary: Tribunal Constitucional Rulings Search description: >- Search every resolution the Tribunal Constitucional del Perú has published since 1996: sentencias, autos and sentencias interlocutorias. Free text matches the case file number, the resolution number and the full text. Filter by `type`, `proceeding_type` (`AA` amparo, `HC` hábeas corpus, `HD` hábeas data, `AC` cumplimiento, `AI`/`PI` inconstitucionalidad, `CC` competencial, `Q` queja), `chamber`, `registration_number` (the expediente), `year` and the publication date (`from_date`/`to_date`). Each result links to the document on the court's own site. Served by Croma (`as_of` says how current the data is). **Dataset endpoint**: answers from the whole source in milliseconds and carries `as_of`. operationId: tribunal_constitucional_rulings_search parameters: - $ref: '#/components/parameters/IdempotencyKey' requestBody: required: true content: application/json: schema: type: object required: [] properties: query: type: string maxLength: 300 default: '' description: >- Optional search terms matched against the case file number, the resolution number and the full text. type: type: string enum: - '' - sentencia - auto - sentencia_interlocutoria default: '' description: >- Optional kind of resolution: `sentencia`, `auto` (autos and decretos) or `sentencia_interlocutoria`. proceeding_type: type: string maxLength: 40 default: '' description: >- Optional kind of proceeding, by code or by name: `AA` (amparo), `HC` (hábeas corpus), `HD` (hábeas data), `AC` (cumplimiento), `AI` or `PI` (inconstitucionalidad), `CC` (competencial), `Q` (queja). chamber: type: string maxLength: 20 default: '' description: 'Optional chamber: `Pleno`, `Sala Primera` or `Sala Segunda`.' registration_number: type: string maxLength: 40 default: '' description: >- Optional case file number (expediente) as the court writes it, e.g. `05005-2025-HC`. Returns every document of that case. Case and spaces are ignored. year: type: integer minimum: 0 maximum: 2100 default: 0 description: Optional year of publication. 0 searches every year. from_date: type: string format: date default: '' description: Optional date filter in yyyy-mm-dd format. to_date: type: string format: date default: '' description: Optional date filter in yyyy-mm-dd format. page: type: integer minimum: 1 maximum: 1000 default: 1 description: 1-based page number for paginated results. per_page: type: integer minimum: 1 maximum: 50 default: 20 description: Results per page (1-50). additionalProperties: false example: query: debido proceso proceeding_type: HC responses: '200': description: Successful response headers: X-Request-Id: $ref: '#/components/headers/X-Request-Id' RateLimit-Policy: $ref: '#/components/headers/RateLimit-Policy' Idempotency-Key: $ref: '#/components/headers/Idempotency-Key' Deprecation: $ref: '#/components/headers/Deprecation' Sunset: $ref: '#/components/headers/Sunset' X-RateLimit-Limit: $ref: '#/components/headers/X-RateLimit-Limit' X-RateLimit-Remaining: $ref: '#/components/headers/X-RateLimit-Remaining' X-RateLimit-Reset: $ref: '#/components/headers/X-RateLimit-Reset' X-Cache: $ref: '#/components/headers/X-Cache' content: application/json: schema: $ref: >- #/components/schemas/TribunalConstitucionalRulingsSearchResponse '400': description: Invalid request body headers: X-Request-Id: $ref: '#/components/headers/X-Request-Id' RateLimit-Policy: $ref: '#/components/headers/RateLimit-Policy' Idempotency-Key: $ref: '#/components/headers/Idempotency-Key' Deprecation: $ref: '#/components/headers/Deprecation' Sunset: $ref: '#/components/headers/Sunset' content: application/json: schema: $ref: '#/components/schemas/ApiError' '401': description: Missing or invalid API key headers: X-Request-Id: $ref: '#/components/headers/X-Request-Id' RateLimit-Policy: $ref: '#/components/headers/RateLimit-Policy' Idempotency-Key: $ref: '#/components/headers/Idempotency-Key' Deprecation: $ref: '#/components/headers/Deprecation' Sunset: $ref: '#/components/headers/Sunset' content: application/json: schema: $ref: '#/components/schemas/ApiError' '429': description: Rate limit exceeded headers: X-Request-Id: $ref: '#/components/headers/X-Request-Id' RateLimit-Policy: $ref: '#/components/headers/RateLimit-Policy' Idempotency-Key: $ref: '#/components/headers/Idempotency-Key' Deprecation: $ref: '#/components/headers/Deprecation' Sunset: $ref: '#/components/headers/Sunset' X-RateLimit-Limit: $ref: '#/components/headers/X-RateLimit-Limit' X-RateLimit-Remaining: $ref: '#/components/headers/X-RateLimit-Remaining' X-RateLimit-Reset: $ref: '#/components/headers/X-RateLimit-Reset' Retry-After: $ref: '#/components/headers/Retry-After' content: application/json: schema: $ref: '#/components/schemas/ApiError' '500': description: Internal error headers: X-Request-Id: $ref: '#/components/headers/X-Request-Id' RateLimit-Policy: $ref: '#/components/headers/RateLimit-Policy' Idempotency-Key: $ref: '#/components/headers/Idempotency-Key' Deprecation: $ref: '#/components/headers/Deprecation' Sunset: $ref: '#/components/headers/Sunset' content: application/json: schema: $ref: '#/components/schemas/ApiError' '502': description: Upstream source returned an error headers: X-Request-Id: $ref: '#/components/headers/X-Request-Id' RateLimit-Policy: $ref: '#/components/headers/RateLimit-Policy' Idempotency-Key: $ref: '#/components/headers/Idempotency-Key' Deprecation: $ref: '#/components/headers/Deprecation' Sunset: $ref: '#/components/headers/Sunset' content: application/json: schema: $ref: '#/components/schemas/ApiError' security: - bearerAuth: [] externalDocs: description: Interactive documentation and examples url: https://docs.usecroma.com/guides/peru/tribunal-constitucional components: parameters: IdempotencyKey: name: Idempotency-Key in: header required: false description: >- Optional client-chosen key for this request (any string up to 255 characters, e.g. a UUID). Every Croma operation is an idempotent lookup: repeating a request with the same body returns the same result and creates nothing, so retrying after a timeout or network failure is always safe. The key is echoed back in the `Idempotency-Key` response header so you can correlate a retry with its first attempt. Each attempt that reaches the API counts against the rate limit. schema: type: string maxLength: 255 example: 0f8e9a42-6b7c-4d1e-9a3f-2c5d7e8f9a0b headers: X-Request-Id: description: Unique id for the request (req_…). Include it in support reports. schema: type: string RateLimit-Policy: description: >- Quota policy for this endpoint as an IETF RateLimit-Policy structured field, e.g. `"default";q=100;w=86400` (100 requests per 86400-second window per organization). Endpoints with an extra hourly ceiling list both policies, e.g. `"webSearch";q=10;w=3600, "default";q=100;w=86400`. Present on every response, including 401 and 429. schema: type: string example: '"default";q=100;w=86400' Idempotency-Key: description: >- The `Idempotency-Key` the request carried, echoed back unchanged. Absent when the request sent none. schema: type: string Deprecation: description: >- Present only on an endpoint version scheduled for removal: the date the deprecation took effect (RFC 9745). A `Sunset` header and a `Link` with `rel="successor-version"` accompany it. Policy: https://docs.usecroma.com/versioning schema: type: string example: '@1767225600' Sunset: description: >- Present only on an endpoint version scheduled for removal: the date after which it answers 410 (RFC 8594). Announced in the changelog at least 90 days ahead. schema: type: string format: date-time example: Wed, 01 Apr 2026 00:00:00 GMT X-RateLimit-Limit: description: Requests allowed in the current window. schema: type: integer X-RateLimit-Remaining: description: Requests left before you are throttled. schema: type: integer X-RateLimit-Reset: description: ISO 8601 timestamp when the window resets. schema: type: string format: date-time X-Cache: description: HIT or MISS. Cached hits still count against your quota. schema: type: string enum: - HIT - MISS Retry-After: description: Seconds to wait before retrying. schema: type: integer schemas: TribunalConstitucionalRulingsSearchResponse: type: object required: - data properties: data: $ref: '#/components/schemas/TribunalConstitucionalRulingsSearchData' ApiError: type: object required: - error properties: error: type: object required: - type - code - message properties: type: type: string description: >- Broad category: invalid_request_error, authentication_error, not_found_error, rate_limit_error, upstream_error, api_error. code: type: string description: Machine-readable specific code. message: type: string description: Human-readable explanation, safe to surface in UI. param: type: string description: Field that triggered the error. Present on validation errors. details: type: object description: Free-form structured detail. TribunalConstitucionalRulingsSearchData: type: object properties: as_of: anyOf: - type: string - type: 'null' description: How current the data in this response is. query: type: string type: anyOf: - type: string - type: 'null' proceeding_type: anyOf: - type: string - type: 'null' chamber: anyOf: - type: string - type: 'null' registration_number: anyOf: - type: string - type: 'null' year: anyOf: - type: number - type: 'null' from_date: anyOf: - type: string - type: 'null' to_date: anyOf: - type: string - type: 'null' total: type: number page: type: number per_page: type: number total_pages: type: number count: type: number results: type: array items: type: object properties: id: type: string description: >- The document's permanent identifier: its path on the court's site, e.g. "2026/05005-2025-HC.pdf" or "2021/04841-2019-HC Aclaracion.pdf". One case can have several documents, so the case file number is not unique. registration_number: type: string description: >- The case file number (expediente) as the court prints it, e.g. "05005-2025-HC". proceeding_type_code: anyOf: - type: string - type: 'null' description: >- The kind of proceeding as the court's code, read off the case file number: `AA` amparo, `HC` hábeas corpus, `HD` hábeas data, `AC` cumplimiento, `AI` or `PI` inconstitucionalidad, `CC` competencial, `Q` queja. proceeding_type: anyOf: - type: string - type: 'null' description: >- The kind of proceeding by name: "Amparo", "Hábeas corpus", "Hábeas data", "Cumplimiento", "Inconstitucionalidad", "Competencial" or "Queja". Null for a code outside that list. type: anyOf: - type: string enum: - sentencia - auto - sentencia_interlocutoria - type: 'null' description: >- The kind of resolution: `sentencia`, `auto` (autos and decretos) or `sentencia_interlocutoria`. number: anyOf: - type: string - type: 'null' description: >- The number the court gives a sentencia, e.g. "181/2026". Null on autos and on many older sentencias. publication_date: type: string description: '`yyyy-mm-dd` the court published the resolution on its site.' year: type: number description: The year of publication. chamber: anyOf: - type: string - type: 'null' description: >- "Pleno", "Sala Primera" or "Sala Segunda". Null when the court records none. judicial_district: anyOf: - type: string - type: 'null' description: >- The judicial district the case came from, e.g. "Distrito Judicial de Lima". Recorded for about half the resolutions. case_id: anyOf: - type: number - type: 'null' description: >- The court's own identifier for the case, shared by every document of that case. text_status: type: string enum: - ok - scanned - missing description: >- `ok` when the full text is here; `scanned` when the court published the resolution as an image with no text in it; `missing` when it published no readable document. official_url: type: string description: >- The resolution's document on the Tribunal Constitucional's own site. case_url: anyOf: - type: string - type: 'null' description: The case's page on the Tribunal Constitucional's own site. required: - id - registration_number - proceeding_type_code - proceeding_type - type - number - publication_date - year - chamber - judicial_district - case_id - text_status - official_url - case_url required: - as_of - query - type - proceeding_type - chamber - registration_number - year - from_date - to_date - total - page - per_page - total_pages - count - results securitySchemes: bearerAuth: type: http scheme: bearer description: 'Use Authorization: Bearer YOUR_API_KEY' ````