To create a card, you need to specify which list it belongs to. A card is always created within a list context.When using a Company API Key, the company and team are automatically scoped from the key's binding. You only need to provide the listId.
When you copy a card, you specify a destination list. The original card remains unchanged — a new card is created in the target list with the same properties.
Archiving hides a card from default views without permanently deleting it. Archived cards can be restored at any time. This is useful for completed tasks that you want to keep for reference but remove from the active board.
For integrations that need to operate on multiple cards at once, bulk endpoints allow you to update, archive, copy, or move several cards in a single request.When to use bulk operations:
Migrating cards between teams
Batch archiving completed tasks
Updating multiple cards with the same change
Copying a set of cards to another team
Using bulk endpoints is more efficient than making individual requests and helps you stay within rate limits.
You can fetch a card's full details including its checklists, comments, labels, and members. You can also fetch just the list that contains a specific card, which is useful for understanding a card's position in the workflow.
