# Conversion minter API

Source: https://docs.settlemint.com/docs/api-reference/token-features/conversion-minter
How to grant mint authority and configure the conversion-minter feature on the target asset so it mints to holders when the paired source asset burns their position.



The `conversion-minter` token feature attaches to the target asset of a conversion pair. It mints to the target holder when the paired [`conversion`](/docs/api-reference/token-features/conversion) feature on the source asset burns the holder's source position.

For the operator how-to, see [Conversion minter how-to](/docs/operators/token-features/conversion-minter). For the architecture model, see [Conversion architecture](/docs/architects/components/token-features/conversion).

## Configuration [#configuration]

No `featureConfigs` entry required. The feature is self-contained. The Asset Designer attaches it during target-asset creation when a paired conversion source asset is also being created or already exists.

## Authorisation [#authorisation]

The conversion-minter requires the source-asset conversion contract to hold mint authorization. The Asset Designer wires this during deployment when both assets sit under the same operating organisation. For cross-organisation conversions, the target asset's operator must explicitly grant the minter role to the source-side conversion contract:

```
POST /api/v2/token/{targetAddress}/roles/conversion-minter
{
  "grantee": "0x..."
}
```

`grantee` is the address of the source-side conversion contract.

## Behaviour [#behaviour]

The conversion-minter does not run standalone. It only mints in response to the paired conversion contract's burn-and-request flow. Routine conversions require no separate operator step.

## Related [#related]

* [conversion](/docs/api-reference/token-features/conversion): required companion feature on the source asset.
* [Feature constraints](/docs/architects/components/token-features/feature-constraints#dependency-rules)