> This page is for Documentation, version Integration guides (default).
> For other versions, use one of these documentation indexes:
> - Integration guides (default): https://avalara.ferndocs.com/docs/integration-guides/llms.txt
> - Refactor guides: https://avalara.ferndocs.com/docs/refactor-guides/llms.txt
> - Get certified: https://avalara.ferndocs.com/docs/get-certified/llms.txt
> - Agent to Agent (A2A): https://avalara.ferndocs.com/docs/agent-to-agent-a2a/llms.txt
> - AI use cases: https://avalara.ferndocs.com/docs/ai-use-cases/llms.txt
> - API versioning: https://avalara.ferndocs.com/docs/api-versioning/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://avalara.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://avalara.ferndocs.com/_mcp/server.

# Endpoints and Methods

* [Previous](https://developer.avalara.com/communications/dev-guide_geo_soap/getting-started/account-creation/)
* [Next](https://developer.avalara.com/communications/dev-guide_geo_soap/getting-started/sample-messages/)

### Endpoints

AFC Geo SaaS Pro Soap has two sets of endpoints:

1. Binding set ending in `/2.0` returns exceptions when problems are encountered - we recommend using these endpoints so that you can properly handle any exceptions
2. Binding set *not* ending in `/2.0` returns a NULL when problems are encountered

Binding

URL

Basic HTTP

[https://ezgeoasp.billsoft.com/LocatorService.svc/2.0](https://ezgeoasp.billsoft.com/LocatorService.svc/2.0)

[https://ezgeoasp.billsoft.com/LocatorService.svc](https://ezgeoasp.billsoft.com/LocatorService.svc)

Custom

[https://ezgeoasp.billsoft.com/LocatorService.svc/SSL/2.0](https://ezgeoasp.billsoft.com/LocatorService.svc/SSL/2.0)

[https://ezgeoasp.billsoft.com/LocatorService.svc/SSL](https://ezgeoasp.billsoft.com/LocatorService.svc/SSL)

### Web Service Methods

Method

Description

Request

Response

`GeocodeAddress`

Accepts a single address as input and returns a single address in the street database that best matches the input data

[GeocodeAddress](https://developer.avalara.com/communications/dev-guide_geo_soap/reference/geocode-address/)

[GeocodeAddressResponse](https://developer.avalara.com/communications/dev-guide_geo_soap/reference/geocode-address-response/)

`GeocodeAllMatches`

Accepts a single address as input and returns all addresses in the street database that matches the input data

[GeocodeAllMatches](https://developer.avalara.com/communications/dev-guide_geo_soap/reference/geocode-all-matches/)

[GeocodeAllMatchesResponse](https://developer.avalara.com/communications/dev-guide_geo_soap/reference/geocode-all-matches-response/)

`GeocodeLatLong`

Accepts the latitude and longitude of a location as input and returns jurisdiction information only (not complete addresses)

[GeocodeLatLong](https://developer.avalara.com/communications/dev-guide_geo_soap/reference/geocode-lat-long/)

[GeocodeLatLongResponse](https://developer.avalara.com/communications/dev-guide_geo_soap/reference/geocode-lat-long-response/)

`GetServerTime`

Returns current time on the web server in UTC

[GetServerTime](https://developer.avalara.com/communications/dev-guide_geo_soap/reference/get-server-time/)

[GetServerTimeResponse](https://developer.avalara.com/communications/dev-guide_geo_soap/reference/get-server-time-response/)

* [Previous](https://developer.avalara.com/communications/dev-guide_geo_soap/getting-started/account-creation/)
* [Next](https://developer.avalara.com/communications/dev-guide_geo_soap/getting-started/sample-messages/)

> **Note**
>
> Part of the **Communications Geo SaaS Pro SOAP guide** integration guide. [Open the full "Endpoints and Methods" milestone on Avalara](https://developer.avalara.com/products/communications/integration-guides/dev-guide_geo_soap/getting-started/) to see every page in this section.