Create a Generic OData base connection using the Flow Service API


The Generic OData connector is in beta. See the Sources overview for more information on using beta-labelled connectors.

A base connection represents the authenticated connection between a source and Adobe Experience Platform.

This tutorial walks you through the steps to create a base connection for Generic OData using the Flow Service API.

Getting started

This guide requires a working understanding of the following components of Adobe Experience Platform:

  • Sources: Experience Platform allows data to be ingested from various sources while providing you with the ability to structure, label, and enhance incoming data using Platform services.
  • Sandboxes: Experience Platform provides virtual sandboxes which partition a single Platform instance into separate virtual environments to help develop and evolve digital experience applications.

The following sections provide additional information that you will need to know in order to successfully connect to Generic OData using the Flow Service API.

Gather required credentials

In order for Flow Service to connect with Generic OData, you must provide values for the following connection properties:

Credential Description
url The root URL of the Generic OData service. The connection specification returns a source’s connector properties, including authentication specifications related to creating the base and source connections. The connection specification ID for Generic Generic OData is: 8e6b41a8-d998-4545-ad7d-c6a9fff406c3.

For more information about getting started refer to this Generic OData document.

Using Platform APIs

For information on how to successfully make calls to Platform APIs, see the guide on getting started with Platform APIs.

Create a base connection

A base connection retains information between your source and Platform, including your source’s authentication credentials, the current state of the connection, and your unique base connection ID. The base connection ID allows you to explore and navigate files from within your source and identify the specific items that you want to ingest, including information regarding their data types and formats.

To create a base connection ID, make a POST request to the /connections endpoint while providing your Generic OData authentication credentials as part of the request parameters.

API format

POST /connections


The following request creates a base connection for Generic OData:

curl -X POST \
    '' \
    -H 'Authorization: Bearer {ACCESS_TOKEN}' \
    -H 'x-api-key: {API_KEY}' \
    -H 'x-gw-ims-org-id: {IMS_ORG}' \
    -H 'x-sandbox-name: {SANDBOX_NAME}' \
    -H 'Content-Type: application/json' \
    -d '{
        "name": "Protocols",
        "description": "A test connection for a Protocols source",
        "auth": {
            "specName": "Anonymous Authentication",
        "params": {
            "url" :  "{URL}"
        "connectionSpec": {
            "id": "8e6b41a8-d998-4545-ad7d-c6a9fff406c3",
            "version": "1.0"
Property Description
auth.params.url The host of the Generic OData server. The Generic OData connection specification ID: 8e6b41a8-d998-4545-ad7d-c6a9fff406c3.


A successful response returns the newly created connection, including its unique connection identifier (id). This ID is required to explore your data in the next tutorial.

    "id": "a5c6b647-e784-4b58-86b6-47e784ab580b",
    "etag": "\"7b01056a-0000-0200-0000-5e8a4f5b0000\""

Next steps

By following this tutorial, you have created an OData connection using the Flow Service API and have obtained the connection’s unique ID value. You can use this ID in the next tutorial as you learn how to explore protocols applications using the Flow Service API.

On this page