[v2.0.0] — Major Release Zip Code API

🚀 Improvements

• Complete backend rewrite of the API engine.
• Optimized processing pipeline for faster response times and improved scalability.
• Enhanced query performance across all endpoints.
• Improved infrastructure to support higher concurrency and larger workloads.
• Internal code refactoring to improve long-term maintainability.
• Standardized all Success and Error responses.

✨ New Features

• Distance Calculation Endpoint 

  /zipc/v2/distancecoord

  A new endpoint has been introduced that allows developers to calculate distances between geographic locations.

  The endpoint supports:

  • Distance between a Zip code and a latitude longitude coordinates.

  This enables common geospatial use cases such as:

  • Proximity analysis
  • Logistics and delivery distance calculations
  • Location-based applications

View Documentation here.

Example Use Cases

• Find the distance between ZIP Code 33101 and my current location
• Calculate the distance between ZIP Code 60601 and a GPS coordinate
• Determine the distance between two geographic coordinates

🚀Standardized Success Response Format

• All successful API responses now follow a consistent response envelope across all endpoints.

  The response structure includes three top-level objects:

  • links – Contains navigational links related to the request.
  • meta – Provides metadata about the response such as record counts.
  • data – Contains the actual response payload.

  The data field is now always returned as an array, even when the response contains a single record.

  The object structure inside the data array varies depending on the endpoint, allowing each endpoint to return its own domain-specific fields while maintaining a consistent outer response structure.

🔧 Compatibility

• v1 remains available for backward compatibility.
• Developers are encouraged to migrate to v2 to benefit from improved performance and new features.

📈 Performance

Internal benchmarks show significantly improved response times due to the optimized backend architecture and streamlined data access layer.

---

Migration Notes

Existing integrations can continue using v1 endpoints without interruption.

For new integrations or performance-critical workloads, we recommend using the v2 endpoints.