.svg?fit=max&auto=format&n=9voKLLkajreclhp4&q=85&s=321632804eda4b3cff044941f9ccadda)
Records
Get a CRM Record
Returns a single record for a custom CRM object by its ID.
Required scope: crm:read or crm:write
GET
/
crm
/
{objectSlug}
/
{recordId}
Get a CRM record
curl --request GET \
--url https://api.zeeg.me/v2/crm/{objectSlug}/{recordId} \
--header 'Authorization: Bearer <token>'{
"success": true,
"status": 200,
"record": {
"id": "c1d2e3f4-a5b6-7890-cdef-123456789012",
"objectSlug": "products",
"attributes": {
"sku": "DRESS-001",
"price": 29,
"inventory_count": 150
},
"createdAt": "2025-06-01T10:00:00+00:00",
"updatedAt": "2025-06-01T12:00:00+00:00"
}
}Returns a single record for a custom CRM object by its UUID.Documentation Index
Fetch the complete documentation index at: https://developer.zeeg.me/llms.txt
Use this file to discover all available pages before exploring further.
Path parameters
Response shape
| Field | Type | Description |
|---|---|---|
id | string (UUID) | Unique identifier for the record. |
objectSlug | string | The object this record belongs to (e.g. products). |
attributes | object | All attribute values for this record, keyed by attribute slug. Attributes that have not been set are returned as null. |
createdAt | string (ISO 8601) | Timestamp when the record was created. |
updatedAt | string (ISO 8601) | Timestamp when the record was last modified. |
Understanding the attributes object
Attribute keys inside attributes match the slugs defined on the object schema. The shape of the object depends entirely on which attributes exist on that CRM object.
For example, a products object with attributes sku, price, and in_stock returns:
{
"record": {
"id": "c1d2e3f4-a5b6-7890-cdef-123456789012",
"objectSlug": "products",
"attributes": {
"sku": "DRESS-001",
"price": 29,
"in_stock": true
},
"createdAt": "2025-06-01T10:00:00+00:00",
"updatedAt": "2025-06-01T10:00:00+00:00"
}
}
GET /v2/crm/objects/{slug}.
404 Not Found
If either the object slug does not exist in your workspace, or the record ID does not belong to that object, the API returns404:
{
"success": false,
"message": "Record not found.",
"status": 404
}
When to use this endpoint
- Detail view — display a single record’s full data after the user clicks a row.
- Verification — confirm a record still exists and fetch its latest values before displaying or editing.
- Webhook handlers — look up a record by the ID received in a webhook payload.
Authorizations
Path Parameters
Slug of the custom CRM object.
UUID of the record.
Response
OK
Example:
true
Example:
200
A record for a custom CRM object.
Hide child attributes
Hide child attributes
Unique identifier for the record.
Example:
"c1d2e3f4-a5b6-7890-cdef-123456789012"
Slug of the CRM object this record belongs to.
Example:
"products"
Key/value pairs for the custom attributes defined on the object. Keys are attribute slugs.
Example:
{
"sku": "DRESS-001",
"price": 29,
"inventory_count": 150
}ISO 8601 timestamp when the record was created.
Example:
"2025-06-01T10:00:00+00:00"
ISO 8601 timestamp when the record was last updated.
Example:
"2025-06-01T12:00:00+00:00"
Last modified on May 7, 2026
⌘I
Get a CRM record
curl --request GET \
--url https://api.zeeg.me/v2/crm/{objectSlug}/{recordId} \
--header 'Authorization: Bearer <token>'{
"success": true,
"status": 200,
"record": {
"id": "c1d2e3f4-a5b6-7890-cdef-123456789012",
"objectSlug": "products",
"attributes": {
"sku": "DRESS-001",
"price": 29,
"inventory_count": 150
},
"createdAt": "2025-06-01T10:00:00+00:00",
"updatedAt": "2025-06-01T12:00:00+00:00"
}
}