Envia.com Manifest API

The Manifest API from Envia.com — 1 operation(s) for manifest.

Operations 1

POST /ship/manifest Create a Shipping Manifest #

Specifications

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.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/envia:envia-manifest-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

envia-manifest-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Envia Shipping API — Complete Documentation Manifest API
  version: v2.3.0
  description: 'Shipping API to connect with over 100 couriers worldwide. Shipping made simple for e-commerces and enterprises. Envia''s Shipping Web Services offers solutions that applications can use to quote, create labels, request pickups, track packages, cancel shipments and many other logistics operations in USA, Mexico, Colombia, Brazil, India, Canada, Argentina, Chile, Guatemala, Spain, Italy and France. This API is built for e-commerce platforms, logistics teams, and enterprise applications that need a single integration to access multi-carrier shipping capabilities. Core features include real-time rate comparison, label generation, package tracking, pickup scheduling, shipment cancellation, and webhook-based event notifications.


    **Important Information:**

    - State codes must be 2 digits

    - Country codes must be 2 digits

    - Validate the shipping address structure

    - Make sure the zip code or locality are correct


    **Custom Keys:** Custom Keys are used when you have a direct account with a carrier. This way you create labels with your rates with an additional small fee for service.'
  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://api-test.envia.com
  description: Sandbox/Test
- url: https://api.envia.com
  description: Production
security:
- bearerAuth: []
tags:
- name: Manifest
paths:
  /ship/manifest:
    post:
      tags:
      - Manifest
      summary: Create a Shipping Manifest
      description: 'Group multiple shipment tracking numbers into a single manifest document that the carrier driver uses to verify packages at pickup.


        **When to use:** Call this endpoint at the end of your shipping batch — typically before a scheduled pickup — to consolidate all outgoing shipments into one manifest for the carrier.


        **Prerequisites:**

        - Valid JWT authentication token (Bearer)

        - One or more valid tracking numbers from previously generated labels


        **Key behaviors:**

        - Returns a manifest ID and a downloadable manifest document URL

        - The manifest lists all included tracking numbers for carrier verification

        - Some carriers require a manifest (also called "close-out" or "end-of-day") before pickup

        - Each tracking number can only belong to one manifest'
      operationId: create-shipping-manifest
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - trackingNumbers
              properties:
                trackingNumbers:
                  type: array
                  description: Array of tracking numbers to include in the manifest. These are the shipment identifiers that will be grouped together for warehouse pickup and handoff to the carrier.
                  items:
                    type: string
                  example:
                  - '7520610403'
                  - '7520610404'
            example:
              trackingNumbers:
              - '794929929630'
              - '794929929743'
              - '794929929856'
      responses:
        '200':
          description: Manifest created successfully. Returns the manifest ID, creation timestamp, list of included tracking numbers, and a download URL for the manifest document.
          content:
            application/json:
              schema:
                type: object
                properties:
                  meta:
                    type: string
                    default: manifest
                  data:
                    type: object
                    properties:
                      manifestId:
                        type: string
                        description: Manifest ID
                      manifestUrl:
                        type: string
                        description: URL to download the manifest
                      trackingNumbers:
                        type: array
                        description: List of tracking numbers included in the manifest
                        items:
                          type: string
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/cancel-shipment.md
  - https://docs.envia.com/reference/classify-hs-code.md
  - https://docs.envia.com/reference/create-commercial-invoice.md
  - https://docs.envia.com/reference/create-shipping-label.md
  - https://docs.envia.com/reference/create-shipping-manifest.md
  - https://docs.envia.com/reference/locatecolombiacity.md
  - https://docs.envia.com/reference/schedule-pickup.md
  - https://docs.envia.com/reference/shipping-rates.md
  - https://docs.envia.com/reference/test-webhook-endpoint.md
  - https://docs.envia.com/reference/track-shipments.md
  - https://docs.envia.com/reference/upload-customs-documents.md
  merge:
    pages: 11
    deduped: 10
    conflicts_kept_first: 0