Skip to main content

​
Overview

Part of Zamp’s managed service, Zamp includes a thorough nexus analysis of any customer. Unless a business is brand-new has made no prior transactions, Zamp will perform the nexus analysis to track when they would need to register in different jurisdictions. As a result, your integration platform should handle syncing transactions between user-determined dates.

​
Endpoints Used

​
What Does the Integration Platform Need to Do?

​
Recommended Workflow

1

Customer Determines Date Range

The client should navigate to a Historical Sync page or Bulk Sync page and be prompted to select a date range to sync transactions to Zamp.
2

Post Sync Trigger, Integration Fetches Transactions in Zamp

Keep in mind that the integration will only return transactions that are tied to the API Key you are using. Transactions pushed from other sources will not be returned by GET requests.
  1. Initiate a GET /transactions call to fetch transactions with the given parameters.
    1. Parameters are listed here.
3

Review and Store Returned Transaction IDs and Names

The transaction fetch will return a list of transactions (and any associated tax information), along with ID and name for those transactions.
4

Building Transactions to Push

  1. For the selected date range, you will build transaction objects for any transactions in the date range.
  2. For all transactions, ensure the ID and name do not match any transactions already in Zamp. 
  3. For each transaction, include as much information as possible. At minimum, include:
5

Pushing Transactions

  1. For transactions that do NOT exist in Zamp already, make a POST /transactions call for every transaction from the previous step.
    Zamp will return a 409 for any transaction that already exists in Zamp as a safeguard.
  2. Ensure every unique transaction is accepted with a 200 - Successful.
  3. Return a breakdown to the user of:
    1. Total number of attempted transactions
    2. Number of successful transactions
    3. Number of failed transactions
    4. Number of transactions already listed in Zamp
6

Customer to Review Transactions in Zamp

Once the sync is completed, the user should be prompted to navigate to Zamp for transaction review.