Skip to content
getgeolens.com
GeoLens Docs

Create Dataset Relationship

POST
/datasets/{dataset_id}/relationships/
 
curl --request POST \
  --url https://example.com/datasets/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/relationships/ \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "label": "example", "source_column": "example", "target_column": "gid", "target_dataset_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0" }'

Create a new FK relationship. Editor+ required.

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
dataset_id
required
Dataset Id
string format: uuid

Request Body required

Section titled “Request Body required ”
Media type application/json
DatasetRelationshipCreate
object
label
Any of:
string
<= 500 characters
source_column
required
Source Column

Join column in the source dataset

string
<= 63 characters
target_column
Target Column

Join column in the target dataset

string
default: gid <= 63 characters
target_dataset_id
required
Target Dataset Id

UUID of the dataset to link to

string format: uuid

Responses

Section titled “ Responses ”

201

Section titled “201 ”

Successful Response

Media type application/json
DatasetRelationshipResponse
object
id
required
Id
string format: uuid
label
required
Any of:
string
relationship_type
required
Relationship Type
string
source_column
required
Source Column
string
source_dataset_id
required
Source Dataset Id
string format: uuid
target_column
required
Target Column
string
target_dataset_id
required
Target Dataset Id
string format: uuid
target_dataset_title
Any of:
string
Example generated
{
  "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
  "label": "example",
  "relationship_type": "example",
  "source_column": "example",
  "source_dataset_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
  "target_column": "example",
  "target_dataset_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0",
  "target_dataset_title": "example"
}

400

Section titled “400 ”

Bad request — invalid payload

ProblemDetail
object
detail
required
Detail
string
status
required
Status
integer
title
required
Title
string
type
Type
string
default: about:blank
Example 
{
  "type": "about:blank"
}

401

Section titled “401 ”

Unauthorized — missing or invalid credentials

ProblemDetail
object
detail
required
Detail
string
status
required
Status
integer
title
required
Title
string
type
Type
string
default: about:blank
Example 
{
  "type": "about:blank"
}

403

Section titled “403 ”

Forbidden — caller lacks write access

ProblemDetail
object
detail
required
Detail
string
status
required
Status
integer
title
required
Title
string
type
Type
string
default: about:blank
Example 
{
  "type": "about:blank"
}

404

Section titled “404 ”

Not found

ProblemDetail
object
detail
required
Detail
string
status
required
Status
integer
title
required
Title
string
type
Type
string
default: about:blank
Example 
{
  "type": "about:blank"
}

409

Section titled “409 ”

Conflict — resource state prevents the operation

ProblemDetail
object
detail
required
Detail
string
status
required
Status
integer
title
required
Title
string
type
Type
string
default: about:blank
Example 
{
  "type": "about:blank"
}

422

Section titled “422 ”

Validation error

ProblemDetail
object
detail
required
Detail
string
status
required
Status
integer
title
required
Title
string
type
Type
string
default: about:blank
Example 
{
  "type": "about:blank"
}

500

Section titled “500 ”

Internal server error

ProblemDetail
object
detail
required
Detail
string
status
required
Status
integer
title
required
Title
string
type
Type
string
default: about:blank
Example 
{
  "type": "about:blank"
}