# Crowley Shipping & Logistics Advisories Scraper (`arman-bd/crowley-shipping-advisories-scraper`) Actor

Scrape Crowley Maritime's surcharge, terminal handling charge, port omission and vessel schedule change notices as structured JSON, with the full notice body, classified by type and date-filterable.

- **URL**: https://apify.com/arman-bd/crowley-shipping-advisories-scraper.md
- **Developed by:** [Arman Hossain](https://apify.com/arman-bd) (community)
- **Categories:** News, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 notice scrapeds

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Crowley Shipping & Logistics Advisories Scraper

![Crowley Advisories: Every customer notice, rate change and terminal handling charge, with full body text](https://api.apify.com/v2/key-value-stores/ZQOcNAOHrIgTacAmy/records/crowley-shipping-advisories-scraper.jpg)

Crowley Maritime publishes its surcharge changes, terminal handling charges, port omissions and vessel schedule updates as regular posts on crowley.com, one notice per event. This Actor reads that feed as structured JSON: the classified notice type, the full body text (effective dates, charge amounts, ports affected), and the publish and last-modified timestamps, filterable by date range and full-text search.

This is the schedule-change and local-charge-tariff slice of Crowley's Latin America, Caribbean, Central America and Puerto Rico trades, the kind of update that otherwise arrives as a PDF attachment on a mailing list.

**Agent skill: [SKILL.md](https://api.apify.com/v2/key-value-stores/t7YoTxpZEJOWvw4Ug/records/crowley-shipping-advisories-scraper.md)**

```
https://api.apify.com/v2/key-value-stores/t7YoTxpZEJOWvw4Ug/records/crowley-shipping-advisories-scraper.md
```

### What you get

| Field | What it holds |
|---|---|
| `id` | Crowley's post ID, the stable identifier for this notice |
| `noticeType` | Classified from the title: `SURCHARGE`, `TERMINAL_HANDLING_CHARGE`, `VESSEL_SCHEDULE_CHANGE`, `PORT_OMISSION`, `RATE_OR_CHARGE_CHANGE`, `HOLIDAY_SCHEDULE`, `WEATHER_ADVISORY`, `REGULATORY_NOTICE`, or `OTHER` when nothing fits |
| `title` | Notice title, HTML entities decoded |
| `slug` | URL slug |
| `link` | Canonical URL on crowley.com |
| `publishedAt`, `modifiedAt` | ISO 8601 UTC timestamps |
| `excerpt` | Auto-generated teaser, plain text |
| `content` | The full notice body as plain text: effective dates, charge tables flattened to readable lines, ports affected |
| `categories` | Crowley's own WordPress category IDs on the post |
| `postType` | Always `post` for this feed |
| `scrapedAt` | Run timestamp |

`RUN_SUMMARY` in the key-value store holds per-run counts, the filters you used, any date or notice-type value that could not be understood, and any page that failed.

### Use cases

- **Freight audit and pay.** Diff `content` against a customer's invoice line items to catch a surcharge that changed before the invoice was generated.
- **Rate management platforms.** Pull `noticeType: SURCHARGE` and `TERMINAL_HANDLING_CHARGE` on a schedule to keep a local-charge tariff table current without a human reading PDFs.
- **Forwarder and BCO alerts.** Filter to `VESSEL_SCHEDULE_CHANGE` and `PORT_OMISSION` for a lane-specific booking-risk feed.
- **Competitive intelligence.** Track how often and by how much a carrier adjusts fuel surcharges relative to bunker price moves.
- **Compliance monitoring.** `REGULATORY_NOTICE` surfaces documentation, inspection and tariff-ruling notices that affect customs clearance.

### Quick start

The most recent notices, no filtering at all:

```json
{}
```

Everything published this year in the two families that hit an invoice hardest:

```json
{
 "noticeTypes": ["SURCHARGE", "TERMINAL_HANDLING_CHARGE"],
 "after": "2026-01-01",
 "maxNotices": 200,
 "maxPages": 10
}
```

A full-text search across the whole feed:

```json
{
 "search": "Costa Rica",
 "maxNotices": 50
}
```

### Input

| Field | Type | Default | Notes |
|---|---|---|---|
| `after` | string | (none) | Earliest publish date to keep, `YYYY-MM-DD` or a full ISO timestamp. An unparseable value is dropped and recorded in `RUN_SUMMARY.invalidInputs`, not treated as fatal. |
| `before` | string | (none) | Latest publish date to keep, same format as `after`. |
| `search` | string | (none) | Full-text search applied server-side across the notice title and body. |
| `noticeTypes` | array | `[]` | Keep only these classified families. An unknown value is dropped and recorded in `RUN_SUMMARY.invalidInputs` rather than silently matching nothing. Empty means every type, including `OTHER`. |
| `order` | string | `desc` | `desc` for newest first, `asc` for oldest first. |
| `maxNotices` | integer | `100` | Total saved for the run, the most you can be charged for. `0` means no limit, bounded only by `maxPages`. |
| `maxPages` | integer | `5` | How many 100-notice pages to walk. The category holds roughly 1,900 notices, so 19 pages is a full backfill; raise this when a strict `noticeTypes` filter throws most of a page away. |

Nothing is required. Running with no input returns the most recent notices across every type.

### Output example

```json
{
 "id": 74740,
 "noticeType": "TERMINAL_HANDLING_CHARGE",
 "title": "Costa Rica Terminal Handling Charge Effective 09-13-2026",
 "slug": "costa-rica-terminal-handling-charge-effective-09-13-2026",
 "link": "https://www.crowley.com/uncategorized/costa-rica-terminal-handling-charge-effective-09-13-2026/",
 "publishedAt": "2026-08-14T20:25:15Z",
 "modifiedAt": "2026-08-14T20:25:20Z",
 "excerpt": "Effective September 13, 2026, Crowley will implement an increase to the Costa Rica Terminal Handling Charge on inbound and outbound loads via Costa Rica ports.",
 "content": "Effective September 13, 2026, Crowley will implement an increase to the Costa Rica Terminal Handling Charge on inbound and outbound loads via Costa Rica ports. This adjustment is due to operational cost increases from APM terminals.\n\nEquipment | Direction | Previous Charge | New Charge |\nAll Containerized Equipment | Inbound | $650 | $675 |\nAll Containerized Equipment | Outbound | $585 | $610 |",
 "categories": [13, 1],
 "postType": "post",
 "scrapedAt": "2026-08-21T22:41:37.000Z"
}
```

Charge tables in the body are flattened from HTML into `|`-joined lines, one per row, so the amounts and directions in `content` stay readable and parseable without a browser or an HTML parser on your end.

### API example

```bash
curl -X POST "https://api.apify.com/v2/acts/arman-bd~crowley-shipping-advisories-scraper/run-sync-get-dataset-items?token=YOUR_TOKEN" \
 -H "Content-Type: application/json" \
 -d '{
 "noticeTypes": ["SURCHARGE", "TERMINAL_HANDLING_CHARGE"],
 "maxNotices": 100
 }'
```

### JavaScript example

```js
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('arman-bd/crowley-shipping-advisories-scraper').call({
 noticeTypes: ['VESSEL_SCHEDULE_CHANGE', 'PORT_OMISSION'],
 after: '2026-01-01',
 maxNotices: 100,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
for (const n of items) console.log(`${n.noticeType} | ${n.title} | ${n.publishedAt}`);
```

### Notes

- The category is resolved by its slug (`shipping-logistics-announcements`) at the start of every run rather than a fixed ID, so this keeps working if Crowley's site restructures its taxonomy.
- `noticeType` is classified from the title using ordered pattern matching built from the titles actually observed in the feed. Most notices land cleanly in one family; anything that does not fit is `OTHER`, not forced into the nearest guess.
- `maxNotices` and `maxPages` bound the run from two directions, whichever is hit first stops it. A strict `noticeTypes` filter over a quiet window can exhaust `maxPages` before reaching `maxNotices`; raise `maxPages` in that case.
- `content` is fetched in the same request as the listing, no second fetch per notice is needed to get the full body.
- `after` and `before` accept a bare date or a full timestamp. A bare date is anchored to the start of that day for `after` and the end of that day for `before`, so `after: "2026-01-01", before: "2026-01-31"` covers the whole month.
- An unparseable date or an unrecognized `noticeTypes` value never fails the run. It is dropped, and `RUN_SUMMARY.invalidInputs` names exactly which field and value were ignored.

### FAQ

**Do I need an account or API key?** No. The feed is read without credentials.

**How far back does this go?** The category holds roughly 1,900 notices going back over a decade, though the volume of surcharge and schedule notices increases sharply in recent years. `maxPages` up to 19 to 20 covers a full backfill at the default page size.

**Why do some notices classify as `OTHER`?** The feed also carries the occasional operational or terminal-system notice that does not fit any of the eight named families. `content` still carries the full body either way.

**Can I get only new notices since my last run?** Yes. Set `after` to the `publishedAt` of the newest notice you already have, and `order: "asc"` if you want to walk forward chronologically.

**Does this cover other carriers?** No, this Actor is scoped to Crowley Maritime's own advisories feed.

# Actor input Schema

## `after` (type: `string`):

Earliest publish date to keep, as YYYY-MM-DD (or a full ISO timestamp). Leave empty for no lower bound. An unparseable value is ignored and recorded in RUN\_SUMMARY.invalidInputs rather than failing the run.

## `before` (type: `string`):

Latest publish date to keep, as YYYY-MM-DD (or a full ISO timestamp). Leave empty to run through to the most recent notice. An unparseable value is ignored and recorded in RUN\_SUMMARY.invalidInputs rather than failing the run.

## `search` (type: `string`):

Full-text search applied server-side across the notice title and body, e.g. 'Costa Rica' or 'bunker'. Leave empty to skip full-text filtering entirely.

## `noticeTypes` (type: `array`):

Keep only notices classified into these families, matched from the title after fetching. Leave empty to keep every notice type, including ones that don't fit any of these buckets (OTHER).

## `order` (type: `string`):

Newest first (desc) or oldest first (asc). Applies to both the fetch order and, combined with 'Max notices', which notices you get when the cap binds first.

## `maxNotices` (type: `integer`):

Stop once this many notices have been saved. This is also the most you can be charged for in one run. Set 0 for no limit, bounded only by 'Max pages'.

## `maxPages` (type: `integer`):

How many 100-notice pages to walk. The category holds roughly 1,900 notices, so 19 pages covers a full backfill; raise this when a strict 'Notice types' filter throws most of a page away.

## Actor input object example

```json
{
  "after": "2026-01-01",
  "before": "2026-06-30",
  "search": "Terminal Handling Charge",
  "noticeTypes": [
    "SURCHARGE",
    "TERMINAL_HANDLING_CHARGE"
  ],
  "order": "desc",
  "maxNotices": 100,
  "maxPages": 5
}
```

# Actor output Schema

## `items` (type: `string`):

Every notice the run produced.

## `runsummary` (type: `string`):

The RUN\_SUMMARY record from the run's key-value store.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("arman-bd/crowley-shipping-advisories-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("arman-bd/crowley-shipping-advisories-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call arman-bd/crowley-shipping-advisories-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,arman-bd/crowley-shipping-advisories-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/FAQrMteey0eUBle86/builds/f8RR8Pa1pUx7LcPMC/openapi.json