Try our plataform
Parent Collections

In Kondado, Parent Collections are the sources and destinations that can be added by users of our platform.

List Available Sources for Creation

Description

Lists the sources available for creation for the user. This endpoint should not be confused with the endpoint that lists the sources created by the user.

Method

GET

Endpoint

/parent_collections/src

URL Parameters

None

Example Response

{
    "success": true,
    "data": [
        {
            "id": 76,
            "createdAt": "2020-06-30T23:30:56.904Z",
            "updatedAt": "2020-06-30T23:30:56.904Z",
            "parent_collection_name": "Salesforce Marketing Cloud",
            "parent_collection_image": "https://kondado.com.br/assets/images/conectores_salesforcemarketingcloud.png",
            "_links": {
                "src": {
                    "tutorial": "https://kondado.io/wiki/en/a/salesforce-marketing-cloud"
                }
            }
        }
    ]
}

Response Description

id

Record ID

createdAt

Record creation date

updatedAt

Record last update date

parent_collection_name

Source name

parent_collection_image

URL of the source logo image

_links

JSON object containing links related to the record. Since some collections can act as both sources (src) and destinations (dest) at the same time (for example, PostgreSQL), the links are separated in the JSON under the src and dest keys.

The src/dest JSON object will contain the key describing the link and the link itself as its value, for example:

"tutorial": "https://kondado.io/wiki/en/a/salesforce-marketing-cloud"

List Available Destinations for Creation

Description

Lists the destinations available for creation for the user. This endpoint should not be confused with the endpoint that lists the destinations created by the user.

Method

GET

Endpoint

/parent_collections/dest

URL Parameters

None

Example Response

{
    "success": true,
    "data": [
        {
            "id": 20,
            "parent_collection_image": "https://kondado.com.br/assets/images/conectores_bigquery.png",
            "parent_collection_name": "BigQuery",
            "_links": {
                "src": {
                    "tutorial": "https://kondado.io/wiki/en/a/bigquery"
                },
                "dest": {
                    "tutorial": "https://kondado.io/wiki/en/a/dest-bigquery"
                }
            },
            "createdAt": "2019-03-24T21:26:41.134Z",
            "updatedAt": "2019-03-24T21:26:41.134Z"
        }
    ]
}

Response Description

id

Record ID

createdAt

Record creation date

updatedAt

Record last update date

parent_collection_name

Destination name

parent_collection_image

URL of the destination logo image

_links

JSON object containing links related to the record. Since some collections can act as both sources (src) and destinations (dest) at the same time (for example, PostgreSQL), the links are separated in the JSON under the src and dest keys.

The src/dest JSON object will contain the key describing the link and the link itself as its value, for example:

"tutorial": "https://kondado.io/wiki/en/a/salesforce-marketing-cloud"

List available sources and destinations via the Kondado API

Use the Parent Collections endpoints to discover which sources and destinations can be created in your Kondado account.

1
Authenticate with the Kondado API

Ensure you have valid API credentials for your Kondado account. If you haven't set up access yet, you can create a free account to get started.

2
Call the sources endpoint

Make a GET request to /parent_collections/src to retrieve all available sources. This returns source names, logos, and tutorial links—do not confuse it with the endpoint listing sources already created by the user.

3
Call the destinations endpoint

Make a GET request to /parent_collections/dest to retrieve all available destinations. The response includes destination names, images, and related links under _links.

4
Parse dual-role collections

Check the _links object for collections that serve as both source and destination (e.g., PostgreSQL). The src and dest keys contain separate tutorial links for each role.

5
Integrate with your pipeline

Use the retrieved collection IDs and metadata to configure your data integration workflows, connecting your chosen sources to destinations like BI tools or data warehouses.

Frequently asked questions

What is the difference between Parent Collections and the sources/destinations I have already created?▼
Parent Collections are the available sources and destinations that can be added to your account, not the ones already configured. The /parent_collections/src and /parent_collections/dest endpoints list what is available for creation, whereas other endpoints list your existing connections.
Why do some collections have both src and dest keys in the _links object?▼
Some collections, like PostgreSQL, can function as both a source and a destination. The _links object separates related resources under src and dest keys so you can access the appropriate tutorial or documentation for each use case.
Do I need any URL parameters to call the Parent Collections endpoints?▼
No. Both /parent_collections/src and /parent_collections/dest require no URL parameters. You only need to authenticate and make a GET request to retrieve the full list of available collections.
What information does the API return for each Parent Collection?▼
Each item includes an id, createdAt and updatedAt timestamps, parent_collection_name, parent_collection_image (logo URL), and _links with related resources such as tutorials.
How can I use Parent Collections to build a data pipeline?▼
After identifying available sources and destinations via the API, you can plan your pipeline architecture. For implementation guidance, explore Kondado's data integration capabilities or data-to-dashboards solutions to connect your data to visualization tools.
Written by·Published 2026-01-12·Updated 2026-04-25