Authentication

Envía.com uses Bearer Token authentication to authorize requests (both for Shipping and Queries API). Every request to the API must include the following header:

Authorization: Bearer <API Access Token>

Your API access token uniquely identifies your account and permissions. Without this token, requests to the API will not be authorized.

Step to get your API Keys

The process to obtain your API keys is the same for both production and sandbox environments, but you must log in to the corresponding dashboard.

1. Create Your Account

• Sandbox: Sign up at https://accounts-sandbox.envia.com/signup
• Production: Sign up at https://accounts.envia.com/signup

2. Platform Access

• Navigate to Settings → API.

  

• Click Add to generate a new API key.

  

• Verify API key was created successfully

  

3. Make Your First Shipment (Try It!)

API Reference

• Start simple: Use real-life use case recipes with copy-paste code examples in your preferred language (Curl, Python, PHP, Ruby, Node, Java).
• On every API endpoint page:
  • Select the environment (Sandbox or Production) using the dropdown.
  • Pick the example language you want.
  • The code panel adjusts automatically. Copy the provided samples.
• All requests require your token. Paste it into the "Authorization" field or sample code where directed.

4. Explore, Test & Go Live

• Sandbox preview: Try real requests in the Sandbox and confirm responses match what you expect.
• Production ready: Switch to Production when you're ready to go live (just swap out the endpoint URL and token).
• Recommended workflow:
  • Discover & Validate: Use the Queries API first to validate addresses, get service/carrier options, or check shop/webhook/account resources.
  • Execute Shipping Operations: Use the Shipping API to quote rates, create a shipment, generate a label, schedule pickups, and track packages.
  • Monitor & Improve: Use both APIs to track shipments and analyze delivery logs or events.

💡 Important Notes

• You will have different API keys for sandbox and production environments.
• Make sure you use the correct dashboard and base URL when generating and using your tokens.
• Tokens from one environment will not work in the other.