Skip to main content

Secoda API (ELT Feeds)

Secoda is an AI platform for data and analytics that helps teams manage trusted metadata, lineage, documentation, governance, and workspace activity. The Secoda API (ELT Feeds) connector is a source-only ELT connector that ingests the whole Secoda catalog as a set of feeds. Select from 29 workspace objects — including catalog resources, integrations, databases, schemas, tables, columns, dashboards, charts, lineage, tags, users, teams, groups, collections, questions, replies, documents, queries, monitors, incidents, measurements, events, custom properties, audit logs, and AI usage data — and Nexla full-refreshes each selected feed on a schedule.

Secoda API (ELT Feeds) icon

Power end-to-end data operations for your Secoda API (ELT Feeds) API with Nexla. Our bi-directional Secoda API (ELT Feeds) connector is purpose-built for Secoda API (ELT Feeds), making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Secoda API (ELT Feeds) or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Secoda API (ELT Feeds) workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

Before creating a Secoda API credential in Nexla, generate an API key in the Secoda workspace that has access to the objects you plan to ingest. Secoda's API documentation states that API requests require an Authorization header with a bearer token, and that API keys are generated from workspace settings.

To obtain a Secoda API key:

  1. Sign in to your Secoda workspace with a user account that has access to the API settings.

  2. Navigate to Workspace settings.

  3. Open the API page to view existing API keys.

  4. Click Generate New API Key.

  5. Copy the generated key immediately and store it securely. Secoda notes that the key has the same access to the workspace as the user who created it.

  6. Confirm the workspace region so API requests use the correct base URL. Secoda documents api.secoda.co for US workspaces, eapi.secoda.co for EU workspaces, and aapi.secoda.co for APAC workspaces. Managed or on-premise workspaces use the custom workspace domain followed by the API version path.

Treat the Secoda API key as a sensitive secret. Rotate the key if it is exposed, and generate keys from an account with the minimum workspace access needed for the feeds you plan to ingest.

For more information, see the Secoda API authentication guide and Secoda API getting started guide.

Authenticate​

Create a credential in Nexla​

  1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Resource descriptions are recommended but are not required. Use them to identify the Secoda workspace, region, or access level represented by this credential.

  3. Enter the Secoda API key in the API Key field.

  4. Enter the Secoda API base URL for the workspace. The default value is https://api.secoda.co for US workspaces. Use https://eapi.secoda.co for EU workspaces, https://aapi.secoda.co for APAC workspaces, or the custom managed workspace domain for managed or on-premise deployments. Nexla sends the key to Secoda as a bearer token in the Authorization header when ingesting feeds.

  5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation and can be selected for use with Secoda API (ELT Feeds) flows.

Use as a data source​

How This Connector Works​

The Secoda API (ELT Feeds) connector is a source-only, whole-catalog ELT connector. Rather than configuring one endpoint at a time, you select the Secoda objects you want from a single catalog of feeds, and Nexla ingests each selected object as its own feed.

  • Discovery: When you create the source, Nexla discovers the objects (feeds) available from your Secoda workspace and presents them for selection.

  • Full refresh: Each selected feed is ingested using a full-refresh strategy, so every run reads the complete current set of records for that object. The id field is used as the primary key to uniquely identify records within each feed.

  • Parallel ingestion: Selected feeds are ingested in parallel, so a single source can pull many Secoda objects on the same schedule.

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, click the New Data Flow button, select the ELT flow type, and click Create.

  2. Select the Secoda API (ELT Feeds) connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Secoda workspace and click Next; or, create a new Secoda API credential for use in this flow. The credential controls the Secoda API base URL, so use the credential that matches the workspace region or managed domain.

Select the Objects to Ingest​

After authenticating, Nexla lists the Secoda objects available from the connector. Select one or more of the following 29 objects to ingest. Each selected object becomes its own feed and is full-refreshed on the configured schedule.

  • List Resources — All catalog resources.
  • List Integrations — Integrations active in the workspace.
  • List Databases — Database assets.
  • List Schemas — Schema assets.
  • List Tables — Table assets.
  • List Columns — Column assets.
  • List Dashboards — Dashboard assets.
  • List Charts — Chart assets.
  • List Lineage — Manual lineage objects.
  • List Tags — Workspace tags.
  • List Users — Workspace users.
  • List Teams — Workspace teams.
  • List Groups — User groups in the workspace.
  • List Collections — Workspace collections.
  • List Questions — Workspace questions.
  • List Question Replies — Replies to workspace questions.
  • List Documents — Workspace documents.
  • List Queries — Stored queries.
  • List Monitors — Workspace monitors.
  • List Incidents — Workspace incidents.
  • List Measurements — Monitor and incident measurements.
  • List Event Categories — Event categories in the workspace.
  • List Events — Workspace events.
  • List Event Properties — Properties of workspace events.
  • List Custom Properties — Custom properties defined in the workspace.
  • List Audit Logs — Workspace audit logs.
  • List AI Chats — AI chat conversations with analytics data.
  • List Rated AI Chats — AI chat conversations that received user feedback ratings.
  • List AI Prompts by Member — Per-member AI prompt counts.
  • List Teams V2 — Teams in the workspace using the v2 endpoint.

Many Secoda objects return paginated responses with next-page links. Nexla follows the Secoda pagination links automatically while reading each feed, so each full refresh ingests all available pages for the selected objects.

Schedule and Activate​

  • Use the default sync schedule or adjust the schedule in the source settings before activating the flow. On each run, every selected feed is full-refreshed.

Reference​

For object schemas, field definitions, and additional detail on each Secoda endpoint, see the Secoda API reference and Secoda API examples.