Correos de Costa Rica Tracker
Pricing
from $0.01 / 1,000 results
Correos de Costa Rica Tracker
Track Correos de Costa Rica shipping guides by logging into the sucursal portal and scraping tracking events.
Pricing
from $0.01 / 1,000 results
Rating
0.0
(0)
Developer
ainnllus
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
3 days ago
Last modified
Categories
Share
Tracks shipping guides (guías) via the Correos de Costa Rica sucursal portal. Logs in once, queries each guide, and writes one dataset item per guide with current status and full event history.
Input
| Field | Type | Required | Description |
|---|---|---|---|
username | string | Yes | Correos portal username |
password | string | Yes | Correos portal password (secret) |
trackingNumbers | string[] | Yes | Guide numbers, e.g. ["PY999999999CR"] |
delaySeconds | integer | No | Delay between guide queries to avoid rate limiting (default: 1) |
Output
One dataset item per guide:
| Field | Description |
|---|---|
trackingNumber | Guide number (as confirmed by the portal) |
status | Normalized enum: delivered, in_transit, or not_found. An explicit delivery event (code EMI) overrides a stale estado label |
estado | Human-readable status as shown on the page (e.g. Entregado) |
fechaRecepcion | Reception/start date, e.g. 2026-08-11 14:40:56 |
destinatario | Destination address, when the portal shows it |
recibidoPor | Name of the person who received the shipment, when delivered |
eventos | Event history in chronological order (see below) |
eventCount | Number of events |
ok | true if the portal responded without errors |
error | Error message, if any |
Each event in eventos:
| Field | Description |
|---|---|
sucursal | Office/location where the event occurred |
fecha | Event date, DD/MM/YY |
hora | Event time, HH:MM AM/PM |
descripcion | Event description |
codigo | Portal event code: EMA (admitted), EMB (distribution center), EMF (internal transfer), EMG (received at office), EDG (out for delivery), EMI (delivered) |
lat, lng | Delivery coordinates, present on the delivery event when the portal provides a location map |
Pricing
Pay per event — no subscription:
| Event | Price |
|---|---|
| Actor start | $0.00005 per run |
| Guide query | $0.01 per guide (one dataset item, whether delivered, in transit, or not found) |
A run that fails to log in costs only the start fee. A daily schedule checking 5 guides costs roughly $1.50/month.
Usage
Run from the Apify Console, the API, or on a schedule (create a Task with saved input and attach a Schedule for recurring runs).
Example run via API:
Local development
Notes
- The portal is protected by a WAF (Radware). Requests from Apify datacenter IPs may occasionally be blocked with 403s; retry, or add Apify Proxy support if it becomes a persistent problem.
- Login is a single session reused across all guides in one run; sessions are not persisted between runs.
