---
title: "Ice identity"
description: "Learn how Ice identities are mapped to paths in IceRPC."
url: https://docs.icerpc.dev/icerpc-for-ice-users/rpc-core/ice-identity
docs_index: https://docs.icerpc.dev/llms.txt
---

> For an index of every page, see [llms.txt](https://docs.icerpc.dev/llms.txt).

# Ice identity

Learn how Ice identities are mapped to paths in IceRPC.

In Ice, each Ice object has an identity represented by an Ice struct:

```ice
struct Identity
{
    string name;
    string category = "";
}
```

In IceRPC, Ice objects are called services, and each service has a URI-compatible absolute path. For interop with Ice, the identities of Ice objects can be converted back and forth into URI-compatible percent-escaped paths.

For simple identities with only ASCII letters and numbers, the conversion is straightforward:

- path `/category/name` is equivalent to Identity { name = "name", category = "category" }
- path `/name` is equivalent to Identity { name = "name", category = "" }
- path `/` is equivalent to the "null" Identity (with an empty name and empty category)

More generally, an identity is equivalent to a 1 or 2-segment absolute path, where each segment is [percent-escaped](https://en.wikipedia.org/wiki/Percent-encoding):

- path `/percent-escaped-category/percent-escaped-name` is equivalent to Identity { name = "unescaped-name", category = "unescaped-category" }
- path `/percent-escaped-name` is equivalent to Identity { name = "unescaped-name", category = "" }

Here are a few examples:

| Ice identity | Corresponding path |
| --- | --- |
| name = "hello" | `/hello` |
| name = "hello", category = "Xyz" | `/Xyz/hello` |
| name = "hello " | `/hello%20` |
| name = "hello", category = "Xyz/" | `/Xyz%2F/hello` |
