Lost Reasons

Entity›Datastore›Datastore.LostReason

Lost reasons track why sales opportunities were lost (e.g., price, competitor, timing).

Use the Datastore_LostReason endpoint to query lost reasons.

Endpoints

List Lost Reasons

GET/v1/odata/Datastore_LostReason

Single Lost Reason

GET/v1/odata/Datastore_LostReason({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
SalesOpportunity	Activity_SalesOpportunity	1:N	SalesOpportunity

Expanding Relationships

GET/v1/odata/Datastore_LostReason({id})?$expand=SalesOpportunity

Navigating Relationships

GET/v1/odata/Datastore_LostReason({id})/SalesOpportunity

Filtering Examples

GET/v1/odata/Datastore_LostReason?$filter=Name eq '{Name}'&$top={top}

GET/v1/odata/Datastore_LostReason?$filter=contains(Name, '{Name}')&$top={top}

GET/v1/odata/Datastore_LostReason?$filter=Code eq '{Code}'&$top={top}

GET/v1/odata/Datastore_LostReason?$filter=IsDefault eq {IsDefault}&$top={top}

Custom Query

Build your own OData query against Datastore_LostReason. 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_LostReason?$top=10