> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getnexor.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Create Conversion Event

> Record a conversion event for a lead. Conversions track business outcomes such as reservations (intermediary) or closed sales (final).

The `workflow_id`, `master_workflow_id`, and `currency` are automatically inherited from the conversion type, and `converted_at` defaults to the current time. You only need to provide `conversion_type_id`, `lead_id`, and `amount`. You may optionally provide `converted_at`, `workflow_run_id`, or override `currency`.

Each conversion type can define custom `fields` (see GET /conversion-types). When creating an event, pass the corresponding values in the `metadata` object using the field `key` as the JSON key. For example, if a conversion type has a field with `key: "property_unit"`, include `"property_unit": "Apt 302"` in metadata.



## API Specification

The full API specification for this endpoint is available in the [documentation index](https://docs.getnexor.ai/llms.txt).
