Me Endpoint

/odata/Me returns the current user’s Person entity as defined in our system.
It is implemented as an OData v4 operation import that returns a single entity from the Persons set (same shape as items in /odata/Persons).

In short: GET your own Person record with optional $select / $expand.

URL

GET /odata/Me

Response

200 OK — Person entity

Returns a single Person (EDM type PROLIN.Web.OData.Model.Person) in OData JSON. Example (truncated):

{
  "@odata.context": "https://myserver:5181/odata/$metadata#Persons/$entity",
  "Uid": 3101032460,
  "FirstName": "System",
  "LastName": "User",
  "Name": "User, System",
  "Jobtitle": "Service Desk System Administrator",
  "Email": "user@example.com",
  "Searchcode": "SYSTEM",
  "Category": { "Text": "Employee", "Value": 3095134634 },
  "Status":   { "Text": "Active",   "Value": 3095134621 },
  "Registration": { "DateCreated": "2001-06-29T12:00:00Z", "DateModified": "2025-08-26T10:17:21Z" }
}

204 No Content — No Person for this account

When the authenticated account has no Person entity, the endpoint returns 204 with an empty body (function returns null).

Query options

This endpoint supports the following OData query options:

$select — return only specific properties
Example: /odata/Me?$select=Uid,Name
$expand — inline navigation properties
Example: /odata/Me?$expand=Account($select=Name)

Options like $filter, $orderby, $top, $skip are not applicable to a single-entity result and are ignored.

Notes on `$select/$expand`

$select controls which properties are serialized. Unselected properties are omitted from the response.
$expand supports nested $select, e.g. /odata/Me?$expand=Account($select=Name).
Only navigation properties, such as Account, can be expanded. Code properties such as Status and Category are complex values, not navigation properties: they are always returned in full, and $expand=Status answers 400 Bad Request (Property 'Status' on type 'PROLIN.Web.OData.Model.Person' is not a navigation property or complex property. Only navigation properties can be expanded.). Use $select=Uid,Name,Status to limit the response to them.

Common properties on `Person`

Property	Type	Notes
`Uid`	`int64`	Primary identifier
`FirstName` / `LastName` / `Name`	`string`	Display name is `Name`
`Jobtitle`	`string`
`Email` / `EmailLowerCase`	`string`
`Searchcode`	`string`
`Blocked`	`bool?`
`Birthdate`	`DateTimeOffset?`
`Category`	`Code`	Has `Text`, `Value`
`Status`	`Code`	Has `Text`, `Value`
`Folder`	`Code`
`Registration`	`Registration`	`DateCreated`, `DateModified`
`Account`	`Account`	Expand with `$expand=Account`

Property names/casing must match the EDM (metadata). Use $metadata to discover the full schema.

Examples

Get your Person with just two fields

curl -H "Authorization: Bearer <token>" \
  "https://myserver:5181/odata/Me?$select=Uid,Name"

Inline related data

curl -H "Authorization: Bearer <token>" \
  "https://myserver:5181/odata/Me?$select=Uid,Name,Status&$expand=Account($select=Name)"

URL