Create a new piece of data

post

https://example.com/resource

Create an invividual resource of a certain type about a certain subject.

It is not possible to choose your own resource identifier (e.g. to express semantics about the resource). After creation, the URI of the resource will be provided in the Location header of the HTTP response. If you want to add your own metadata to express semantics about the resource, you can do so using the Labels header.

It is not possible to use this endppoint to add resources for types or subjects that do not exist yet. If you want to create a new type or subject, you can do so via the authorisation agent.

Query Params

type

string

required

The URL-encoded URI that represents the type of data for which the resource should be created.

subject

string

required

The URL-encoded URI that represents the data subject for whom the resource should be created.

Headers

X-Request-ID

string

If provided, this string will be set as the value of the X-Request-ID response header.

X-Correlation-ID

string

If provided, this string will be set as the value of the X-Correlation-ID response header.

Authorization

string

required

A DPoP bound Solid JWT token containing at least three claims: sub, azp and iss.

DPoP

string

required

The DPoP proof for the Solid JWT token, endpoint and http method.

Purpose

string

A comma separated list of URIs that identify the purposes for which data is being read. For example https://dbpedia.org/marketing/, https://dbpedia.org/direct-mailing/. Depending on the tenant, this field can be required or not.

Legal-Basis

string

A comma separated list of URIs that identify the legal bases for which data is being read. For example https://w3id.org/dpv#PublicInterest. Depending on the tenant, this field can be required or not.

Content-Type

string

required

Mandatory. The IANA media type template. For example application/json.

Labels

string

A comma separated list of labels for this resource. Labels can be used to provide custom metadata to the resource.

Origin

string

If provided, this value will be used in the reponse to enable cross origin resource sharing.

Responses

`purpose_header_required_but_not_present`
`purpose_header_invalid`
`legal_basis_header_required_but_not_present`
`legal_basis_header_invalid`
`labels_header_invalid`
`content_type_unknown`
`content_type_missing`
`x_correlation_id_invalid`
`x_request_id_invalid`
`type_query_parameter_missing`
`type_query_parameter_invalid`
`subject_query_parameter_missing`
`subject_query_parameter_invalid`
`body_missing`
`resource_too_large`

Create a new piece of data

`tenant_not_found`

`origin_server_not_available`
`origin_server_status_code_400`
`origin_server_status_code_401`
`origin_server_status_code_403`
`origin_server_status_code_404`
`origin_server_status_code_4xx`
`origin_server_status_code_500`
`origin_server_status_code_5xx`

`conditional_http_requests_not_yet_supported`
`tenant_operating_mode_is_read_only`
`tenant_operating_mode_not_yet_supported`
`tenant_operating_mode_is_read_only`

201Created

401Unauthorized

403Forbidden

404Not Found Possible errors: tenant_not_found

500Internal Server Error Possible errors: origin_server_not_available origin_server_status_code_400 origin_server_status_code_401 origin_server_status_code_403 origin_server_status_code_404 origin_server_status_code_4xx origin_server_status_code_500 origin_server_status_code_5xx

501Not Implemented Possible errors: conditional_http_requests_not_yet_supported tenant_operating_mode_is_read_only tenant_operating_mode_not_yet_supported tenant_operating_mode_is_read_only

`tenant_not_found`

`origin_server_not_available`
`origin_server_status_code_400`
`origin_server_status_code_401`
`origin_server_status_code_403`
`origin_server_status_code_404`
`origin_server_status_code_4xx`
`origin_server_status_code_500`
`origin_server_status_code_5xx`

`conditional_http_requests_not_yet_supported`
`tenant_operating_mode_is_read_only`
`tenant_operating_mode_not_yet_supported`
`tenant_operating_mode_is_read_only`