Talend
Talend (now part of Qlik) provides data integration, quality, and API management capabilities through cloud-native APIs for ETL, data pipelines, and application integration. The Qlik Talend Cloud platform exposes REST APIs for orchestrating tasks and plans, executing data integration jobs, managing remote engines, configuring connections, monitoring execution history, and administering identities, workspaces, and environments.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Talend the way a machine reads it — 53 machine-readable artifacts across 18 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Talend scores 48.9/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Talend
Each block below is one kind of artifact we hold for Talend. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Talend Cloud Identities Management API
Manages user, group, and role identity information for Talend Cloud accounts. Supports SCIM v2 for automated provisioning from enterprise identity providers.
Talend Cloud Audit Logs API
Load account audit logs for monitoring activities on Talend Cloud applications, ensuring data security and regulatory compliance.
Talend Cloud Connections API
Administers connections used by datasets and crawlers to retrieve data at scale.
Talend Cloud Execution Logs API
Retrieve logs about task runs for debugging and monitoring data integration pipeline executions.
Talend Artifacts API
The Artifacts API from Talend — 1 operation(s) for artifacts.
Talend Connections API
The Connections API from Talend — 1 operation(s) for connections.
Talend Environments API
The Environments API from Talend — 1 operation(s) for environments.
Talend Plan Executions API
The Plan Executions API from Talend — 4 operation(s) for plan executions.
Talend Plans API
The Plans API from Talend — 2 operation(s) for plans.
Talend Promotion Executions API
The Promotion Executions API from Talend — 1 operation(s) for promotion executions.
Talend Promotions API
The Promotions API from Talend — 1 operation(s) for promotions.
Talend Remote Engine Clusters API
The Remote Engine Clusters API from Talend — 1 operation(s) for remote engine clusters.
Talend Remote Engines API
The Remote Engines API from Talend — 2 operation(s) for remote engines.
Talend Run Profiles API
The Run Profiles API from Talend — 2 operation(s) for run profiles.
Talend Schedules API
The Schedules API from Talend — 1 operation(s) for schedules.
Talend Task Executions API
The Task Executions API from Talend — 3 operation(s) for task executions.
Talend Tasks API
The Tasks API from Talend — 3 operation(s) for tasks.
Talend Workspaces API
The Workspaces API from Talend — 2 operation(s) for workspaces.
Scroll within the panel for all 18 ·
Open Collections 2
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Talend Cloud Orchestration API
OPEN COLLECTIONTalend Cloud Processing API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Talend Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Talend Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Talend Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Talend Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Talend API Rules
SPECTRALTalend API Rules
SPECTRALJSON Schema 21
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Artifact
JSON SCHEMAConnection
JSON SCHEMAConnectionCreate
JSON SCHEMAEnvironment
JSON SCHEMAEnvironmentCreate
JSON SCHEMATask Execution
JSON SCHEMAPlan
JSON SCHEMAPlanCreate
JSON SCHEMAPlanExecution
JSON SCHEMAPlanExecutionRequest
JSON SCHEMARemoteEngine
JSON SCHEMARemoteEngineCreate
JSON SCHEMARunProfileCreate
JSON SCHEMASchedule
JSON SCHEMAScheduleCreate
JSON SCHEMATalend Task
JSON SCHEMATaskCreate
JSON SCHEMATaskExecution
JSON SCHEMATaskExecutionRequest
JSON SCHEMAWorkspace
JSON SCHEMAWorkspaceCreate
JSON SCHEMAScroll within the panel for all 21 ·
JSON Structure 2
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Talend Structure
JSON STRUCTURETalend Task Structure
JSON STRUCTUREExamples 1
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Talend Execute Task Example
EXAMPLESecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Talend — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/talend · machine-readable index on apis.io