Languages
Languages define the available language options for relations, templates, and localization. They can include a flag image.
Use the Datastore_Language endpoint to query languages.
Endpoints
List Languages
GET
/v1/odata/Datastore_LanguageSingle Language
GET
/v1/odata/Datastore_Language({id})Fields
Datastore Fields (inherited)
| Field | Type | Description |
|---|---|---|
Name | String | Display name |
Code | String | Unique code identifier |
LocalizedName | String | Localized display name |
IsDefault | Boolean | Whether this is the default value |
Relationships
| Relationship | Target Entity | Cardinality | Description |
|---|---|---|---|
| Relation | Relation | 1:N | Relation |
| Template | Template | 1:N | Template |
| LicenseContract | LicenseContract | 1:N | LicenseContract |
| Person | Relation_Person | 1:N | Person |
| Flag | File | N:1 | Flag |
Expanding Relationships
GET
/v1/odata/Datastore_Language({id})?$expand=RelationNavigating Relationships
GET
/v1/odata/Datastore_Language({id})/RelationFiltering Examples
GET
/v1/odata/Datastore_Language?$filter=Name eq '{Name}'&$top={top}GET
/v1/odata/Datastore_Language?$filter=contains(Name, '{Name}')&$top={top}GET
/v1/odata/Datastore_Language?$filter=Code eq '{Code}'&$top={top}GET
/v1/odata/Datastore_Language?$filter=IsDefault eq {IsDefault}&$top={top}Custom Query
Build your own OData query against Datastore_Language. Open Run and edit the whole request inline — swap the entity set, change the $filter, or add $expand, $select, $orderby, $top, $skip. Type $ for suggestions; use ↺ Reset to restore this example.
GET
/v1/odata/Datastore_Language?$top=10