---
title: Importer ID and Endpoint Provisioning
slug: public-apis/importer-id-and-endpoint-provisioning
createdAt: 2026-03-09T14:00:17.534Z
---

::::ExpandableHeading
###

**Topic type: Constraint**

:::hint{type="warning"}
**Purpose**: Explain how Importer IDs define integration context and request routing in Accertify APIs.

**Audience**: API integrators and client developers.&#x20;

**Applies to**: Accertify APIs that use Importer ID–based endpoint provisioning.&#x20;

**Does not apply to**: Internal batch processing or non‑request‑based integrations.
:::
::::

All Accertify API requests that use **Importer ID–based endpoints&#x20;**&#x61;re associated with a&#x6E;**&#x20;Importer ID**, which identifies the client integration context under which the request is processed. Importer IDs are a foundational part of request routing, authorization, and configuration.

Importer IDs are **provisioned by Accertify** and must be used exactly as assigned.

- Universal Fraud APIs may use different Importer IDs for preAuth, postAuth, and update workflows depending on client configuration.&#x20;
- Clients cannot create or modify Importer IDs programmatically.

:::ExpandableHeading{isOpen="true"}
## What is an Importer ID

An Importer ID is a unique identifier that represents a specific client integration and processing context within the Accertify platform.

The Importer ID is included as part of the API endpoint and allows the platform to:

- Associate requests with the correct client configuration
- Apply the appropriate industry, configuration, rules, and processing logic
- Route events to the correct internal workflows

Importer IDs are not user‑defined and are not derived from request data.

A single client may be assigned:

- One Importer ID, or
- Multiple Importer IDs, depending on implementation needs
:::

::::ExpandableHeading{isOpen="true"}
## Multiple Importer IDs per Client

It is common for a client to have **multiple Importer IDs**.

:::hint{type="success"}
****<font color="#4f6228">**Examples**</font>:

- Different Importer IDs for preAuth, postAuth, authorizationUpdate, fulfillmentUpdate, or chargebackUpdate workflows.&#x20;
  (See [Transaction Lifecycle Contexts](docId\:wzGRpnj6pDyzrQHyTDnXy))
- Separate Importer IDs for distinct business units or flows
- Separate Importer IDs for testing and production environments
:::

Each Importer ID represents a distinct processing context. Requests sent to the wrong Importer ID may be rejected or processed incorrectly.
::::

