POST
/
ingest
/
{namespace}
/
{datasetName}
curl --request POST \
  --url https://api.datalinks.com/api/v1/ingest/{namespace}/{datasetName} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "data": [
    {
      "name": "Braveheart",
      "year": 1995,
      "budget": 72000000,
      "director": "Mel Gibson"
    },
    {
      "name": "Argo",
      "year": 2012,
      "budget": 44500000,
      "director": "Ben Affleck"
    },
    {
      "name": "A Quiet Place",
      "year": 2018,
      "budget": 17000000,
      "director": "John Krasinski"
    },
    {
      "name": "Dances with Wolves",
      "year": 1990,
      "budget": 22000000,
      "director": "Kevin Costner"
    },
    {
      "name": "Unforgiven",
      "year": 1992,
      "budget": 14000000,
      "director": "Clint Eastwood"
    },
    {
      "name": "The Postman",
      "year": 1997,
      "budget": 80000000,
      "director": "Kevin Costner"
    }
  ],
  "link": {
    "ExactMatch": null
  }
}'
This response does not have an example.
Before uploading data to a dataset you first need to create it! Please do so through API, or find your datasets through the UI.

​
Uploading structured data

Data can currently be uploaded by providing a structured JSON file. To upload data, you must have write permissions for the dataset. If it’s a dataset you created, you automatically have these permissions. However, if the dataset belongs to someone else, you’ll need to request write access. While this functionality is supported, there is no user interface available for it at the moment. Until the UI is implemented, you can contact the DataLinks team to enable sharing permissions on the backend.

Authorizations

​
Authorization
string
header
required

Use a Bearer token for authentication. Submit the token using the Authorization header: Authorization: Bearer <token>.

Path Parameters

​
namespace
string
required

Namespace for the dataset.

​
datasetName
string
required

Name of the dataset.

Body

application/json

Response

200

Successful ingestion response.