---
title: "Changes to Get a contact"
method: GET
path: "/contacts/{id}"
---

# Changes to Get a contact

`GET /contacts/{id}`

> Every recorded change to this operation, newest first.

## Timeline

Changed in 2 of 7 revisions.

- **2026-09-30** `4dc1e20989c8`: 12 warning
- **2026-09-29** `ef5b22b98333`: 4 breaking, 3 warning, 15 info

## Changes

- **2026-09-30** `4dc1e20989c8`: 12 warning
  - added the new `daily_limit_exceeded` enum value to the `anyOf[#/components/schemas/Error]/code` response property for the response status `403`
  - added the new `daily_limit_exceeded` enum value to the `code` response property for the response status `400`
  - added the new `daily_limit_exceeded` enum value to the `code` response property for the response status `401`
  - added the new `daily_limit_exceeded` enum value to the `code` response property for the response status `404`
  - added the new `monthly_limit_exceeded` enum value to the `anyOf[#/components/schemas/Error]/code` response property for the response status `403`
  - added the new `monthly_limit_exceeded` enum value to the `code` response property for the response status `400`
  - added the new `monthly_limit_exceeded` enum value to the `code` response property for the response status `401`
  - added the new `monthly_limit_exceeded` enum value to the `code` response property for the response status `404`
  - added the new `send_limit_exceeded` enum value to the `anyOf[#/components/schemas/Error]/code` response property for the response status `403`
  - added the new `send_limit_exceeded` enum value to the `code` response property for the response status `400`
  - added the new `send_limit_exceeded` enum value to the `code` response property for the response status `401`
  - added the new `send_limit_exceeded` enum value to the `code` response property for the response status `404`
- **2026-09-29** `ef5b22b98333`: 4 breaking, 3 warning, 15 info
  - added the new path request parameter `id`
  - the response property `contact/properties` became nullable for the status `200`
  - the `contact/email` response's property format changed from `email` to no format for status `200`
  - the `contact/id` response's property type changed from `string` to `integer` for status `200`
  - removed the optional property `contact/created_at` from the response with the `200` status
  - removed the optional property `contact/first_name` from the response with the `200` status
  - removed the optional property `contact/last_name` from the response with the `200` status
  - added the non-success response with the status `400`
  - added the non-success response with the status `401`
  - added the non-success response with the status `403`
  - added the non-success response with the status `404`
  - added the optional property `contact/createdAt` to the response with the `200` status
  - added the optional property `contact/engagementSegment` to the response with the `200` status
  - added the optional property `contact/firstName` to the response with the `200` status
  - added the optional property `contact/lastEngagedAt` to the response with the `200` status
  - added the optional property `contact/lastName` to the response with the `200` status
  - added the optional property `contact/updatedAt` to the response with the `200` status
  - the response property `contact` became required for the status `200`
  - the response property `contact/email` became required for the status `200`
  - the response property `contact/id` became required for the status `200`
  - the response property `contact/unsubscribed` became required for the status `200`
  - added the required property `contact/publicId` to the response with the `200` status

---

[Operation](https://skmtc.dev/poststack/apis/poststack-api/docs/contacts/:id/get.md) - [API](https://skmtc.dev/poststack/apis/poststack-api.md) - [Page](https://skmtc.dev/poststack/apis/poststack-api/changes/contacts/:id/get)