canonical: https://jentic.com/apis/licitalab.cl/licitalab

# Licitalab Cl Licitalab

Jentic publishes the only available OpenAPI specification for Licitalab, keeping it validated and agent-ready. Licitalab is a Chilean public-procurement workspace that helps businesses discover, track, and respond to government tenders sourced from Mercado Publico and other Chilean procurement bodies. The API exposes 225 endpoints covering authentication, opportunities discovery, member workspaces, calendar tracking, attachments, guarantees, business lines, and notifications. Agents can search tender opportunities by code, follow them, assign them across team members, and manage offers and guarantees through bearer-token authentication.

## For AI agents

Search Chilean public-procurement opportunities, manage tender follow-up, and coordinate workspace members and offers via 225 bearer-authenticated endpoints.

## Scope

Does not handle Chilean tax filing, payroll, or banking - use for Chilean public-procurement tender discovery and bid coordination only.

## Capabilities

- Search and follow Chilean public-tender opportunities scraped from Mercado Publico and other Chile procurement systems
- Assign tender opportunities across workspace members with bulk follow, unfollow, and tag operations
- Track tender deadlines and milestones through the calendar and notification endpoints
- Submit offers and manage guarantee documents associated with tender responses
- Authenticate users via login, Google OAuth, and token-validation endpoints
- Manage business-line classifications to filter relevant tender opportunities for each workspace

## Use cases

### Tender Discovery Pipeline

Continuously surface new Chilean public-tender opportunities relevant to a workspace's business lines, then filter and assign them to the right team members. The opportunities endpoints support search, push-by-code, share, and assignment in bulk. Setup takes under a day for a workspace already authenticated against Licitalab.

Example prompt: List opportunities for the current workspace filtered by business line 'construction', then assign the top five to user ID 'member-42'

### Bid Response Workflow

Coordinate tender bid responses by tracking deadlines, attaching offer documents, and managing guarantees. The Offers, Attachments, and Guarantee tags expose document submission and bond tracking. This replaces manual spreadsheet workflows with an API-driven response pipeline.

Example prompt: Upload an attachment to opportunity code 'OP-2026-0145' and create a guarantee record with amount 5000000 CLP

### Workspace Notifications and Calendar

Centralize tender deadlines and updates in a workspace calendar with notifications when status changes. The Notification, Calendar, and Dashboard tags expose realtime workspace state. Useful for procurement teams managing dozens of concurrent tenders.

Example prompt: Fetch all unread notifications for workspace ID 'ws-123' and produce a calendar view of deadlines in the next seven days

### AI Agent Procurement Assistant

An AI agent uses Jentic to call Licitalab opportunities, calendar, and notification endpoints to summarize the day's tender activity for a Chilean procurement team. The agent filters by business line, surfaces priority deadlines, and drafts assignment recommendations. Credentials are isolated through Jentic.

Example prompt: Search Jentic for 'find Chilean tender opportunities', load the opportunities-by-workspace schema, fetch today's matches, and post a summary

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/v1/auth/login` | Authenticate user and issue bearer token |
| POST | `/api/v1/opportunities/create` | Create a new tender opportunity record |
| GET | `/api/v1/opportunities/workspace` | List opportunities for the current workspace |
| GET | `/api/v1/opportunities/code/{code}/details` | Get full details of an opportunity by code |
| PUT | `/api/v1/opportunities/follow-list` | Follow multiple opportunities in bulk |
| PUT | `/api/v1/opportunities/assign-list` | Assign multiple opportunities to a workspace member |

## Key resources

- **Auth** — Login, token validation, and Google OAuth authentication endpoints
- **Opportunities** — Search, follow, assign, share, and update Chilean tender opportunities
- **Members** — Manage workspace members and per-member tender assignments
- **Offers** — Submit and track offers attached to tender opportunities
- **Guarantee** — Manage guarantee bonds required for tender responses
- **Notification** — Workspace notifications and read-state tracking

## Why Jentic

- **Setup:** Wiring the Licitalab API by hand means logging in for a JWT bearer token, keeping it refreshed, finding which of the 225 operations cover tender discovery and bid coordination, and calling api2.licitalab.cl yourself. Through Jentic you install once, import the Licitalab API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Licitalab reads a tender by code in the path (`/opportunities/code/{code}/details`) but coordinates through workspace and list operations, so scope the agent to the operations it needs, such as searching opportunities or following a tender. You leave out assign or follow-list writes unless you add them, so it only calls the ones you allow.
- **Credential handling:** Your Licitalab bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find Chilean tender opportunities', and Jentic returns the matching Licitalab operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **HubSpot Account Info** — Push won-tender data into HubSpot CRM as deals after Licitalab tracks the opportunity
- **Salesforce Platform API** — Sync tender opportunities into Salesforce as opportunity records
- **Outreach Sales Engagement** — Trigger sales sequences when Licitalab surfaces a high-value tender

## FAQ

### Why is there no official OpenAPI spec for Licitalab?

Licitalab does not publish a maintained OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Licitalab API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Licitalab API use?

Licitalab uses HTTP bearer authentication. Tokens are issued via `/api/v1/auth/login` or `/api/v1/auth/google` and validated through `/api/v1/auth/validate.` Through Jentic, bearer tokens are stored in your Jentic One instance and injected at execution time.

### Can I follow Chilean public tenders programmatically with the Licitalab API?

Yes. Use POST `/api/v1/opportunities/push_code` to push a tender code into the workspace, PATCH `/api/v1/opportunities/followed/{code}` to follow it, and PUT `/api/v1/opportunities/follow-list` to follow many at once.

### What are the rate limits for the Licitalab API?

The spec does not document explicit rate limits. Treat workspace-scoped endpoints as moderately throttled; back off on HTTP 429 and use bulk operations such as `/api/v1/opportunities/added-opportunities` to reduce request volume.

### How do I assign a tender to a team member through Jentic?

Run pip install jentic, then search Jentic with 'assign a Licitalab tender to a member' to retrieve the `/api/v1/opportunities/assign-list` operation. Execute it with the opportunity codes and target member ID; Jentic handles the bearer token automatically.

### Is the Licitalab API free?

Licitalab is a paid SaaS for Chilean procurement teams. API access is included with paid workspace plans; check licitalab.cl for current pricing tiers.

### Can I limit what my agent is allowed to do with the Licitalab API?

Yes. Because you run Jentic One yourself, your own rules decide which of the 225 Licitalab operations and which bearer credentials the agent can use. You can allow read-only calls such as searching opportunities or fetching a tender by code with GET `/api/v1/opportunities/code/{code}/details`, while leaving out write operations like PUT `/api/v1/opportunities/follow-list` and PUT `/api/v1/opportunities/assign-list.` The agent can then only call the endpoints you have explicitly permitted.