Lists the linked objects for a specific object and the given link type.
Note that this endpoint does not guarantee consistency. Changes to the data could result in missing or repeated objects in the response pages.
For Object Storage V1 backed objects, this endpoint returns a maximum of 10,000 objects. After 10,000 objects have been returned and if more objects
are available, attempting to load another page will result in an ObjectsExceededLimit error being returned. There is no limit on Object Storage V2 backed objects.
Each page may be smaller or larger than the requested page size. However, it is guaranteed that if there are more results available, at least one result will be present in the response.
Note that null value properties will not be returned.
Third-party applications using this endpoint via OAuth2 must request the following operation scope: api:ontologies-read.
stringThe API name of the ontology. To find the API name, use the List ontologies endpoint or check the Ontology Manager.
stringThe API name of the object type. To find the API name, use the List object types endpoint or check the Ontology Manager.
stringThe primary key of the object from which the links originate. To look up the expected primary key for your
object type, use the Get object type endpoint or the Ontology Manager.
stringThe API name of the link that exists between the object and the requested objects. To find the API name for your link type, check the Ontology Manager.
integerThe desired size of the page to be returned. Defaults to 1,000. See page sizes for details.
stringThe page token indicates where to start paging. This should be omitted from the first page's request.
To fetch the next page, clients should take the value from the nextPageToken field of the previous response
and use it to populate the pageToken field of the next request.
list<SelectedPropertyApiName>The properties of the object type that should be included in the response. Omit this parameter to get all the properties.
stringBy default, anytime an object is requested, every property belonging to that object is returned.
The response can be filtered to only include certain properties using the properties query parameter.
Properties to include can be specified in one of two ways.
properties query parameter
properties={property1ApiName},{property2ApiName}properties query parameters.
properties={property1ApiName}&properties={property2ApiName}The primary key of the object will always be returned even if it wasn't specified in the properties values.
Unknown properties specified in the properties list will result in a PropertiesNotFound error.
To find the API name for your property, use the Get object type endpoint or check the Ontology Manager.
stringA command representing the list of properties to order by. Properties should be delimited by commas and
prefixed by p or properties. The format expected format is
orderBy=properties.{property}:{sortDirection},properties.{property}:{sortDirection}...
By default, the ordering for a property is ascending, and this can be explicitly specified by appending
:asc (for ascending) or :desc (for descending).
Example: use orderBy=properties.lastName:asc to order by a single property,
orderBy=properties.lastName,properties.firstName,properties.age:desc to order by multiple properties.
You may also use the shorthand p instead of properties such as orderBy=p.lastName:asc.
stringThe repository associated with a marketplace installation.
stringThe package name of the generated SDK.
booleanA flag to exclude the retrieval of the __rid property.
Setting this to true may improve performance of this endpoint for object types in OSV2.
objectSuccess response.
list<OntologyObjectV2>map<PropertyApiName, PropertyValue>Represents an object in the Ontology.
stringThe name of the property in the API. To find the API name for your property, use the Get object type
endpoint or check the Ontology Manager.
anyRepresents the value of a property in the following format.
| Type | JSON encoding | Example |
|---|---|---|
| Array | array | ["alpha", "bravo", "charlie"] |
| Attachment | JSON encoded AttachmentProperty object | {"rid":"ri.blobster.main.attachment.2f944bae-5851-4204-8615-920c969a9f2e"} |
| Boolean | boolean | true |
| Byte | number | 31 |
| Date | ISO 8601 extended local date string | "2021-05-01" |
| Decimal | string | "2.718281828" |
| Double | number | 3.14159265 |
| Float | number | 3.14159265 |
| GeoPoint | geojson | {"type":"Point","coordinates":[102.0,0.5]} |
| GeoShape | geojson | {"type":"LineString","coordinates":[[102.0,0.0],[103.0,1.0],[104.0,0.0],[105.0,1.0]]} |
| Integer | number | 238940 |
| Long | string | "58319870951433" |
| Short | number | 8739 |
| String | string | "Call me Ishmael" |
| Timestamp | ISO 8601 extended offset date-time string in UTC zone | "2021-01-04T05:00:00Z" |
Note that for backwards compatibility, the Boolean, Byte, Double, Float, Integer, and Short types can also be encoded as JSON strings.
stringThe page token indicates where to start paging. This should be omitted from the first page's request.
To fetch the next page, clients should take the value from the nextPageToken field of the previous response
and use it to populate the pageToken field of the next request.
1
2
3
curl \
-H "Authorization: Bearer $TOKEN" \
"https://$HOSTNAME/api/v2/ontologies/palantir/objects/employee/50030/links/directReport"1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
{
"nextPageToken": "v1.QnVpbGQgdGhlIEZ1dHVyZTogaHR0cHM6Ly93d3cucGFsYW50aXIuY29tL2NhcmVlcnMvP2xldmVyLXNvdXJjZSU1YiU1ZD1BUElEb2NzI29wZW4tcG9zaXRpb25z",
"data": [
{
"__rid": "ri.phonograph2-objects.main.object.74f00352-8f13-4764-89ea-28e13e086136",
"__primaryKey": 80060,
"__apiName": "Employee",
"id": 80060,
"firstName": "Anna",
"lastName": "Smith"
},
{
"__rid": "ri.phonograph2-objects.main.object.74f00352-8f13-4764-89ea-28e13e086136",
"__primaryKey": 51060,
"__apiName": "Employee",
"id": 51060,
"firstName": "James",
"lastName": "Matthews"
}
]
}