# Object API Names

{% hint style="success" %}
**Audience:** Developers and Solution Architects

**Purpose:** Explains how API names and object identifiers are used in <code class="expression">space.vars.Kizen\_company\_name</code> to reference <code class="expression">space.vars.object</code>, fields, <code class="expression">space.vars.activities</code>, and <code class="expression">space.vars.automations</code> when interacting with the API.
{% endhint %}

## Overview

Each <code class="expression">space.vars.object</code> has an API name that is unique to the business. The API name is automatically derived from the <code class="expression">space.vars.object</code> name, and is displayed in the <code class="expression">space.vars.object</code> settings wizard as a read-only field.

### Object Identifier <a href="#object-identifier" id="object-identifier"></a>

The <code class="expression">space.vars.object</code> identifier is the primary way to interact with the API. The <code class="expression">space.vars.object</code> identifier can be either the  [Object’s API name](/docs/concepts/objects/object-apis/object-api-names.md), or the Object ID.

The API name of an <code class="expression">space.vars.object</code> is easily accessible in the UI when editing an <code class="expression">space.vars.object</code>. Look for the read-only field **Object API Name**. This value can be used as the object identifier when using the API.

<div data-with-frame="true"><figure><img src="/files/v3zUpSTOfHESblCzO7O1" alt=""><figcaption></figcaption></figure></div>

### Additional API Names <a href="#additional-api-names" id="additional-api-names"></a>

In addition to <code class="expression">space.vars.objects</code>, other types of data have API names associated with them as well:

* Activities
* <code class="expression">space.vars.object</code> Fields
* Activity Fields
* <code class="expression">space.vars.automations</code>

***

## What's Next

Now that you understand how API names and object identifiers are used to reference <code class="expression">space.vars.objects</code> and other entities in the <code class="expression">space.vars.Kizen\_company\_name</code> API, the next step is learning how those identifiers are used to work with actual data.

In the next section, [Records](/docs/concepts/objects/records.md), you’ll learn how <code class="expression">space.vars.entities</code> represent instances of <code class="expression">space.vars.objects</code>, how data is stored in <code class="expression">space.vars.Kizen\_company\_name</code>, and where to find guidance on creating, retrieving, and searching <code class="expression">space.vars.entities</code> using the API.

<details>

<summary>Related Topics</summary>

* [Object Core Concepts](/docs/concepts/objects/object-core-concepts.md)
* [Object Data Model](/docs/concepts/objects/object-data-model.md)
* [Object Relationships](/docs/concepts/objects/object-configuration/object-relationships.md)
* [Object Layout Customization](/docs/concepts/objects/object-configuration/object-layout-customization.md)
* [Object Permissions](/docs/concepts/objects/object-configuration/object-permissions.md)

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.kizen.com/docs/concepts/objects/object-apis/object-api-names.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.