Importer ID and Endpoint Provisioning
2 min
\<font color="#78b5c7">\</font> topic type constraint purpose explain how importer ids define integration context and request routing in apis audience api integrators and client developers applies to apis that use importer id–based endpoint provisioning does not apply to internal batch processing or non‑request‑based integrations all api requests that use importer id–based endpoints are associated with an 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 and must be used exactly as assigned clients cannot create or modify importer ids programmatically what is an importer id an importer id is a unique identifier that represents a specific client integration and processing context within the 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 multiple importer ids per client it is common for a client to have multiple importer ids \<font color="#4f6228">examples\</font> different importer ids per transaction or event lifecycle stage (such as pre‑authorization, post‑authorization, or updates 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