Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/envia:envia-carriers-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Envia Queries Carriers API
version: v2.3.1
description: Read-only service for lookups, lists, and account utilities. This API provides access to countries, states, cities, carriers, services, and address structure information needed for shipping operations. Use this API to get the required information for building shipping forms and validating addresses. The Queries API is designed for developers who need read-only access to reference data such as supported carriers, available services, shipment history, and user account settings. It serves as the lookup layer of the Envia platform, enabling applications to populate dropdowns, validate inputs, and retrieve shipment details without modifying any data.
contact:
name: Envia API Support
url: https://docs.envia.com/discuss
license:
name: Proprietary
url: https://www.envia.com/terminos-y-condiciones
termsOfService: https://www.envia.com/terminos-y-condiciones
servers:
- url: https://queries.test.envia.com/
description: Sandbox/Test
- url: https://queries.envia.com/
description: Production
security:
- bearerAuth: []
tags:
- name: Carriers
description: Get available carriers by country
paths:
/available-carrier-detailed/{country}/{international}/{shipment_type_id}:
get:
tags:
- Carriers
summary: Get Carriers (Detailed)
description: Return available couriers for the given **country**, **international** flag (0 or 1) and **shipment_type_id** (1 = Parcel, 2 = Freight/LTL, 3 = Full Truck Load).
operationId: available-couriers-detailed
parameters:
- name: country
in: path
required: true
schema:
type: string
example: MX
enum:
- MX
- US
- CO
- CA
- AR
- CL
- GT
- ES
- IN
- FR
- IT
- BR
description: Country code of courier origin.
- name: international
in: path
required: true
schema:
type: integer
enum:
- 0
- 1
example: 0
description: Defines if return international couriers.
- name: shipment_type_id
in: path
required: true
schema:
type: integer
enum:
- 1
- 2
- 3
example: 1
description: "Defines if needs return couriers by shipment type.\n\n| ID | Shipment type |\n| :-----| :--------:|\n| 1 | Parcel |\n| 2 | LTL (Consolidated Charge) | \n| 3 | FTL (Full TruckLoad) |"
responses:
'200':
description: Successful response
content:
application/json:
schema:
type: object
properties:
data:
type: array
items:
type: object
properties:
carrier_id:
type: integer
example: 9
default: 0
description: Courier identification number
carrier_name:
type: string
example: ups
description: Courier description name
country_code:
type: string
example: MX
description: Origin country of the courier
endpoint:
type: string
example: https://api-clients.envia.com/
description: Url used to works via API
active:
type: integer
example: 1
default: 0
description: Flag to check if the courier is active.
reason:
type: string
example: Active
description: Short description in case of the courier is not active.
examples:
MX Domestic Parcel:
summary: MX Domestic, Shipment Type = Parcel
value:
data:
- carrier_id: 9
carrier_name: ups
country_code: MX
endpoint: https://api-clients.envia.com/
active: 1
reason: Active
- carrier_id: 12
carrier_name: dhl
country_code: MX
endpoint: https://api-clients.envia.com/
active: 1
reason: Active
/carrier:
get:
tags:
- Carriers
summary: Get Carriers by Country
description: 'Returns the list of shipping carriers that are currently active and available for a given country. Use this endpoint to discover which carriers you can use when creating shipments.
**When to use:** Call this endpoint to populate carrier selection dropdowns in your shipping forms, or to programmatically determine which carriers are available before requesting a shipping quote.
**Prerequisites:**
- Valid JWT token in the Authorization header
- A valid two-letter ISO country code (e.g., `MX`, `US`, `CO`)
**Key behaviors:**
- Returns only carriers that are currently active for the specified country
- Each carrier object includes the carrier `name` (used as identifier in other API calls), a human-readable `description`, and an `active` status flag
- The carrier `name` value returned here is the exact identifier you must pass to the `/service` endpoint and the Shipping API when creating shipments'
operationId: carriers-by-country
parameters:
- name: country_code
in: query
required: true
description: Two-digit country code
schema:
type: string
example: MX
responses:
'200':
description: Successful response
content:
application/json:
schema:
type: object
properties:
data:
type: array
description: List of carriers
items:
type: object
properties:
id:
type: integer
description: Carrier id. Use it as `carrier_id` in `GET /carrier-action/{carrier_id}` and as `carrierId` in `POST /branches/{carrier}/{country_code}` live lookups.
example: 172
name:
type: string
description: Carrier name
example: fedex
description:
type: string
description: Carrier description
example: FedEx
country_code:
type: string
description: Country code
example: MX
active:
type: boolean
description: Whether the carrier is active
example: true
/carrier-action/{carrier_id}:
get:
tags:
- Carriers
summary: Get Carrier Actions by Carrier
description: Retrieve carrier action for the specified carrier id. Requires Bearer JWT authentication.
operationId: carrier-actions-by-carrier
parameters:
- name: carrier_id
in: path
required: true
description: Carrier identificator
schema:
type: integer
example: 1
responses:
'200':
description: Successful response
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
description: Indicates if the request was successful
data:
type: array
description: List of carrier actions
items:
type: object
properties:
id:
type: integer
description: Action ID
name:
type: string
description: Action name
description:
type: string
description: Action description
/carrier/{carrier_id}:
get:
tags:
- Carriers
summary: Get Single Carrier
description: Get detailed information about a specific carrier.
operationId: carrier-by-id
parameters:
- name: carrier_id
in: path
required: true
description: Carrier identificator
schema:
type: integer
example: 1
responses:
'200':
description: Successful response
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
description: Indicates if the request was successful
data:
type: object
description: Carrier information
properties:
id:
type: integer
description: Carrier ID
name:
type: string
description: Carrier name
code:
type: string
description: Carrier code
active:
type: boolean
description: Whether the carrier is active
services:
type: array
description: Available services for this carrier
items:
type: object
properties:
id:
type: integer
description: Service ID
name:
type: string
description: Service name
code:
type: string
description: Service code
components:
securitySchemes:
bearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
externalDocs:
description: Full Envia API Documentation
url: https://docs.envia.com
x-provenance:
method: searched
source: https://docs.envia.com/reference
harvested: '2026-10-27'
tool: harvest-readme-openapi.py
note: Assembled verbatim from the OpenAPI definition ReadMe embeds in each operation page of the provider's developer portal; paths and components merged by API title, nothing authored.
assembled_from:
- https://docs.envia.com/reference/active-notifications.md
- https://docs.envia.com/reference/additional-services-by-locale.md
- https://docs.envia.com/reference/additional-services.md
- https://docs.envia.com/reference/addresses-by-type.md
- https://docs.envia.com/reference/all-addresses.md
- https://docs.envia.com/reference/all-countries.md
- https://docs.envia.com/reference/all-packages.md
- https://docs.envia.com/reference/all-provinces.md
- https://docs.envia.com/reference/all-webhooks.md
- https://docs.envia.com/reference/available-carriers-by-shipment-type.md
- https://docs.envia.com/reference/available-couriers-detailed.md
- https://docs.envia.com/reference/available-services.md
- https://docs.envia.com/reference/cancel-dce.md
- https://docs.envia.com/reference/carrier-actions-by-carrier.md
- https://docs.envia.com/reference/carrier-branches.md
- https://docs.envia.com/reference/carrier-by-id.md
- https://docs.envia.com/reference/carrier-print-options.md
- https://docs.envia.com/reference/carriers-by-country.md
- https://docs.envia.com/reference/country-address-structure.md
- https://docs.envia.com/reference/country-by-code.md
- https://docs.envia.com/reference/country-locale.md
- https://docs.envia.com/reference/create-ndr-request.md
- https://docs.envia.com/reference/create-package.md
- https://docs.envia.com/reference/create-shop-shipping-rule.md
- https://docs.envia.com/reference/create-user-address.md
- https://docs.envia.com/reference/create-webhook.md
- https://docs.envia.com/reference/deactivate-company-notifications.md
- https://docs.envia.com/reference/default-shop-services.md
- https://docs.envia.com/reference/default-user-address.md
- https://docs.envia.com/reference/default-user-print.md
- https://docs.envia.com/reference/download-labels-bulk.md
- https://docs.envia.com/reference/estafeta-branches-mexico.md
- https://docs.envia.com/reference/generate-dce.md
- https://docs.envia.com/reference/get-orders.md
- https://docs.envia.com/reference/invoice-detail.md
- https://docs.envia.com/reference/ndr-history.md
- https://docs.envia.com/reference/ndr-shipment-actions.md
- https://docs.envia.com/reference/payment-history.md
- https://docs.envia.com/reference/province-by-code.md
- https://docs.envia.com/reference/remove-package.md
- https://docs.envia.com/reference/remove-user-address.md
- https://docs.envia.com/reference/select-shipping-rule-for-order.md
- https://docs.envia.com/reference/serviceable-countries.md
- https://docs.envia.com/reference/services-by-carrier-and-country.md
- https://docs.envia.com/reference/services-by-carrier.md
- https://docs.envia.com/reference/shipment-by-tracking.md
- https://docs.envia.com/reference/shipment-types.md
- https://docs.envia.com/reference/shipments-by-month-year.md
- https://docs.envia.com/reference/shop-by-url.md
- https://docs.envia.com/reference/shop-shipping-rule.md
- https://docs.envia.com/reference/shop-shipping-rules.md
- https://docs.envia.com/reference/state-by-code.md
- https://docs.envia.com/reference/states-by-country.md
- https://docs.envia.com/reference/update-package.md
- https://docs.envia.com/reference/update-shop-shipping-rules.md
- https://docs.envia.com/reference/update-user-address.md
- https://docs.envia.com/reference/update-webhook.md
- https://docs.envia.com/reference/webhook-types.md
merge:
pages: 58
deduped: 57
conflicts_kept_first: 0