Skip to main content
As you work with the API, the CLI, and the event log, you’ll see IDs such as drusr_01kgst84wc8ak0a5ng6snvtw1n for Ian Sanford’s Directory User and porul_01kgstavz1ckwq4jv3pcef3pwk for a Policy Rule. Each ID starts with a short abbreviation for the kind of record it identifies, so you can tell what a record is at a glance, even in a list that mixes several types. This page explains how those abbreviations are built and lists the abbreviation of every resource.

ID Format

Every resource ID has two parts, joined by an underscore. The first part is the resource’s five-character abbreviation, and the second is a 26-character ULID in lowercase. A ULID is a unique identifier that also encodes when the record was created, which ULIDs on the Event Logs page explains in more detail. We don’t support shorthand IDs for parameters, so a command or API request always needs the full ID. When you only have part of one, you can search with the partial ID in the :list command for that resource and copy the full ID from the results.

Namespace Prefixes

We’ve standardized a five-character abbreviation for each of the resources in each of our namespaces. The first two letters stand for the namespace, and the last three stand for the resource. For example, drusr combines dr for the directory namespace with usr for a user, and porul combines po for the policy namespace with rul for a rule.

Resource Abbreviations

Each resource ID is prefixed with its abbreviation, which makes it easy to recognize what type of record it is.
Every event in your workspace’s event log names the records it’s about by these IDs, and the next page describes how that event log works. Continue reading: Event Logs →