Skip to content

EasyPost Log Documentation

Menu Location: Tools > Integrations > EasyPost Log

Access Level: Manager and above

Last Updated: 2026-03-01

Overview

The EasyPost Log tracks all interactions with the EasyPost shipping API, including label purchases, address verifications, rate requests, and tracking updates. This diagnostic tool helps troubleshoot shipping issues, monitor API usage, and verify successful label generation.

Primary Functions:

  • Monitor shipping label creation success/failure
  • Track address verification attempts and results
  • Review shipping rate calculations
  • Diagnose shipping API errors
  • Monitor API usage for billing purposes
  • Verify tracking number assignment

Page Layout

Header Section

  • Date Range Selector: Filter by log date
  • Request Type Filter: Label Creation, Address Verify, Rates, Tracking, Refunds
  • Status Filter: Success, Failed, Pending
  • Search: Find by order ID, tracking number, or address

Main Content Area

Log table showing EasyPost API requests, responses, status codes, and error messages.

Summary Panel

  • Total API calls in period
  • Success vs failure rate
  • Most common errors
  • Total shipping costs

Report Data & Columns

Column Description
Timestamp When API call was made
Request Type Label, Address Verify, Rate Quote, Tracking Update
Order ID Associated order number
Status Success, Failed, Pending
Response Code HTTP/API status code
Tracking Number Generated tracking number (if applicable)
Carrier USPS, UPS, FedEx, etc.
Cost Shipping cost charged
Error Message Detailed error if failed
Request Details Full API request data
Response Details Full API response data

Common Use Cases

Use Case 1: Troubleshoot Failed Label

Goal: Determine why shipping label didn't generate

Steps:

  1. Filter to failed requests
  2. Search for order ID
  3. Review error message
  4. Common issues:
    • Invalid address format
    • Oversized/overweight package
    • Missing required address fields
    • Carrier service not available for destination
    • Payment method issue
  5. Correct issue and retry label generation

Example: Order #12345 label failed with "Invalid ZIP code format". Customer entered "123456" instead of "12345-6789". Edit customer address, regenerate label successfully.

Use Case 2: Address Verification Issues

Goal: Understand why address verification failed

Steps:

  1. Filter to "Address Verify" requests
  2. Find customer's address
  3. Review verification response
  4. Check for:
    • Suggested corrected address from USPS
    • Invalid apartment/suite number
    • Non-existent street address
    • PO Box not allowed for carrier
  5. Contact customer to verify correct address

Use Case 3: Monitor Daily Shipping Costs

Goal: Track shipping expenses for accounting

Steps:

  1. Set date range to today or yesterday
  2. Filter to successful label purchases
  3. Review total shipping costs
  4. Export for accounting records
  5. Compare to expected costs; investigate anomalies

Use Case 4: Tracking Number Lookup

Goal: Find tracking number for customer inquiry

Steps:

  1. Search for order ID
  2. Locate label creation record
  3. Copy tracking number
  4. Provide to customer
  5. Optionally click tracking link to see current status

Use Case 5: API Performance Monitoring

Goal: Ensure EasyPost integration is healthy

Steps:

  1. Review last 24 hours of requests
  2. Calculate success rate (should be 95%+)
  3. Check for patterns in failures
  4. If low success rate or system-wide errors, contact support
  5. Monitor response times for performance degradation

Troubleshooting

High Volume of Failed Requests

Investigate:

  1. Check if system-wide carrier outage
  2. Review if all failures same error type
  3. Verify EasyPost API credentials still valid
  4. Check if billing/payment issue with EasyPost account
  5. Contact EasyPost support if persistent

Cannot Find Expected Log Entry

Check:

  1. Expand date range
  2. Verify order actually attempted label creation
  3. Check if manual label used instead of API
  4. Some test/preview requests may not log

Error Messages Unclear

Common Errors:

  • "Invalid Address": Address doesn't validate with USPS
  • "Insufficient Funds": EasyPost account needs funding
  • "Rate Not Available": Carrier doesn't service this route/package size
  • "Timeout": API temporarily unreachable, retry usually works

Solution: Document error and contact EasyPost support or system administrator.

  • Orders - Order management and manual label creation
  • Shipping Settings - Configure carriers and shipping rules
  • Customer Address Management - Edit and verify addresses

Permissions & Access

Required Access Level: Manager or higher

Best Practices

Daily Monitoring

  1. Check for failed labels each morning before packing
  2. Resolve address issues before delivery day
  3. Monitor costs to catch configuration errors
  4. Export daily for accounting

Error Response

  1. Don't ignore failed address verifications
  2. Contact customers for address corrections promptly
  3. Document recurring issues for product team
  4. Keep EasyPost account funded to avoid disruptions

Quick Reference Card

Task Action
Find failed labels Status: Failed, Type: Label Creation
Daily cost report Date: Today, Status: Success, export total
Address verification check Type: Address Verify, search customer
Find tracking number Search order ID
Monitor API health Last 24 hours, review success rate

FAQs

Why do some orders not appear in log?

Manual label creation, pickup orders, or orders using different shipping system won't appear in EasyPost log.

Can I regenerate a failed label from this page?

No - view log only. Return to order management page to retry label generation.

How often does tracking update?

Tracking updates pull from EasyPost periodically (varies by system configuration, typically every few hours).

What if EasyPost cost differs from expected?

May indicate package dimensions/weight incorrect, wrong carrier tier selected, or address surcharge applied. Review order shipping settings.

Change Log

2026-03-01

  • Initial documentation created

End of Documentation

For additional help, contact your system administrator or Kiva Logic support.