> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: About FQDNs

## Article: About FQDNs

## Article Link: https://dev.wix.com/docs/api-reference/articles/work-with-wix-apis/platform/about-fqdns.md

## Article Content:

# About FQDNs

A Fully Qualified Domain Name (FQDN) is a unique identifier for each Wix service object. Think of it as the "address" that tells Wix exactly which service object you want to work with.

> **Note:** Some legacy service objects and their events don't have FQDNs. For more information, see [legacy webhooks](http://dev.wix.com/docs/api-reference/articles/work-with-wix-apis/platform/about-the-structure-of-webhooks).

## FQDN structure

FQDNs follow this structure:
`wix.<domain>.<product>.<version>.<service_object>`

The `<product>` segment is included only when the service object belongs to a sub-product within a domain. For example, `wix.ecom.v1.order` has no `<product>` segment, while `wix.stores.catalog.v1.product` includes `catalog` as the `<product>`.

## Wildcards

When working with data extension schemas or other APIs that accept FQDNs, you can use wildcards (`*`) instead of specific version numbers to prevent issues when service objects are updated to newer versions. For example: `wix.<domain>.<product>.*.<service_object>`

This ensures your code continues to work when Wix updates the service object to a newer version (for example, `wix.ecom.v2.order`), without requiring you to update your implementation.

**Examples:**
- `wix.ecom.*.order` - [Wix eCommerce Order](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/orders/orders/order-object.md) service object (any version)
- `wix.ecom.v1.checkout` - [Wix eCommerce Checkout](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/purchase-flow/checkout/checkout/checkout-object.md) service object  
- `wix.ecom.v1.cart` - [Wix eCommerce Cart](https://dev.wix.com/docs/api-reference/business-solutions/e-commerce/purchase-flow/cart/cart-object.md) service object
- `wix.multilingual.machine.*.translatable_content` - [Wix Multilingual Machine Translation](https://dev.wix.com/docs/api-reference/business-management/multilingual/machine-translation/machine-translation/translatable-content-object.md) service object (any version)

## When to use FQDNs

You'll need FQDNs when:

- **Working with data extension schemas** to specify which service object you want to extend with [site-specific custom fields](https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/extend-an-existing-object-with-a-site-specific-field.md). See [Data Extension Schema API](https://dev.wix.com/docs/api-reference/business-management/data-extension-schema/introduction.md).
- **Using schema plugins** to define which service objects your plugin extends. See [About Schema Plugin Extensions](https://dev.wix.com/docs/build-apps/develop-your-app/extensions/backend-extensions/schema-plugins/about-schema-plugin-extensions.md).
- **Calling certain APIs** to identify the specific service object type. For example, [List Data Extension Schemas](https://dev.wix.com/docs/api-reference/business-management/data-extension-schema/list-data-extension-schemas.md) requires an FQDN parameter.
- **Processing events** to understand which service object triggered the event. See [Webhooks](https://dev.wix.com/docs/build-apps/develop-your-app/api-integrations/events-and-webhooks/about-webhooks.md).

## Finding FQDNs

FQDNs are available in event payloads. Events that return FQDNs will have the `entityFqdn` field documented in their event reference, and the FQDN is returned as `entityFqdn` in the event data.

```json
{
  "eventType": "order.created",
  "entityFqdn": "wix.ecom.v1.order",
  "data": { ... }
}
```