aid: infoworks name: Infoworks description: >- Infoworks is an Enterprise Data Operations and Orchestration (EDO2) platform that automates data onboarding, preparation and operationalization onto Databricks, Snowflake, BigQuery, Synapse and Apache Spark. Unlike a multi-tenant SaaS, Infoworks is deployed into the customer's own cloud account (Kubernetes on AKS/EKS/GKE, or VM-based), so every deployment answers on its own host and the published contract carries a templated server. The product exposes the Infoworks REST API v3 — 369 paths and 510 operations across 62 tag groupings (41 of them declared) covering sources, tables, table groups, topic and file mappings, domains, pipelines, pipeline groups, workflows, workflow versions, jobs, environments, clusters, secrets, service authentication, users, admin operations and metrics — plus a first-party Python SDK on PyPI. Infoworks was acquired by Uniphore in 2024 and is sold as InfoWorks inside the Uniphore Business AI platform; the corporate site now redirects to uniphore.com while the product documentation, support desk and API reference remain on infoworks.io. image: https://uploads.developerhub.io/prod/Bqr9/thfuawsbhl64giqmsect3d7t9soygddj2m5jd6spkfpphxzhyiyr28crjxt3yycf.png url: https://raw.githubusercontent.com/api-evangelist/infoworks/refs/heads/main/apis.yml x-type: company x-source: harvest:secondary-market specificationVersion: '0.20' created: '2026-08-23' modified: '2026-08-23' tags: - Data Engineering - Data Integration - Data Ingestion - Data Pipelines - Workflow Orchestration - Data Warehouse Modernization - Databricks - Snowflake - Big Data - ETL - Enterprise Data Operations - Self-Hosted maintainers: - FN: Kin Lane email: kin@apievangelist.com - FN: APIs.json email: info@apis.io apis: - name: Infoworks REST API v3 description: >- The Infoworks v3 REST API — 369 paths and 510 operations across 62 tag groupings — for onboarding sources, crawling and ingesting tables, building pipelines and pipeline groups, scheduling and running workflows and jobs, and administering environments, clusters, secrets, service authentication, subscribers, job hooks and users. Authentication is a short-lived JWT bearer token minted from either HTTP Basic (username:password) or a long-lived refresh token copied from the Infoworks UI. The server block is templated ({protocol}://{host}:{port}/v3) because Infoworks runs in the customer's own cloud, not on a vendor-operated host. humanURL: https://docs.infoworks.io/infoworks-rest-api-v3/ref baseURL: https://{host}:{port}/v3 x-base-url: >- NO FIXED BASE URL EXISTS, and this is a product fact rather than a gap in our research. Infoworks is licensed software deployed into the customer's own cloud account, so every deployment answers on its own host. The provider's own OpenAPI declares a fully templated server ({protocol}://{host}:{port}/v3 with defaults http/localhost/3001, the in-cluster service address) and the official Python SDK is initialized with protocol/host/port supplied by the operator. repair-api-bases.py returns `no-usable-base` for exactly this reason; nothing is guessed from the domain to fill it. tags: - Data Engineering - Data Integration - Data Ingestion - Workflow Orchestration - Databricks - ETL properties: - type: OpenAPI url: openapi/infoworks-rest-api-v3-openapi.yml - type: Overlay url: overlays/infoworks-rest-api-v3-overlay.yaml - type: Authentication url: authentication/infoworks-authentication.yml - type: ErrorCatalog url: errors/infoworks-problem-types.yml - type: Conventions url: conventions/infoworks-conventions.yml - type: DataModel url: data-model/infoworks-data-model.yml - type: Documentation url: https://docs.infoworks.io/developer-resources/rest-api - type: APIReference url: https://docs.infoworks.io/infoworks-rest-api-v3/ref common: - type: Website url: https://www.uniphore.com/infoworks/ - type: Documentation url: https://docs.infoworks.io/ - type: APIReference url: https://docs.infoworks.io/infoworks-rest-api-v3/ref - type: DeveloperPortal url: https://docs.infoworks.io/developer-resources/rest-api - type: GettingStarted url: https://docs.infoworks.io/getting-started/navigating-infoworks - type: Support url: https://support.infoworks.io/support/home - type: Blog url: https://www.uniphore.com/blog/ - type: GitHubOrganization url: https://github.com/Infoworks - type: TermsOfService url: https://www.uniphore.com/legal/msa/ - type: PrivacyPolicy url: https://www.uniphore.com/legal/privacy-policy/ - type: Compliance url: https://www.uniphore.com/security/ - type: TrustCenter url: security/infoworks-trust-center.yml - type: Packages url: packages/infoworks-packages.yml - type: SDKs url: packages/infoworks-packages.yml - type: ChangeLog url: changelog/infoworks-changelog.yml - type: Lifecycle url: lifecycle/infoworks-lifecycle.yml - type: Conformance url: conformance/infoworks-conformance.yml - type: LLMsTxt url: llms/infoworks-llms.txt - type: AgentSkill url: skills/_index.yml - type: Plans url: plans/infoworks-plans-pricing.yml - type: RateLimits url: rate-limits/infoworks-rate-limits.yml - type: DomainSecurity url: security/infoworks-domain-security.yml - type: Security url: security/infoworks-vulnerability-disclosure.yml - type: VulnerabilityDisclosure url: security/infoworks-vulnerability-disclosure.yml x-enrichment: date: '2026-08-23' status: enriched artifacts_added: 19 pass: local-v1 note: >- Contract discovery beat a JavaScript-rendered docs host. docs.infoworks.io is a DeveloperHub Angular SPA that answers HTTP 200 with an identical 18,776-byte shell for every path — including /openapi.json, /swagger.json and every /.well-known/* path — but its published API reference is backed by a real, downloadable OpenAPI 3.0.1 (369 paths, 510 operations, 62 tag groupings of which 41 are declared), which was retrieved verbatim and saved to openapi/. Verified 200 on https://docs.infoworks.io/infoworks-rest-api-v3/ref, 2026-08-23. No x-coverage block is written because the pass is covered, not thin.