Skip to main content
​
v1.2.1

​
Performance improvements and bug fixes

Validation error messages: improved specificity of validation error messages for date fields. Previously, any invalid date value returned "Invalid ISO 8601 date format." regardless of the actual problem. Now the message distinguishes between malformed strings, out-of-range values, and missing timezone offset.
​
v1.2.0

​
Custom fields returned in ID lookups

When fetching any record by ID (GET /v1/people/:id, GET /v1/companies/:id, GET /v1/deals/:id), the custom_fields array is now returned automatically with the values filled in for that record. Previously, custom field values were only available via a separate endpoint.
{
  "data": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "full_name": "Ana Costa",
    "custom_fields": [
      {
        "id": "assoc-uuid",
        "value": "referral",
        "field": {
          "id": "field-uuid",
          "label": "Lead Source",
          "key": "lead_source",
          "type": "select"
        }
      }
    ]
  }
}
Custom fields with no value for the record appear with "value": null. Fields are returned in the order defined in the workspace settings.

​
Idempotency-Key header now accepted on all POST endpoints

The Idempotency-Key header is now supported on POST /v1/people, POST /v1/companies, and POST /v1/deals.
​
v1.1.0

​
Rate limiting headers

Every response now includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers. When the limit is exceeded, the API returns 429 with a Retry-After header indicating when to retry.