Skip to content

EasyPost Validations

Menu Location: Settings > System > Easypost Validations

Access Level: Administrator

Last Updated: 2026-03-01

Overview

The EasyPost Validations page provides a complete audit trail of address validation requests processed through the EasyPost API. Track validation attempts, view verification results, and troubleshoot shipping address issues.

Primary Functions:

  • View all address validation API calls
  • Track validation success/failure rates
  • Identify problematic addresses
  • Monitor API usage and costs
  • Troubleshoot address verification issues

Page Layout

Header Section

  • Page title and description
  • Date range filter
  • Search by customer name or address
  • Export to CSV button

Validation Log Table

  • Timestamp of validation
  • Customer name
  • Original address submitted
  • Validated/corrected address
  • Validation result (Success/Failed/Warning)
  • EasyPost response details
  • Cost per validation

Summary Stats

  • Total validations (time period)
  • Success rate percentage
  • Total API costs
  • Most common validation issues

Primary Features

Address Validation Tracking

Every address validation attempt is logged with complete details including original input, EasyPost corrections, and verification status.

Search and Filtering

Filter validation records by date range, customer name, address components, or validation status to quickly find specific entries.

API Cost Monitoring

Track EasyPost API costs per validation and total spending over time to manage integration expenses.

Verification Status Analysis

View success rates, common failure patterns, and identify addresses requiring manual review or customer contact.

Common Use Cases

Use Case 1: Review Failed Validations

Goal: Identify and resolve addresses that failed validation

Steps:

  1. Navigate to EasyPost Validations page
  2. Filter by status: "Failed"
  3. Review failed addresses
  4. Contact customers for address clarification
  5. Update addresses manually if needed

Use Case 2: Monitor API Costs

Goal: Track EasyPost API spending

Steps:

  1. Select date range (e.g., last month)
  2. View total validation count
  3. Check total API costs
  4. Calculate average cost per validation
  5. Export data for accounting records

Use Case 3: Troubleshoot Address Issues

Goal: Investigate why specific addresses fail validation

Steps:

  1. Search for customer name or address
  2. Review validation attempts
  3. Compare original vs. corrected address
  4. Check EasyPost response details
  5. Determine if address needs manual correction

Use Case 4: Verify Validation Patterns

Goal: Identify common address problems

Steps:

  1. Set date range to last 30 days
  2. Review validation results
  3. Note repeated failure patterns
  4. Identify geographic areas with issues
  5. Update address entry guidance for customers

Use Case 5: Audit API Integration

Goal: Ensure EasyPost integration is functioning properly

Steps:

  1. Check recent validations
  2. Verify success rate is acceptable
  3. Review API response codes
  4. Identify any integration errors
  5. Report issues to system administrator

Troubleshooting

No Validation Records Appear

Symptoms:

  • Page shows no validation history
  • Empty table despite address verifications

Check:

  1. Verify date range includes expected period
  2. Check if EasyPost integration is enabled
  3. Confirm address validation feature is active
  4. Remove any search filters
  5. Contact administrator if persistent

High Validation Failure Rate

Symptoms:

  • Many addresses marked as failed
  • Low success rate percentage

Investigation:

  1. Review failed addresses for patterns
  2. Check if customers are entering incomplete data
  3. Verify address format requirements
  4. Consider adding address entry guidance
  5. Contact EasyPost support if systematic issue

Validation Costs Higher Than Expected

Symptoms:

  • API costs exceed budget
  • Unexpectedly high validation counts

Check:

  1. Review validation frequency settings
  2. Verify validations aren't duplicated
  3. Check if validation is triggered appropriately
  4. Review integration configuration
  5. Consider implementing validation rules
  • EasyPost Settings - Configure EasyPost API integration
  • EasyPost Log - View all EasyPost API activity
  • EasyPost Webhooks - Manage EasyPost webhook events
  • Shipping Report - View shipping activity and costs

Best Practices

Monitoring

  1. Review validation logs weekly
  2. Monitor success rates monthly
  3. Track API costs for budgeting
  4. Identify recurring problem patterns
  5. Document validation issues

Address Quality

  1. Follow up on failed validations promptly
  2. Provide clear address entry guidance to customers
  3. Update addresses with EasyPost corrections
  4. Validate addresses at signup when possible
  5. Maintain clean address data

Cost Management

  1. Track API usage trends
  2. Set validation rules to avoid unnecessary calls
  3. Review monthly costs against budget
  4. Optimize validation triggers
  5. Export cost data for accounting

Quick Reference Card

Task Action/Location
View all validations Navigate to EasyPost Validations page
Filter by date Use date range selector
Search address Enter address in search field
View failed only Filter by status: Failed
Export data Click Export CSV button
Check API costs View summary stats section
View validation details Click validation row
Search by customer Enter customer name in search

FAQs

What happens when an address fails validation?

Failed validations are logged but do not prevent order processing. Administrators should review failed validations and follow up with customers to verify addresses manually.

How much does each validation cost?

EasyPost charges per validation attempt. Costs are shown in the validation log and summarized in the stats section. Contact EasyPost for current pricing.

Can I re-validate an address?

Yes, you can trigger re-validation by updating the customer's address in their account, which will create a new validation attempt.

Why are some addresses showing warnings instead of failures?

Warnings indicate EasyPost found the address but identified potential issues (e.g., apartment number missing). These typically don't require action but should be reviewed.

How long are validation records kept?

Validation records are retained indefinitely for audit purposes. You can export historical data as needed.

Can validation be disabled for specific customers?

Validation settings are system-wide. Contact your administrator to discuss custom validation rules if needed.

End of Documentation

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