# Virtual relationships

The current Core API integration enables you create rules' conditions based on some information contained in the currently issued JWT token, such as:

<table><thead><tr><th width="274">JWT field</th><th>Description</th></tr></thead><tbody><tr><td><strong><code>jwt_customer</code></strong></td><td>The customer associated to the current JWT.</td></tr><tr><td><strong><code>jwt_user</code></strong></td><td>The user associated to the current JWT.</td></tr><tr><td><strong><code>jwt_markets</code></strong></td><td>The list of markets associated to the current JWT.</td></tr><tr><td><strong><code>jwt_stock_locations</code></strong></td><td>The list of stock locations associated to the current JWT.</td></tr><tr><td><strong><code>jwt_custom_claim</code></strong></td><td>The custom claim attached to the current JWT (if any).</td></tr></tbody></table>

{% hint style="warning" %}
These relationships are **virtual**, meaning that, behind the scenes, the integration calls the related [customer](https://app.gitbook.com/s/RWJeylueWkzLadK710XZ/customers/object), [user](https://app.gitbook.com/s/xrdVVavnnBMHRCqrLp1y/api-reference/user), [custom claim](https://app.gitbook.com/s/-LgByaSP8eKjad-MIuHE/authentication/jwt-bearer#creating-the-jwt-assertion) object or the array of [market](https://app.gitbook.com/s/RWJeylueWkzLadK710XZ/markets/object) or [stock location](https://app.gitbook.com/s/RWJeylueWkzLadK710XZ/stock_locations/object) objects to fetch the data keeping the `jwt_*` prefix in the outcome payload and API interaction.
{% endhint %}

{% hint style="info" %}
At the moment this relationships are available for the [price](https://app.gitbook.com/s/RWJeylueWkzLadK710XZ/prices/object) and [SKU](https://app.gitbook.com/s/RWJeylueWkzLadK710XZ/skus/object) resources only (more to come, keep and eye on the [Core API reference](https://app.gitbook.com/o/-Lfu_B3DKew-kvoEWzTk/s/RWJeylueWkzLadK710XZ/) for any update).
{% endhint %}