How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

trello Cards API

Operations for creating, retrieving, updating, and deleting cards, including managing card attachments, checklists, comments, labels, members, and stickers.

trello Cards API is one of 16 APIs that Trello publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Cards. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 16 operations across 11 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against a single base URL, https://api.trello.com/1.

16 operations 11 paths 8 schemas 3 DELETE5 GET7 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://api.trello.com
Authentication
API Key, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

trello Cards API declares 2 security schemes for authenticating requests. An API key is passed in the query as key (apiKey). An API key is passed in the query as token (apiToken). By default, every request must be authenticated.

  • apiKey — Your Trello API key, obtained from the Power-Ups admin page at https://trello.com/power-ups/admin.
  • apiToken — A user token that grants access to Trello resources. Obtained by authorizing via the /1/authorize route or OAuth 1.0.

Paths & Operations 16

Across 11 paths, the API surfaces 16 operations — 3 DELETE, 5 GET, 7 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Cards 16

Operations for creating, retrieving, updating, and deleting cards, including managing card attachments, checklists, comments, labels, members, and stickers.

POST
/cards
Create a Card
createCard 11 params → 200400401
GET
/cards/{id}
Get a Card
getCard 7 params → 200401404
PUT
/cards/{id}
Update a Card
updateCard 14 params → 200401404
DELETE
/cards/{id}
Delete a Card
deleteCard 1 param → 200401404
GET
/cards/{id}/actions
Get Actions on a Card
getCardActions 2 params → 200401404
POST
/cards/{id}/actions/comments
Add a Comment to a Card
createCardComment 2 params → 200401404
GET
/cards/{id}/attachments
Get Attachments on a Card
getCardAttachments 2 params → 200401404
POST
/cards/{id}/attachments
Create an Attachment on a Card
createCardAttachment 4 params → 200401404
GET
/cards/{id}/checklists
Get Checklists on a Card
getCardChecklists 1 param → 200401404
POST
/cards/{id}/checklists
Create a Checklist on a Card
createCardChecklist 4 params → 200401404
POST
/cards/{id}/labels
Add a Label to a Card
addCardLabel 2 params → 200401404
DELETE
/cards/{id}/labels/{idLabel}
Remove a Label from a Card
removeCardLabel 2 params → 200401404
POST
/cards/{id}/members
Add a Member to a Card
addCardMember 2 params → 200401404
DELETE
/cards/{id}/members/{idMember}
Remove a Member from a Card
removeCardMember 2 params → 200401404
GET
/cards/{id}/stickers
Get Stickers on a Card
getCardStickers 1 param → 200401404
POST
/cards/{id}/stickers
Add a Sticker to a Card
addCardSticker 6 params → 200401404

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are Card (23 properties), Member (13 properties), Attachment (10 properties), CheckItem (7 properties). Each schema is shown below with its type and property counts.

Attachment
object
Represents a file or URL attachment on a card.
10 properties
CheckItem
object
Represents a single item in a checklist that can be checked or unchecked.
7 properties
Action
object
Represents an activity event that occurred on a Trello object, such as creating a card, adding a comment, or moving a card between lists.
7 properties
Member
object
Represents a Trello user who can be a member of boards, organizations, and cards.
13 properties
Label
object
Represents a color-coded label that can be applied to cards for categorization and filtering.
4 properties
Card
object
Represents a Trello card, which is the fundamental unit of work on a board. Cards live within lists and can have members, labels, checklists, attachments, due…
23 properties
Checklist
object
Represents a checklist on a card, containing a list of check items that can be marked as complete or incomplete.
6 properties
Sticker
object
Represents a decorative sticker placed on a card.
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

trello-cards-api-openapi.yml Raw ↑

Other APIs Trello publishes across the network.

Trello Webhooks API
Trello Power-Ups
trello Actions API
trello Boards API
trello Checklists API
trello CustomFields API
trello Labels API
trello Lists API
trello Members API
trello Notifications API
trello Organizations API
trello Plugins API
Where this information came from

This is an independent, third-party profile of trello Cards API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.