Process Pre-Alert — Argentina 🇦🇷

Country-specific rules. Auth, routing (air/ground), request shape, the completeness contract, and the error envelope are the same for every country — see the main endpoint page: Process Pre-Alert (JSON). This page covers only what's specific to Argentina.

A manifest is routed to Argentina when its destination resolves to AR (destination_airport: "EZE" / AEP / COR / CBA for air, or destination_country: "AR" for ground) and AR is in your allowed_countries.

Required fields (Argentina)

On top of the shared required fields, Argentina needs:

Field	Rule
consignee_rut	The document number. CUIT/CUIL (validated, mod-11) when consignee_document_type is CUIT/CUIL; DNI only needs to be non-empty.
consignee_type	C (comercial) or P (particular). P triggers a cupo check (see below); C skips it.
weight_kg, fob_usd	Must be > 0.
internal_number	Chile-only — send null.
shipper_name, shipper_address, shipper_city, shipper_country	Required. They are positional fields of AIDA record 02 and of MANIELEC. A missing value is written as a blank position with no error, so the customs file leaves incomplete. (Chile exempts them; Argentina does not.)
insurance_usd	Required. Also an AIDA record-02 position, and the fallback CIF is fob + freight + insurance.
iva_override	Optional on AR — no effect on the current AR customs model. May be omitted or null; the default derives from the company's is_iva_registered. (Required on CL and PE.)
order_created_at	Optional on AR — accepted but not yet persisted. (Required on CL and PE.)
internal_number	Optional on AR — send null. (Required on CL and PE.)

Top-level (manifest header) fields

Field	Rule
dispatcherDocument	Required — customs broker (despachante) document, 7–11 digits. The customs file generation fails without it.
cargoReference	Optional — send null and the server auto-generates a unique reference.
licensePlate	Optional — the delivery vehicle plate. Used on ground shipments (written into the customs file).

Request example (Argentina)

curl -X POST https://api.logirai.com/api/manifests/process-pre-alert-json \
  -H "Authorization: Bearer $API_PASSWORD" \
  -H "Content-Type: application/json" \
  -d @body-ar.json

{
  "mawbNumber": "111-22334455",
  "transportMode": "air",
  "flightData": {
    "flight_number": "LA8074",
    "origin_airport": "PVG",
    "destination_airport": "EZE",
    "origin_country": "CN",
    "scheduled_departure": "2026-06-10T02:00:00+08:00",
    "scheduled_arrival": "2026-06-10T18:30:00-03:00"
  },
  "dispatcherDocument": "30715432",
  "cargoReference": null,
  "licensePlate": null,
  "guideRows": [
    {
      "hawb": "AR-AWB-001",
      "consignee_name": "María González",
      "consignee_rut": "20312345677",
      "consignee_type": "P",
      "consignee_document_type": "CUIL",
      "consignee_address": "Av. Corrientes 1234, Piso 5",
      "consignee_city": "Buenos Aires",
      "consignee_state": "C",
      "consignee_zip_code": "C1043AAZ",
      "consignee_phone": "+541145678900",
      "consignee_email": "maria.gonzalez@example.com.ar",
      "consignee_country": "AR",
      "shipper_name": "Shanghai Trading Co.",
      "shipper_address": "123 Nanjing Road",
      "shipper_city": "Shanghai",
      "shipper_country": "CN",
      "packages_count": 1,
      "weight_kg": 1.8,
      "description_original": "Wireless bluetooth earphones",
      "hs_code": "8518.30.0000",
      "fob_usd": 39.9,
      "product_value": 39.9,
      "freight_usd": 7.0,
      "insurance_usd": 1.0,
      "currency": "USD",
      "internal_number": null,
      "iva_override": null,
      "extra_data": {}
    }
  ]
}

Cupo check (particulares)

For every row with consignee_type = "P", the server checks the consignee's import quota (cupo):

• Cupo OK → guide is registered.
• Cupo exceeded / document problem / lookup error → guide is created as pending_cuit_correction, and a correction email is sent to the consignee (non-blocking).

C (comercial) rows skip the cupo check entirely.

Other behavior

• Platform resolution (consolidator clients). If your token is a consolidator client, every row must carry the platform_rut + merchant_name keys (value may be null). On AR this is identity capture only: platform_rut resolves to guides.platform_company_id and merchant_name is persisted, but — unlike CL — the AR customs model (CUIT / NCM) does not branch on platform registration. A null / unmatched platform_rut leaves platform_company_id empty and is never a rejection reason.
• Orphan auto-attach. Guides left unattached from a previous run (same company) are linked to this manifest before the new rows are inserted. The count is returned.
• Multi-product hs_code → AIDA. If a guide uses products[] with several distinct hs_codes, the derived guide hs_code is a joined multi-code string (e.g. "111 - 999"). The AIDA record-04 generator writes it verbatim — that exact string reaches ARCA. Only send multi-code HAWBs for AR if your customs flow accepts it; otherwise send one product (or one shared hs_code) per guide.

Response (Argentina)

201 Created:

{
  "success": true,
  "cargo_reference": "TR001",
  "guides_created": 5,
  "guides": [{ "hawb": "AR-AWB-001", "tracking_code": "TR-A1B2C3" }],
  "guides_reassigned_from_orphan_pool": 0,
  "pending_cuit_correction_count": 1,
  "flight_id": "uuid",
  "transport_mode": "air",
  "errors": [],
  "warnings": []
}

Field	Meaning
cargo_reference	The (possibly auto-generated) cargo reference for this manifest.
guides_reassigned_from_orphan_pool	Orphan guides linked to this manifest.
pending_cuit_correction_count	Guides held for cupo/document correction.