All connectors
Implemented
Procurement, logistics & supply chain

Envia Shipping

Discover active shipping carriers by country through Envia, including Latin American shipping origins.

Discover active shipping carriers by country through Envia, including Latin American shipping origins.

Source actions

1

Destination actions

0

Data types

1

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

carriers
  • List country shipping carriers
    Source

    Read active carriers for the configured origin country; no label is purchased.

    carriers.list

Authentication

Provider-issued access token

Plans and access

Envia Queries API account with a bearer token. Carriers and services depend on the selected origin country and route; the API response determines availability.

Test environment

Separate test environment and token; Nexra provider sandbox validation has not run.

Rate limits

Provider account quotas apply; HTTP 429 uses bounded retries and Retry-After when supplied.

Pagination

Country carrier discovery returns one data array.

Provider events

Not included in this read-only batch. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

  • Fixture-tested implementation only; provider sandbox and authorised-account validation have not run.
  • Only the listed reads are implemented. Writes, consent flows and automatic access-token refresh are not included.

Developer reference

  1. Create the Envia Shipping credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Envia Shipping, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide

Machine-readable detail: GET /api/public/connect/connectors/envia and the Connections API.