This document provides an overview of Town’s Partner API, webhooks, and dashboard used by our partners to refer their customers to us and track the state of these referrals through the tax prep and filing process.

Town API & Key Concepts

Our API docs are available at https://api.town.com.

Key concepts of the Town product and API:

• An entity is a tax filing entity, such as a corporation, an LLC, a sole proprietorship, etc. An example entity would be a company on the partner’s platform named “Stark Industries, Inc.”
• A client is a person (or group of people) that is responsible for taxes for that entity, such as an owner or an officer or an authorized representative. An example client would be a user on the partner’s platform named “Tony Stark.”
• A client may be responsible for multiple entities. For example, “Tony Stark” may be responsible for “Stark Industries, Inc.” as well as “Iron Man, LLC.”
• An entity may have multiple clients associated with it. For example, “Stark Industries, Inc.” may also be managed by clients “Pepper Potts” and “Happy Hogan.”

For simplicity, we start with a 1:1 mapping between entities and clients for partner referrals, but the partner can use the API to add other relationships if necessary.

Refer a customer to Town

There are a few ways the partner can refer a customer (i.e., a client and their entity) to Town, in order from the easiest (and simplest) to most customizable and seamless:

• Option 1: Partner-specific URLs the partner can expose to their customers to sign up for Town
• Option 2: Entity/client-specific URLs (and embeddable UI components) with prefilled entity and client information, increasing conversion of the Town sign up process

More on each of these two options below.

Option 1: Partner-specific URL

Flow overview

When a partner starts working with Town, they will be provided with a partner specific URL in the format of: