---
title: "Data Formats & Field Types"
description: "Understanding the formats and types used across AgentSync APIs ensures consistent integrations and reliable data handling."
url: "https://developer.agentsync.io/api-data-formats-and-field-types"
image: "https://developer.agentsync.io/_og/d/c_Ocean.takumi,title_~RGF0YSBGb3JtYXRzICYgRmllbGQgVHlwZXM,description_Understanding+the+formats+and+types+used+across+AgentSync+APIs+ensures+consistent+integrations+and+reliable+data+handling.,props_eyJ0aGVtZSI6eyJtb2RlIjoibGlnaHQiLCJjb2xvcnMiOnsicHJpbWFyeSI6IiMxODdFRkYifX19,p_Ii9hcGktZGF0YS1mb3JtYXRzLWFuZC1maWVsZC10eXBlcyI,s_SMCY4MK4c2H0N25Y.png"
---

# Data Formats & Field Types

Understanding the formats and types used across AgentSync APIs ensures consistent integrations and reliable data handling.

## [Request and Response Formats](#request-and-response-formats)

All **request** bodies must be in JSON format, and the following request header must be included:

-   `Content-Type: application/json`

API **responses** are compressed using gzip and will return one of the following content types:

-   `Content-Type: application/json` — all endpoints (Contracting, Hierarchies, Identity, ProducerSync)

## [v2 Naming Conventions](#v2-naming-conventions)

The v2 surfaces follow consistent conventions:

-   **JSON fields** are `lowerCamelCase` (`assignmentStatusName`)
-   **Query parameters** are `lower_snake_case` (`updated_since`, `page_token`)
-   **Timestamps** end in `At` and are RFC3339 UTC (`updatedAt: "2026-06-01T14:22:00Z"`)
-   **Dates** end in `On` or are named as dates, formatted `yyyy-MM-dd` (`effectiveOn: "2026-01-15"`)
-   **Related resources** are inlined as an `...Id` plus a `...Name` companion — no lookup round trips

## [Common Field Types](#common-field-types)

| Type     | Description           | Example                                |
| :------- | :-------------------- | :------------------------------------- |
| string   | Text data             | "John Doe"                             |
| integer  | Whole numbers         | 123                                    |
| boolean  | true/false values     | true                                   |
| datetime | ISO 8601 timestamp    | "2024-01-15T10:30:00Z"                 |
| uuid     | Unique identifier     | "550e8400-e29b-41d4-a716-446655440000" |
| array    | List of values        | ["value1", "value2"]                   |
| object   | Nested data structure | {"key": "value"}                       |

## [Date Formats](#date-formats)

All dates are in ISO 8601 format with UTC timezone:

```json
{
  "created_at": "2024-01-15T10:30:00Z",
  "updated_at": "2024-01-15T15:45:30Z"
}
```

## [Best Practices](#best-practices)

-   **Validate inputs**: Ensure requests conform to JSON schema expectations.
-   **Handle gzip compression**: Configure clients to automatically decompress responses.
-   **Use UUIDs consistently**: Treat UUIDs as immutable identifiers across systems.
-   **Normalize dates**: Always store and process dates in UTC to avoid timezone drift.