---
title: "SIC Industrial Property Resolutions Search"
method: POST
path: "/co/sic-ip/resolutions-search/v1"
tags: ["Colombia", "SIC, Registro de la Propiedad Industrial"]
---

# SIC Industrial Property Resolutions Search

`POST /co/sic-ip/resolutions-search/v1`

## Request

- Base URL: `https://api.croma.run`
- URL: `https://api.croma.run/co/sic-ip/resolutions-search/v1`
- Auth: HTTP bearer

Search every resolution and oficio Colombia's industrial-property office (SIC) has sent out since 2016 in trademark, patent and design cases (grants, refusals, oppositions, cancellations, transfers, licences, security interests, requirements) by words of the document type or the parties notified, narrowed by `file_number` (the case or the main case it belongs to), `kind` (`resolucion` or `oficio`) and the date it was sent (`from_date`/`to_date`). Each result carries the number, type, act date, the case numbers, the parties with their notification and ejecutoria dates and the PDF. Served by Croma from its copy (`as_of`).

**Dataset endpoint**: answers from the whole source in milliseconds and carries `as_of`.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `query` string: Optional words to find in the document's type or in the names of the parties it was notified to, e.g. `cancelación`, `garantía mobiliaria`. Every word must appear.
  - `file_number` string: Optional file number (expediente) the document was issued in, either the request itself or the main case it belongs to, e.g. `SD2026/0083453`.
  - `kind` '' | 'resolucion' | 'oficio': Optional kind of document: `resolucion` (a decision) or `oficio` (a requirement or a notice). Empty lists both.
  - `from_date` string, date: Optional date filter in yyyy-mm-dd format.
  - `to_date` string, date: Optional date filter in yyyy-mm-dd format.
  - `page` integer: 1-based page number for paginated results.
  - `per_page` integer: Results per page (1-50).

## Response `200`

Successful response

- SicIpResolutionsSearchResponse
  - `data` SicIpResolutionsSearchData, required
    - `as_of` string, nullable, required: How current the data in this response is.
    - `query` string, required
    - `file_number` string, nullable, required
    - `kind` string, nullable, required
    - `from_date` string, nullable, required
    - `to_date` string, nullable, required
    - `total` number, required: Matches, counted up to 1000.
    - `total_is_exact` boolean, required: False when more than 1000 match: `total` is then 1000, and the pages go on.
    - `page` number, required
    - `per_page` number, required
    - `total_pages` number, required: Pages over `total`; there are more when `total_is_exact` is false.
    - `count` number, required
    - `results` object[], required
      - `document_id` string, required: The register's id of the document, 16 hexadecimal characters, e.g. `09000002825ba3d5`.
      - `kind` 'resolucion' | 'oficio', required: `resolucion` (a decision) or `oficio` (a requirement or a notice).
      - `resolution_number` string, nullable, required: The resolution's or oficio's number, e.g. `77922`.
      - `title` string, nullable, required: The document's type as the register names it, e.g. `TM179 - Acepta Cancelación`, `240 PT Resolución Abandono art 44`.
      - `template_code` string, nullable, required: The template code the type begins with, e.g. `TM179`, `PT240`, `NC513`.
      - `act_date` string, nullable, required: `yyyy-mm-dd` of the administrative act.
      - `sent_date` string, required: `yyyy-mm-dd` the register sent the document out (fecha de envío); what `from_date` and `to_date` filter on.
      - `file_number` string, nullable, required: The request the document answers (número de solicitud): the case itself, or a secondary request in it (an opposition, a transfer, a security interest).
      - `main_file_number` string, nullable, required: The main case a secondary request belongs to (número de solicitud PI), when it is not the same.
      - `parties` object[], required: Who the document was notified to, with each party's own notification and ejecutoria dates.
        - `name` string, nullable, required: The party the document was notified to, as the register writes it.
        - `notified_on` string, nullable, required: `yyyy-mm-dd` that party was notified.
        - `enforced_on` string, nullable, required: `yyyy-mm-dd` the act became final for that party (ejecutoria).
      - `notified_on` string, nullable, required: `yyyy-mm-dd` the act was notified.
      - `enforced_on` string, nullable, required: `yyyy-mm-dd` the act became final (ejecutoria).
      - `document_url` string, nullable, required: Croma's copy of the document (PDF), byte for byte as the register serves it.
      - `source_document_url` string, required: The register's own link to the document.
      - `bytes` integer, nullable, required: Size of our copy in bytes.

## Other responses

- `400`: Invalid request body
- `401`: Missing or invalid API key
- `429`: Rate limit exceeded
- `500`: Internal error
- `502`: Upstream source returned an error

---

[API](https://skmtc.dev/usecroma/apis/croma-marketplace-api.md) · [All operations](https://skmtc.dev/usecroma/apis/croma-marketplace-api/llms.txt) · [OpenAPI document](https://skmtc.dev/usecroma/apis/croma-marketplace-api/revisions/df016cdb29d7?raw)