LogoLogo
  • LiquidCommerce Documentation
  • πŸ”Authentication API Integration
    • Get Access Token
  • Services
    • πŸ—ΊοΈAddress API
      • Autocomplete
      • Details
    • πŸ‘₯Users API
      • Session
      • Fetch User
      • Delete User
      • Create/Update Address
      • Delete Address
      • Add Payment
      • Update Default Payment
      • Delete Payment
    • πŸ—ƒοΈCatalog API
      • Search
      • Availability
    • πŸ›’Cart API
      • Create/Update Cart
    • πŸ›οΈCheckout API
      • Prepare
      • Complete
    • πŸ“Orders API
      • Authentication
      • Get Order
  • CLOUD SDK
    • Overview
    • Methods & Usage
  • EVENTS & ERRORS
    • Overview
    • Cart Events
    • Checkout Status Codes
  • EVENT BRIDGE (WEBHOOKS)
    • Orders
  • Types
    • Loc
    • Catalog
    • Catalog Filters
    • Product
    • Cart
    • User
    • Retailer
    • Checkout
    • Order
Powered by GitBook
On this page
  • Address API Overview
  • Key Features
  • Authentication
  • Error Handling
  • Rate Limiting
  • Best Practices
  • Google Places API Key
Export as PDF
  1. Services

Address API

The LiquidCommerce Address API provides comprehensive address validation, standardization, and geocoding services optimized for beverage alcohol delivery and shipping

Address API Overview

It leverages Google Places API to offer address autocomplete functionality and retrieve geographical coordinates, enhancing the accuracy of shipping addresses and enabling location-based services.

Key Features

  • Address autocomplete using Google Places API

  • Geocoding to obtain latitude and longitude for addresses

  • Validation of shipping addresses

  • Support for international addresses

Authentication

Before using the API, you need to obtain an access token from the Authentication API. Include this token in the Authorization header of all API requests:

Authorization: Bearer <YOUR_ACCESS_TOKEN>

Error Handling

The API uses standard HTTP response codes to indicate the success or failure of requests. In case of an error, the response body will contain a JSON object with more details about the error.

Rate Limiting

The API is subject to rate limiting to ensure fair usage and maintain performance. If you exceed the rate limit, you'll receive a 429 (Too Many Requests) response.

Best Practices

  1. Use the autocomplete endpoint to provide real-time suggestions as users type their address.

  2. Always use the place ID returned by the autocomplete endpoint to fetch detailed address information.

  3. Store both the formatted address and the geocoding data (latitude and longitude) for each validated address.

  4. Implement proper error handling to manage cases where address validation fails.

Google Places API Key

A Google Places API Key is required to use this service. You need to include this key in your requests to the Address API. For instructions on how to obtain a Google Places API Key, please refer to the Google Maps Platform documentation

PreviousGet Access TokenNextAutocomplete

Last updated 6 months ago

πŸ—ΊοΈ

Support

Our dedicated support team is available to assist you with API integration and usage. For any questions or issues, please contact solutions@liquidapp.co.