Textmine for Informatica

Connect Informatica Intelligent Data Management Cloud (IDMC) to Textmine for
document ingestion, processing orchestration, extracted metadata, reports, and
validated business records.

The download URL returns the raw OpenAPI 3.0 JSON definition without
authentication or redirects, so you can also paste the URL directly into
Informatica:

https://public-api.textmine.com/openapi/informatica/application-integration.json

Where the connector runs

The connector is created and used inside your Informatica IDMC organization.
Informatica sends HTTPS requests directly to the Textmine Public API; there is
no additional Textmine connector gateway.

Use the Informatica Cloud Server for the shared Textmine Public API. If you
select a customer-managed Secure Agent, it must have outbound DNS resolution
and HTTPS access to the configured Textmine endpoint. Configure its proxy where
required and allowlist the endpoint in applicable firewall and egress controls.
Use a Secure Agent when you need private routing, controlled egress, or access
to a dedicated Textmine deployment.

Before you begin

You need:

• access to Informatica Application Integration;
• a Textmine organization and environment;
• a dedicated Textmine service-account API key; and
• access to the Textmine Vaults and document types used by the integration.

Store the API key in the Informatica connection or its supported external
secret vault. Do not put a real key in the imported OpenAPI file or an exported
Informatica asset.

Create the Application Integration connector

1. In IDMC, open Application Integration.
2. Create a service connector and choose the option to import an OpenAPI
   definition.
3. Enter the canonical definition URL shown above, or upload the downloaded
   JSON file.
4. Select the operations required by your process, then publish the service
   connector.
5. Create an App Connection from the published service connector.
6. Configure API-key authentication:

Header: X-TextMine-Api-Key
Value: tm_<key>

7. Choose Cloud Server for the shared Textmine Public API, or select a
   customer-managed Secure Agent that meets the DNS, HTTPS, proxy, and firewall
   requirements above.
8. Test checkTextmineConnection, then run listVaults to confirm the
   service account can access the expected Vaults.

Recommended document flow

1. Call listVaults and listDocumentTypes.
2. Call uploadDocument or importDocumentFromProvider.
3. Store every returned document ID.
4. Poll getDocument with bounded backoff until processing reaches a terminal
   status.
5. Call listDocumentMetadata and listDocumentTags.
6. Route the structured results to the downstream Informatica process or
   mapping.

If an upload times out, use the source filename and target Vault to perform a
best-effort search or listing before retrying. This lookup can miss a
just-accepted upload or race with concurrent retries, so it is not an
idempotency guarantee. Only treat uploads as idempotent when the API provides a
request ID or another durable correlation mechanism.

Dedicated Textmine environments

The definition points to https://public-api.textmine.com. For a dedicated
deployment, change the connector binding or connection base URL to the Public
API root supplied by Textmine. Do not append /v3.

For help, contact Textmine Support.