Card blockers

A block on a card: the card cannot move on because of another card or because of a stated reason. Use it for a card waiting on a card (blocker_card_ref), or for a block that only has a reason; a block with neither is invalid. Give only blocks that are active now; the import creates every block as active.
A record of this entity needs records of other entities in the package: Cards.
Files in the package
List every file of this entity in resource_files of the manifest, with "resource": "card_blockers". An entity can have any number of files. See Bundle format.
[
  {
    "resource": "card_blockers",
    "path": "resources/card_blockers.json"
  }
]
Fields
FieldTypeRequiredDescription
external_idstring (ExternalId)YesYour own identifier of the record, for example k-mrr, unique within the resource across all of its files and case sensitive. Other records refer to this one by it.

Constraints: 1–512 characters.

card_refRef<cards>

refers to Cards

YesThe card that is blocked. Give the external_id of a cards record.
created_atTimestampYesWhen the block was set, for example 2026-03-09T10:05:00Z.

Constraints: RFC 3339 with a time zone.

blocker_card_refRef<cards>

refers to Cards

When reason is absent or nullThe card that causes the block. Leave it out for a block that only has a reason.

Rule: Differs from card_ref.

reasonstring?When blocker_card_ref is absentWhy the card is blocked, for example The cohorts must be defined first. Required when there is no blocker_card_ref.
due_dateDateValue?NoThe date by which the block should be gone. A date without time stays a date.

Constraints: a date without time stays a date; it is never turned into midnight.

References

Refers to

Show on the entity map
Example
A record of this entity:
{
  "external_id": "bl-ltv-cohorts",
  "card_ref": "k-ltv",
  "blocker_card_ref": "k-cohorts",
  "reason": "The cohorts must be defined first.",
  "created_at": "2026-03-09T10:05:00Z",
  "due_date": {
    "precision": "date",
    "value": "2026-03-20"
  }
}
Rules
  • a block without blocker_card_ref has a non-empty reason.
  • The combination of card_ref, blocker_card_ref must be unique.
  • card_ref and blocker_card_ref must differ.
Related entities
Cards, Users
Check after the import
After the import, the records of this entity can be checked on Card blockers › Retrieve card blockers list.
JSON Schema
card_blockers.json
logo
Kaiten
If you have any questions or need help with integration feel free to write us at support@kaiten.ru