Karrio is a shipping API and dashboard that unifies carrier operations such as labels, tracking, webhooks, and shipment workflows. The documented API uses API keys, with HTTP Basic authentication as the primary form and a bearer-style Authorization: Token form for cross-origin requests. The key is presented as a privileged secret because it can drive shipment operations.

A Karrio instance is therefore more than a logistics dashboard. It is an integration point that may hold carrier credentials, customer addresses, parcel details, webhook destinations, and permission to create billable shipments. The inventory question should identify the instance and its exposed surfaces, then move to the API key and carrier-connection model.

The Karrio OpenAPI reference says all API requests must use HTTPS and that unauthenticated requests fail. Those are useful baseline properties, not proof that a deployment is safely configured. A reverse proxy can terminate TLS while leaving the upstream API exposed on a broader network. The browser dashboard and the API may also have different access controls.

Query plan

The initial candidates are app="Karrio" and title="Karrio" with sub_type=all, page 1, and page size 1. The application and title observations are separate. A title match can identify a login page or documentation site; it does not prove that the shipping API is reachable. The live counts are not reported because the authorized SDK execution was rejected by the platform during this run.

Treat a candidate as a host to verify through ownership records, not as a host to probe. If a later approved measurement produces a count, preserve the query role, exact time, scope, and status. Compare only observations collected with the same page size and subtype.

Map the integration authority

Inventory the API keys, their owners, creation dates, last use, and the operations they can perform. Separate test keys from production keys and separate label creation from read-only tracking. Test whether a revoked key stops working across the dashboard, API, and any queued jobs.

List carrier connections and the credentials behind them. A carrier sandbox connection should not be usable to create production labels. Verify that webhook endpoints are authenticated, that retries are bounded, and that a webhook cannot be redirected to an arbitrary internal address. The documented webhook API can create and manage endpoints, so the right to change a webhook is part of the integration boundary.

Review shipment and parcel objects for sensitive data. Addresses and phone numbers have privacy value even when no label is generated. Limit export access and retention. Check whether the instance metadata endpoint reveals application features and host details that help an unauthenticated observer map the deployment.

Protect the operator path

Use strong authentication for the dashboard and separate administrative accounts from automation keys. Put the dashboard behind a trusted network path and monitor login failures. Restrict the API to the expected source networks where possible, but do not let a network rule replace key scope and rotation.

Store API keys in a secret manager rather than in CI logs or browser code. Use distinct keys for each integration, with a documented owner and revoke path. Rotate keys after staff changes, provider changes, or suspicious activity. Keep an audit record that links a shipment action to the key or user that requested it.

Respond to an unexpected instance

Confirm ownership through the organization's cloud and DNS records. Check the product banner and response body, but do not submit credentials or attempt a login on an unknown host. If the instance belongs to the organization, review recent keys, carrier connections, webhook changes, and shipment creation. If it is unauthorized, isolate the host and preserve logs before cleanup.

Karrio's API is designed to make shipping workflows programmable. That is exactly why its keys need a stronger lifecycle than a normal dashboard session. Count the instance, then review the authority behind it.

References