---
title: "Glossary: UI and API names"
description: The names the Coevera app shows next to the names the API uses, for the entities and fields whose names differ, and why integrations key on API names.
canonical: https://developers.coevera.com/concepts/glossary/
section: concepts
verification: schema
lastVerified: 2026-10-15
publisher: Coevera
---

# Glossary: UI and API names

**Answer:** The app and the API name several things differently: users are Clients, roles are MasterRights, documents are CloudObjects, messages are Memos, sales units are SalesUnits and product line items are OpptyProductRelations. Admins can rename entities and fields in the app; the API names stay, so integrations key on API names and look labels up when they need them.

These docs give the API name first and the app's name in bold on first use: `owner_id` (shown in
the app as **Owner**). This table is for the other direction: you know a screen in the app and
need the entity behind it.

## Entities

| In the app                            | In the API (REST path, GraphQL repository)                                                                                                                              |
| ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **User**                              | [`Clients`](/reference/rest/clients/), [`client`](/reference/graphql/client/)                                                                                           |
| **Role**                              | [`MasterRights`](/reference/rest/master-rights/), [`masterRight`](/reference/graphql/master-right/)                                                                     |
| **Sales Unit** (**Unit**)             | [`SalesUnits`](/reference/rest/sales-units/), [`salesUnit`](/reference/graphql/sales-unit/)                                                                             |
| **Document**                          | [`CloudObjects`](/reference/rest/cloud-objects/), [`cloudObject`](/reference/graphql/cloud-object/); attached to records through `CloudObjectRelations`                 |
| **Folder** (of documents)             | [`CloudObjectFolders`](/reference/rest/cloud-object-folders/), [`cloudObjectFolder`](/reference/graphql/cloud-object-folder/)                                           |
| **Message**                           | [`Memos`](/reference/rest/memos/), [`memo`](/reference/graphql/memo/); its comments are `MemoComments`                                                                  |
| **Note**                              | [`Notes`](/reference/rest/notes/), [`note`](/reference/graphql/note/)                                                                                                   |
| **Email**                             | [`Emails`](/reference/rest/emails/), [`email`](/reference/graphql/email/)                                                                                               |
| **Text Message**                      | [`TextMessages`](/reference/rest/text-messages/), [`textMessage`](/reference/graphql/text-message/)                                                                     |
| **Product Line Item**                 | [`OpptyProductRelations`](/reference/rest/oppty-product-relations/), [`opptyProductRelation`](/reference/graphql/oppty-product-relation/)                               |
| **Opportunity**                       | [`Opportunities`](/reference/rest/opportunities/), [`opportunity`](/reference/graphql/opportunity/); IDs that may point at a lead or an opportunity are `lead_oppty_id` |
| **Step** (of a pipeline or a process) | [`Steps`](/reference/rest/steps/), [`step`](/reference/graphql/step/)                                                                                                   |
| **Step sales activities**             | [`StepChecklists`](/reference/rest/step-checklists/), [`stepChecklist`](/reference/graphql/step-checklist/)                                                             |
| **Velocity**                          | [`Timeframes`](/reference/rest/timeframes/), [`timeframe`](/reference/graphql/timeframe/)                                                                               |
| **Field Auto Number**                 | [`FieldSequences`](/reference/rest/field-sequences/), [`fieldSequence`](/reference/graphql/field-sequence/)                                                             |
| **Recurrence**                        | `OpptyRecurrences` and `TaskRecurrences`                                                                                                                                |
| Dropdown options                      | [`Data`](/reference/rest/data/), [`data`](/reference/graphql/data/)                                                                                                     |
| **Space**                             | The space ID in every URL, `{space_id}`                                                                                                                                 |

The app files administration of users and roles under **Administration › Units, Users &
Roles**, and API applications under **Units, Users & Roles › Applications**.

## Fields

| In the app           | In the API                                                          |
| -------------------- | ------------------------------------------------------------------- |
| **Owner**            | `owner_id` (the ID), `owner` (the related record)                   |
| **Sales unit**       | `unit_id`, `unit`                                                   |
| **Role** (of a user) | `master_right_id` on `Clients`                                      |
| A user's e-mail      | `email` on `Clients`; records use `email1` to `email5`              |
| A record's phone     | `phone1` to `phone5`                                                |
| Custom fields        | `cf_` plus the field's name at creation, such as `cf_customer_tier` |

## Renamed entities and fields

An admin can rename entities such as Accounts, Contacts, Leads, Opportunities, Projects and Quotes,
and any field, so the labels in one space differ from another's. The API names do not follow:

- `entity_name` on `/entities/Entities` is the stable name (`Account`), and `name_singular` and
  `name_plural` are the labels an admin set, or `null` while the default applies.
- A field keeps its `api_name` when it is renamed. A field that is deleted and created again under
  the same name gets a new one, with a number added (`cf_customer_tier1`).

Key integrations on API names and read labels from those two endpoints when you show them. The
[fields page](/concepts/fields-and-custom-fields/#find-a-fields-api-name) shows how.

## Limits

| Limit      | Details                                                                                                               |
| ---------- | --------------------------------------------------------------------------------------------------------------------- |
| Labels     | Per space: an admin's renames show in the app, never in API names                                                     |
| This table | Covers the names that differ; an entity not listed here has the same name in both, such as **Account** and `Accounts` |