Get Started
- Introduction
- Quickstart
Documentation
- Data Sources
- Business Objects
- Business Graph™
- Knowledge
- Query Agent
- Reports
- Subscriptions
- Destinations
- Tools
- Introduction
- Ably
- Acculynx
- Active campaign
- Affinity
- Agencyzoom
- Ahrefs
- Airtable
- Alchemy
- Amplitude
- Apaleo
- Apollo
- Asana
- Attio
- Bamboohr
- Bannerbear
- Baserow
- Bill
- Bitbucket
- Blackboard
- Bolna
- Borneo
- Box
- Brevo
- Browseai
- Browserbase tool
- Bugbug
- Cal
- Calendly
- Canva
- Canvas
- Chatwork
- Clickup
- Coda
- Codeinterpreter
- Coinbase
- Composio
- Composio search
- Confluence
- Contentful
- Crustdata
- D2lbrightspace
- Dialpad
- Discord
- Discordbot
- Docusign
- Dropbox
- Dynamics365
- Echtpost
- Elevenlabs
- Entelligence
- Exa
- Excel
- Figma
- Firecrawl
- Fireflies
- Flutterwave
- Formsite
- Foursquare
- Freshdesk
- Github
- Gmail
- Gong
- Google maps
- Googleads
- Googlebigquery
- Googlecalendar
- Googledocs
- Googledrive
- Googlemeet
- Googlephotos
- Googlesheets
- Googlesuper
- Googletasks
- Gorgias
- Hackernews
- Heygen
- Hubspot
- Humanloop
- Intercom
- Jira
- Junglescout
- Klaviyo
- Kommo
- Linear
- Linkedin
- Linkhut
- Linkup
- Listennotes
- Lmnt
- Mailchimp
- Mem0
- Metaads
- Microsoft clarity
- Microsoft teams
- Mixpanel
- Monday
- More trees
- Neon
- Ngrok
- Notion
- One drive
- Onepage
- Open sea
- Outlook
- Pagerduty
- Pandadoc
- Peopledatalabs
- Perplexityai
- Pipedrive
- Placekey
- Posthog
- Quickbooks
- Ramp
- Recallai
- Reddit
- Resend
- Retellai
- Rocketlane
- Rootly
- Salesforce
- Semanticscholar
- Semrush
- Sendgrid
- Sentry
- Serpapi
- Servicenow
- Share point
- Shopify
- Shortcut
- Simplesat
- Slack
- Slack user
- Slackbot
- Snowflake
- Stripe
- Supabase
- Tavily
- Text to pdf
- Textrazor
- Tinyurl
- Todoist
- Trello
- Twitter
- Twitter media
- Typefully
- Weathermap
- Webflow
- Whatsapp
- Workiom
- Wrike
- Yousearch
- Youtube
- Zendesk
- Zenrows
- Zoho
- Zoom
- Zoominfo
- Admin
Changelog
Trello
A web-based, kanban-style, list-making application.
Creates a new trello board with customizable attributes and settings. this endpoint allows you to set up a board tailored to your project needs, including its name, description, organization affiliation, and various preferences. you can create a board from scratch or copy an existing one, making it versatile for different use cases. use this when setting up a new project, team workspace, or when you need to replicate an existing board structure. the endpoint offers extensive customization options, from basic details to advanced settings like permissions, power-ups, and visual preferences. note that while many parameters are optional, setting them during creation can save time in subsequent board setup and configuration.
Creates a new label on a specific trello board. this endpoint allows users to add a label with a specified color and/or name to organize and categorize cards on the board. the new label can be used to visually distinguish and group cards, enhancing the board’s organization. use this when you need to introduce a new category or status for cards on a particular board. the color and name are both optional, allowing for flexible label creation based on user needs. note that while you can create a label with no color and no name, it’s generally more useful to specify at least one of these attributes for meaningful organization.
Retrieves information about the list associated with a specific trello action. this endpoint is useful when you need to determine which list was affected by a particular action, such as moving a card or updating a list’s properties. it provides context for action events, helping to track changes across a trello board. use this endpoint when you want to get details about the list involved in a specific action, rather than querying all lists on a board. note that this endpoint focuses solely on the list associated with the action and does not provide information about the action itself or other related entities like cards or board details.<<DEPRECATED use get_actions_list_by_id_action>>
Generates a new email key for a specific trello board. this endpoint is used to create or regenerate a unique email address associated with the board, enabling email-to-board functionality. when invoked, it will invalidate any previously existing email key for the specified board and return a new one. this tool is essential for setting up or updating email integration with a trello board, allowing users to add cards to the board by sending emails to the generated address. it should be used when initially configuring email-to-board features or when needing to reset the email integration for security reasons. note that generating a new key will immediately render the old email address non-functional for adding cards to the board.
Generates or regenerates a calendar key for a specific trello board. this endpoint is used to create a unique identifier that allows integration between the trello board and external calendar services. the generated key can be used to set up synchronization of board events, due dates, and deadlines with calendar applications. this tool should be used when setting up new calendar integrations or when refreshing existing integrations for security purposes. it’s important to note that generating a new key will invalidate any previous calendar key for the same board, potentially disrupting existing integrations until updated with the new key.
Creates a new list within a specified trello board. this endpoint allows users to add a new organizational category to their board, enabling better task management and workflow organization. use this when you need to create a new stage in your project workflow or want to categorize tasks in a different way. the new list will appear on the specified board and can be populated with cards representing individual tasks or items. note that this endpoint only creates an empty list; you’ll need to use separate endpoints to add cards to the newly created list.
Retrieves the board associated with a specific trello action. this endpoint allows you to fetch detailed information about the board on which a particular action occurred. it’s useful when you need to understand the context of an action, such as determining which board a card was moved to or where a comment was added. this tool is particularly helpful for tracking the flow of work across different boards or for auditing purposes. note that while it provides board details, it doesn’t return information about the action itself or other board elements like lists or cards.<<DEPRECATED use get_actions_board_by_id_action>>
Creates a new checklist on a specified trello board. this endpoint allows you to add a named checklist to an existing board, providing a way to organize and track tasks or items within a board. use this when you need to create a new list of to-do items, track project milestones, or add any structured list of tasks to a trello board. the checklist will be empty upon creation; items can be added to it in subsequent operations. this operation is useful for setting up new project structures or preparing boards for upcoming tasks. note that while you can create multiple checklists on a board, each checklist is treated as a separate entity and will need to be managed individually.
Retrieves detailed information about a specific action in trello. this endpoint allows you to fetch the complete data associated with a single action, such as creating a card, moving a list, or adding a comment. it’s useful when you need to access the full context and details of a particular activity that occurred on a trello board. the endpoint should be used when you want to investigate or audit specific changes, or when building activity logs and timelines. note that this endpoint only provides information about a single action; for retrieving multiple actions or a feed of activities, a different endpoint would be more appropriate.<<DEPRECATED use get_actions_by_id_action>>
Adds a new checklist to a specified trello card. this endpoint allows you to create a new checklist from scratch, copy an existing checklist, or add an existing checklist to the card. it’s useful for organizing tasks within a card, breaking down larger tasks into smaller, manageable steps. use this when you need to add a list of to-do items or a set of subtasks to a card. the checklist can be populated with items immediately by copying from an existing checklist, or it can be created empty for later population. this endpoint is particularly helpful for standardizing workflows or replicating common task lists across different cards.
Marks a specific trello board as viewed by the current user. this endpoint is used to update the board’s status, indicating that the user has seen the latest changes or updates on the board. it’s particularly useful for managing notifications and keeping track of which boards have been recently accessed by the user. the endpoint should be called when a user views a board, typically after loading the board’s content or when explicitly marking it as seen. this action may affect the board’s position in the user’s board list and the notification status for recent activities on the board. note that this endpoint only updates the viewed status and does not modify any other board properties or content.
Adds a specified member to a trello card. this endpoint allows you to assign a team member or user to a specific card, which represents a task or project item. use this when you need to delegate responsibilities, track ownership of tasks, or involve specific team members in a card’s activities. the operation requires the unique identifiers of both the card and the member to be added. this functionality is essential for managing team assignments and task distribution within trello boards. note that this endpoint only adds one member at a time; for bulk assignments, multiple calls may be necessary.
Adds a specified power-up to a trello board, enhancing its functionality. this endpoint allows users to enable built-in trello power-ups such as calendar view, card aging, activity recap, or voting features on a specific board. it should be used when you want to extend a board’s capabilities with additional tools for improved project management and team collaboration. the endpoint is board-specific and only adds one power-up at a time. note that this endpoint does not handle custom or third-party power-ups, only the predefined trello power-ups listed in the ‘value’ parameter.
Adds a new comment to a specific trello card. this endpoint allows users to contribute to the conversation on a card by adding textual comments. it’s useful for providing updates, asking questions, or engaging in discussions related to the card’s content or progress. the comment can include mentions of other users and references to other trello elements. this endpoint should be used when you need to programmatically add comments to cards, such as for automated notifications or integrations with other systems. note that while this endpoint adds comments, it does not support attaching files directly - attachments would need to be handled separately.
Adds a new check item to a specific checklist within a trello card. this endpoint allows users to create and append individual tasks or items to an existing checklist, helping to break down larger card tasks into smaller, manageable pieces. it’s particularly useful for adding new steps or requirements to a card’s workflow after the initial checklist has been created. the endpoint requires the card id and checklist id to ensure the new check item is added to the correct location. users can optionally specify the name of the check item and its position within the checklist for precise placement.
This endpoint marks all notifications associated with a specific trello card as read. it’s useful for managing notification status programmatically, especially in scenarios where bulk actions on card notifications are needed. the endpoint should be used when you want to clear the unread status of all notifications linked to a particular card, such as after a user has viewed or processed the card’s updates. this action is irreversible, so use it judiciously. note that this endpoint only affects the read status of notifications and does not delete or modify the notifications themselves.
Adds a specific label to a trello card. this endpoint allows you to associate an existing label with a particular card, enhancing the card’s categorization and visual organization on the board. use this when you need to tag a card with a predefined label, such as for priority levels, project phases, or any custom categories your team uses. the endpoint requires the card’s id in the url path and the label’s id in the request body. it’s important to note that this endpoint only adds existing labels; it cannot create new labels or modify label properties. ensure that both the card and the label exist before making this api call.
This endpoint allows you to add a new label to a specific trello card. it provides options to set the label’s color, name, and value, enabling better organization and visual categorization of cards on a trello board. use this endpoint when you need to add or update labels on a card to reflect its status, priority, or any other classification. the endpoint is particularly useful for automating label management or implementing custom labeling logic in your trello workflows. note that while you can specify both ‘color’ and ‘value’ parameters, ‘value’ takes precedence if both are provided. also, be aware that creating too many unique labels might clutter your board, so use this feature judiciously.
Creates a new card in a specified trello list with customizable attributes. this endpoint allows you to add a card to an existing list, optionally copying properties from another card, setting due dates, assigning members, adding labels, and more. use this when you need to programmatically create new tasks or items in your trello workflow. the endpoint is versatile, supporting simple card creation with just a name and list id, as well as complex scenarios involving multiple attributes and attachments. note that while many parameters are optional, at minimum, you must specify the ‘idlist’ where the card will be added.
This endpoint adds an attachment to a specific trello card. it allows users to upload files directly or attach links to external resources, enhancing the card’s information and context. use this when you need to include supporting documents, images, or relevant web links to a card. the attachment can be either a file upload or a url, providing flexibility in the types of resources that can be added. note that while the endpoint accepts various attachment types, there may be size limits or file type restrictions imposed by trello’s system.
Adds a member’s vote to a specific trello card. this endpoint allows you to record a ‘yes’ vote from a particular member on a given card. it’s useful for tracking member opinions or decisions related to the card’s content or status. the endpoint should be used when you need to programmatically add a member’s approval or agreement to a card, which can be helpful in workflows that require voting or consensus. note that this endpoint only adds positive votes; there is no option to add a negative vote or remove a vote using this call. also, be aware that a member can only have one vote per card, so calling this endpoint multiple times for the same member on the same card will not result in multiple votes.
Adds a sticker to a specific trello card. this endpoint allows you to customize the appearance and position of a sticker on a card, enhancing visual organization and communication within your trello boards. use this when you want to highlight important information, categorize cards, or add visual cues to your trello workflow. the sticker’s image, position, rotation, and stack order can be specified for precise placement. note that this endpoint only adds a single sticker per request; multiple calls are required to add multiple stickers to the same card.
Creates a new checklist in trello, either on a board or within a specific card. this endpoint allows you to add a customizable checklist to organize tasks and track progress. you can create an empty checklist or copy an existing one, specify its name, and set its position. use this when you need to add a new set of to-do items or a list of tasks to be completed. this is particularly useful for breaking down larger tasks into manageable steps or creating standardized processes across different cards or boards. note that while you can create the checklist structure with this endpoint, adding individual checklist items requires separate api calls.
This endpoint adds a new check item to an existing trello checklist. it allows users to create and position new tasks or items within a checklist, enhancing the organization and tracking of work items on a trello board. the endpoint should be used when adding new subtasks or items to a checklist, such as when breaking down a larger task into smaller, actionable steps. it provides flexibility in naming the item, setting its initial completion status, and positioning it within the checklist. however, it does not allow for adding multiple items at once or updating existing items - separate api calls would be needed for those operations. the checklist id must be known and provided in the url path when making this api call.
Retrieves detailed information about a specific action in trello. this endpoint allows you to fetch the complete data associated with a single action, such as creating a card, moving a list, or adding a comment. it’s useful when you need to access the full context and details of a particular activity that occurred on a trello board. the endpoint should be used when you want to investigate or audit specific changes, or when building activity logs and timelines. note that this endpoint only provides information about a single action; for retrieving multiple actions or a feed of activities, a different endpoint would be more appropriate.
Moves all cards from a specified trello list to a different board. this endpoint is useful for bulk transferring cards when reorganizing projects or merging boards. it allows users to quickly relocate an entire list’s content to a new board without manually moving each card. the operation is irreversible, so it should be used with caution. note that this action only moves the cards; it does not copy them or affect the original list structure.
Updates the list assignment of a specific trello card. this endpoint allows you to move a card from one list to another within the same board. it’s particularly useful for updating the status or progress of a task represented by the card. the operation is idempotent, meaning that moving a card to its current list will not cause any changes. this endpoint should be used when you need to programmatically update the position of a card in your trello workflow. it’s important to note that this operation only changes the list assignment and does not modify any other attributes of the card.<<DEPRECATED use update_cards_id_list_by_id_card>>
This endpoint allows you to add a new card to a specific list in trello. it’s used to create a task or item within an existing list on a trello board. the endpoint provides options to set various attributes of the card, including its description, due date, assigned members, labels, and name. this is particularly useful for programmatically creating new tasks or items in your trello workflow. note that while all parameters for card creation are optional, it’s recommended to at least provide a name for the card to easily identify it on the board. the list id (idlist) must be specified in the path to determine where the new card will be placed.
Creates a new webhook for a specific trello token, enabling real-time notifications for events on a specified trello model (such as a board, list, or card). this endpoint allows applications to set up automated triggers for changes in trello, facilitating seamless integration and synchronization with external systems. use this when you need to monitor and react to updates in trello in real-time. the webhook will send post requests to the specified callback url whenever relevant events occur on the monitored model. note that you must have appropriate permissions for the token and the model being monitored.
Retrieves a specific field of a trello action identified by its unique id. this endpoint allows for targeted data retrieval, enabling users to fetch individual attributes of an action without retrieving the entire action object. it’s particularly useful when you need a single piece of information about an action, such as its type, date, or associated member. the endpoint should be used when precise, field-level data about a trello action is required, reducing data transfer and processing overhead. however, it does not provide comprehensive action details in a single call, so multiple requests may be necessary if several fields are needed.
Permanently deletes a trello organization and all its associated data. this endpoint should be used when an organization is no longer needed and all its boards, lists, cards, and member associations should be removed. once an organization is deleted, the action cannot be undone, and all data will be lost. this operation requires appropriate permissions, typically limited to organization administrators. use this endpoint with caution as it will remove all resources linked to the organization, including shared boards and team data.
Adds a board star for a specific trello member, allowing them to mark a board as a favorite or frequently accessed. this endpoint is used to create a new board star, specifying which board to star and where to position it in the member’s list of starred boards. it’s particularly useful for organizing and prioritizing boards for quick access. the endpoint should be used when a user wants to star a new board or adjust the position of an existing starred board. it does not provide functionality for removing board stars or retrieving a list of starred boards.
Deletes a specific checklist from a trello card. this endpoint allows users to remove a checklist entirely from a card, which can be useful for cleaning up completed or unnecessary checklists. the operation is irreversible, so it should be used with caution. this endpoint is particularly helpful when managing card content and simplifying the card’s structure by removing outdated or completed checklists. it requires both the card’s id and the checklist’s id to ensure precise targeting of the checklist to be deleted.
This endpoint removes the invite restriction preferences for a specific trello organization. when invoked, it resets the organization’s settings related to who can invite new members, effectively removing any custom restrictions that were previously in place. this action allows for more open member invitation policies within the organization. use this endpoint when you want to lift invite restrictions and allow all members to invite new people to the organization. it’s particularly useful for organizations that previously had strict invite policies but now want to encourage growth and collaboration. note that this action may have security implications, as it potentially broadens who can add new members to the organization.
The delete card endpoint permanently removes a specific card from a trello board. this operation is irreversible and should be used with caution when a task or item represented by the card is no longer needed or was created in error. it’s important to note that while the schema doesn’t specify, trello typically requires a card to be archived before it can be deleted. this endpoint is useful for cleaning up boards and removing obsolete information, but users should ensure they have the necessary permissions and have backed up any important data from the card before deletion. the operation returns a simple success or failure response without additional details about the deleted card.
Adds a new board background to a specific trello member’s collection. this endpoint allows users to upload and configure custom background images for their trello boards, enhancing the visual customization of their workspace. the new background can be set with specific brightness levels and tiling options, providing flexibility in how the image is displayed on the board. this tool should be used when a user wants to expand their selection of available board backgrounds or when implementing features that allow for dynamic board customization. note that this endpoint only adds the background to the member’s collection; to apply it to a specific board, an additional api call would be required.
Deletes a specific check item from a checklist on a trello board. this endpoint is used to permanently remove an individual task or item from a checklist, helping to manage and organize the content of trello cards. it should be used when a task is no longer relevant, completed and needs to be cleared, or was added by mistake. the operation is irreversible, so caution should be exercised when using this endpoint. it’s important to note that this endpoint only deletes the check item and not the entire checklist. if you need to delete the entire checklist, a separate api call would be required.
Creates a new label on a specified trello board. this endpoint allows users to add a custom label with a specific color and name to organize and categorize cards more effectively. it should be used when setting up a new board, introducing a new category, or refining the existing labeling system. the created label can then be applied to cards across the board. note that this endpoint only creates the label; it does not automatically apply it to any cards. there’s a limit to how many labels can be created on a single board, typically around 1000, but it’s best to use labels judiciously for clarity.
Creates a new list within a specified trello board. this endpoint allows users to add a custom list to their board, optionally copying from an existing list, setting its position, and defining its initial state. it’s particularly useful for organizing tasks, creating new workflow stages, or expanding board structure. the new list can be created open or closed, and the creating user can choose to subscribe to it for notifications. this tool should be used when setting up new projects, restructuring workflows, or expanding existing boards. it doesn’t modify existing lists or move cards between lists.
Creates a new trello board with customizable attributes and settings. this endpoint allows you to set up a board tailored to your project needs, including its name, description, organization affiliation, and various preferences. you can create a board from scratch or copy an existing one, making it versatile for different use cases. use this when setting up a new project, team workspace, or when you need to replicate an existing board structure. the endpoint offers extensive customization options, from basic details to advanced settings like permissions, power-ups, and visual preferences. note that while many parameters are optional, setting them during creation can save time in subsequent board setup and configuration.<<DEPRECATED use add_boards>>
This endpoint archives all cards within a specified trello list. it provides a convenient way to bulk archive multiple cards simultaneously, helping users clean up and organize their trello boards efficiently. the operation is irreversible through this endpoint, so it should be used with caution. this tool is particularly useful when closing out completed projects, clearing inactive lists, or performing board-wide cleanups. note that while cards are archived, they are not deleted and can still be accessed or restored through trello’s archive feature.
This endpoint retrieves a specific field of the organization associated with a particular trello action. it allows you to fetch detailed information about the organization context in which an action occurred. use this endpoint when you need to access specific organization details related to a trello action, such as the organization’s name or id. this can be particularly useful for tracking and analyzing actions across different organizations or teams within your trello workspace. note that this endpoint focuses on a single field of the organization and does not provide comprehensive information about the action or the entire organization object.
Retrieves the organization information associated with a specific trello action. this endpoint allows you to trace back an action to its parent organization, providing valuable context for auditing, reporting, or analysis purposes. use this when you need to identify which organization an action belongs to or when you want to gather more details about the organization context of a particular trello activity. the endpoint returns organization data such as name, id, and other relevant details. it’s particularly useful for applications that need to track actions across different organizational boundaries or for maintaining a clear audit trail of activities within trello.
This endpoint allows you to update the avatar image for a specific trello member. it’s used when you want to change or set a new profile picture for a user in trello. the endpoint accepts a base64-encoded image file and associates it with the specified member’s profile. this is useful for personalizing user profiles or updating outdated avatars. note that this endpoint only changes the avatar and does not modify any other member information. ensure you have the necessary permissions to modify the specified member’s profile before using this endpoint.
Retrieves the display information for a specific trello action. this endpoint is used to fetch formatted or user-friendly representations of action data, which can be helpful for presenting action details in a more readable or visually appealing manner. it’s particularly useful when you need to show action information in a user interface or generate reports. the endpoint focuses solely on display-related data and does not provide full action details or modify the action in any way. use this when you need to present action information to users or need a simplified view of action data for display purposes.
Retrieves a specific field of a card associated with a particular action in trello. this endpoint is useful when you need to access detailed information about how a card was affected by a specific action, without fetching the entire card object. it allows for granular data retrieval, which can be particularly beneficial for tracking changes, auditing, or gathering specific data points about card modifications. the endpoint should be used when you have an action id and need to know how that action affected a particular aspect of a card. it’s important to note that this endpoint only provides information about the specified field and does not return the entire card object or details about the action itself.
Retrieves information about the list associated with a specific trello action. this endpoint is useful when you need to determine which list was affected by a particular action, such as moving a card or updating a list’s properties. it provides context for action events, helping to track changes across a trello board. use this endpoint when you want to get details about the list involved in a specific action, rather than querying all lists on a board. note that this endpoint focuses solely on the list associated with the action and does not provide information about the action itself or other related entities like cards or board details.
Retrieves the member information associated with a specific action in trello. this endpoint is used to identify and fetch details about the user who performed a particular action on a trello board, such as moving a card or updating a list. it’s particularly useful for tracking user activities and understanding who made certain changes within a board. the endpoint returns member data related to the action, which may include the user’s id, username, and other relevant information. this tool should be used when you need to connect an action with its performer or when auditing board activities. note that it only provides information about the member in the context of the specified action and does not give a comprehensive view of the member’s overall trello account or activities.
Updates the position of a specific trello card within its current list. this endpoint allows you to move a card to the top, bottom, or a specific position in its list, helping to reorganize tasks and priorities. use this when you need to change the order of cards in a list without changing the list itself. the new position is specified using either keywords (‘top’, ‘bottom’) or a numeric value, providing flexibility in card arrangement. this operation is particularly useful for reordering tasks, adjusting priorities, or maintaining a specific workflow sequence within a trello board.<<DEPRECATED use update_cards_pos_by_id_card>>
Converts a specific checklist item within a trello card into a new, separate card. this endpoint is useful for expanding a subtask or checklist item into a full-fledged card, allowing for more detailed tracking and management. it should be used when a checklist item requires more elaborate handling or when you want to create a hierarchical relationship between tasks. the newly created card will inherit information from the original checklist item, but the exact details of inheritance are not specified in the schema. this operation is irreversible through the api, so it should be used judiciously. note that this endpoint does not provide options for customizing the new card beyond the conversion process.
This endpoint allows you to add a custom emoji to a specific trello member’s account. it enables personalization of the trello experience by letting members create and use their own unique emojis. the custom emoji can be used in various trello elements such as card descriptions, comments, or checklists. this endpoint should be used when a member wants to expand their emoji options beyond the standard set provided by trello. it’s important to note that these custom emojis are specific to the member and are not shared across the entire trello workspace. be aware that there may be limitations on the number of custom emojis a member can add, although this is not specified in the schema.
Revokes and deletes a specific trello api token. this endpoint should be used when you want to invalidate an existing token, preventing it from being used for future api requests. it’s particularly useful for enhancing security by removing access for unused or compromised tokens. the operation is irreversible, so use it with caution. after deletion, any applications or integrations using this token will lose access to the trello api and will need to re-authenticate to obtain a new token.
Retrieves detailed information about the card associated with a specific trello action. this endpoint is useful when you need to access the current state or details of a card that was affected by a particular action, such as a card being moved, edited, or commented on. it provides a way to trace the impact of an action on a card and gather its up-to-date information. use this endpoint when you want to follow up on an action notification or need to sync card data after a known action has occurred. note that this endpoint only returns information about the card itself and not about the action that led to querying this card.
This endpoint allows you to add a custom board background for a specific trello member. it enables personalization of a member’s trello boards by uploading and configuring a unique background image. use this endpoint when you want to enhance the visual appeal of a member’s boards or create a distinct look for different projects or teams. the custom background can be adjusted for brightness and tiling to ensure optimal visibility of board content. note that this endpoint is member-specific and should be used judiciously to maintain a balance between personalization and consistent team experience.
Retrieves a specific field of the list associated with a given trello action. this endpoint is useful when you need to access particular information about the list where an action occurred, without fetching all list details. it can be used to confirm the list’s name, check if it’s closed, or get its board id after an action has been performed. this endpoint is particularly helpful for tracking changes or verifying the current state of a list following a specific action. note that it only returns a single field value, not the entire list object, making it efficient for targeted data retrieval.
Retrieves a specific field of the member who created a particular action in trello. this endpoint allows you to access detailed information about the user who initiated an action, such as their username, full name, or avatar url. it’s useful for tracking who performed certain actions on a trello board, which can be valuable for auditing, user activity analysis, or displaying user information in your application. the endpoint is read-only and does not modify any data in trello. note that you can only retrieve fields that are publicly available or that you have permission to access based on your authentication level.
This endpoint allows you to delete the logo associated with a specific trello organization. it removes the custom logo image that was previously uploaded and set for the organization, reverting it to the default trello logo or placeholder. this operation is permanent and cannot be undone, so it should be used with caution. it’s particularly useful when rebranding an organization or removing outdated visual identities. note that this endpoint only deletes the logo and does not affect any other organization settings or data.
Retrieves the entities associated with a specific trello action. this endpoint allows you to fetch detailed information about the entities (such as boards, lists, cards, or members) that are related to a particular action in trello. it’s useful for obtaining context and additional data about actions that have occurred within a trello workspace. for example, if an action represents a card being moved, this endpoint could provide details about the card, the source list, the destination list, and the board involved. use this endpoint when you need to gather comprehensive information about the objects affected by or involved in a specific trello action.
The batchrequest endpoint allows you to execute multiple trello api requests in a single http call. this powerful feature enables efficient bulk operations and reduces network overhead. use this endpoint when you need to perform multiple, potentially independent operations on trello resources (such as boards, lists, or cards) simultaneously. the batch request is particularly useful for complex workflows or when synchronizing data between trello and external systems. keep in mind that there may be rate limits or restrictions on the number of requests allowed in a single batch call. this endpoint does not support mixing different http methods within a single batch request.
This endpoint removes a specific label from a trello card. it’s used to update the organization or categorization of a card by removing an associated label. the operation is performed by sending a delete request to the specified url with the card id and label id as path parameters. this action is irreversible and should be used when you want to disassociate a label from a card, such as when a task changes category or a tag is no longer relevant. it’s important to note that this endpoint only removes the association between the card and the label; it does not delete the label itself from the trello board.
Retrieves a specific field of the trello board associated with a given action. this endpoint allows you to fetch targeted information about a board without retrieving the entire board object. it’s particularly useful when you need to access a single piece of board data related to a specific action, such as the board’s name or url. the endpoint should be used when you have an action id and want to know a particular attribute of the board where that action occurred. it will not provide information about the action itself or other board details beyond the requested field. keep in mind that the availability of certain fields may depend on the permissions of the authenticated user and the current state of the trello api.
Retrieves a list of board stars associated with a specific trello board. board stars represent boards that a user has marked as favorite or important, making them easier to access from their trello dashboard. this endpoint is useful for applications that need to display a user’s starred boards or analyze which boards are frequently accessed by team members. it should be used when you need to fetch the star status of a particular board or list all starred boards for a user. note that this endpoint only provides information about the star status and does not allow for adding or removing stars from boards.
This endpoint retrieves a specific field of the member associated with a particular action in trello. it allows you to fetch targeted information about the member who performed or is related to a specific action, without retrieving all member data. this can be useful for obtaining specific details like the member’s username or avatar url in the context of an action. the endpoint is particularly helpful when you need to display or process only a single piece of member information related to an action, reducing data transfer and processing overhead. however, it’s important to note that this endpoint is limited to retrieving only one field at a time; for multiple fields, separate api calls would be necessary.
Removes a member from a trello organization completely. this endpoint should be used when you want to revoke all of a member’s access and permissions within an organization. it will remove the member from all boards, teams, and other resources associated with the organization. this action is permanent and cannot be undone through the api, so it should be used with caution. the endpoint is particularly useful for managing team changes, such as when an employee leaves a company or a project concludes. note that this does not delete the member’s trello account, only their association with the specific organization.
Deletes a specific trello action identified by its unique id. this endpoint should be used when you need to permanently remove an action from a trello board’s history. it’s particularly useful for cleaning up unwanted or erroneous actions, such as accidental card creations or comments. once an action is deleted, it cannot be recovered, so use this endpoint with caution. note that not all actions may be deletable, and attempting to delete certain system-generated actions might result in an error.
Retrieves all labels associated with a specific trello board. this endpoint allows users to fetch the complete set of labels used for categorizing cards within the specified board. it’s particularly useful for getting an overview of the board’s organization system or when preparing to add or update labels on cards. the endpoint returns label information such as names, colors, and ids, which can be used in other api calls for label management or card updates. note that this endpoint only provides label data and does not include information about which cards are using each label.
Retrieves all cards associated with a specific trello board. this endpoint allows users to fetch a comprehensive list of cards, including their details such as names, descriptions, due dates, and other attributes, from a given board. it’s particularly useful for getting an overview of all tasks or items within a project or workflow. the endpoint should be used when you need to gather information about multiple cards at once, rather than querying individual cards separately. note that this endpoint may have limitations on the number of cards returned in a single request for boards with a large number of cards, and pagination might be necessary for complete retrieval.
Removes a specific member from a trello card. this endpoint is used when you need to unassign a user from a particular card, perhaps because they have completed their part of the task or are no longer involved in the work related to that card. the operation is irreversible through this endpoint alone, meaning that if you need to re-add the member to the card, you would need to use a separate api call. this endpoint is particularly useful for automating workflow management, such as when a task is completed or reassigned. note that removing a member from a card does not affect their overall board membership or permissions; it only changes their association with the specific card.
This endpoint removes a specific member from a trello organization. it allows organization administrators to revoke a user’s access to all boards, lists, and cards associated with the organization. use this endpoint when you need to remove a team member who no longer requires access to the organization’s resources. the removal is permanent, and the member will lose all permissions and visibility to the organization’s content. if the member needs to be re-added in the future, they will need to be invited again. note that this action does not delete the user’s trello account; it only removes their association with the specific organization.
Retrieves a specific field’s value from a trello board. this endpoint allows you to fetch individual pieces of information about a board without retrieving the entire board object. it’s particularly useful when you need quick access to a single attribute, such as the board’s name, description, or url. this method should be used when you require only one specific piece of information about a board, rather than its complete details. note that the availability and naming of fields may depend on the current trello api specification, and some fields might have restricted access based on user permissions.
Retrieves a list of cards from a specified trello board, with optional filtering capabilities. this endpoint is essential for accessing and managing task information within a trello project. it allows users to fetch cards based on various criteria, enabling efficient organization and analysis of project tasks. the endpoint is particularly useful for integrations that need to sync trello data with other project management tools or for creating custom reports and dashboards. note that while this endpoint provides comprehensive card data, it does not modify any information on the board.
Retrieves detailed information about the member who created a specific action in trello. this endpoint is useful for tracking who performed particular actions on trello boards, cards, or lists. it provides insights into user activity and can be valuable for audit trails or understanding the history of changes in a trello workspace. the endpoint returns information about the action creator, which may include their username, full name, avatar, and other relevant details. use this when you need to identify or get more information about the user responsible for a specific action in trello.
Retrieves a list of actions (events or changes) associated with a specific trello board. this endpoint is useful for tracking the history of activities on a board, such as card creations, movements, comment additions, or member assignments. it provides a comprehensive audit trail of changes made to the board and its contents. use this endpoint when you need to monitor board activity, implement change tracking, or create activity logs for project management purposes. the actions returned may be limited in number and sorted by recency, so it may not provide a complete historical record if the board has a long history of activities.
Retrieves the deltas (changes or updates) for a specified trello board. this endpoint allows you to fetch recent modifications made to the board, including changes to lists, cards, and other board elements. it’s particularly useful for synchronizing board data with external systems or monitoring board activity. the endpoint returns a list of changes since the last known state, enabling efficient tracking of board updates without fetching the entire board content. use this when you need to keep an external system up-to-date with trello board changes or when implementing real-time board activity monitoring.
Retrieves detailed information about a specific trello board. this endpoint allows you to fetch comprehensive data about a board, including its name, description, members, lists, and other associated metadata. use this endpoint when you need to access or display the current state and configuration of a particular board. it’s particularly useful for applications that need to sync board data, display board information, or perform operations based on the board’s current state. note that this endpoint only provides a read-only view of the board; it cannot be used to modify the board’s properties. the response will likely include all visible elements of the board, but may not include certain private or restricted information depending on the authentication level and permissions of the api key used.
Retrieves detailed information about a specific label on a trello board. this endpoint allows you to fetch the properties of a single label, such as its name, color, and any custom fields associated with it. use this when you need to access or verify the details of a particular label within the context of a specific board. it’s particularly useful for applications that manage or display trello labels, or for automations that need to check label properties. the endpoint will not modify the label or provide information about which cards the label is attached to. note that you must have appropriate permissions to view the specified board and its labels.
Removes an associated domain from a trello organization’s preferences. this endpoint is used to update the email domain restrictions for workspace membership by deleting a previously approved domain. it’s particularly useful for enterprise admins who need to modify organization-wide settings to control access and membership. the operation is irreversible, so it should be used carefully when you want to stop allowing automatic membership for users with email addresses from a specific domain. this endpoint doesn’t return the updated preferences; it only performs the deletion.
Retrieves detailed information about a specific card on a particular trello board. this endpoint is used to fetch up-to-date data for a single card, including its title, description, due date, assigned members, labels, and other associated metadata. it’s particularly useful when you need to access or display comprehensive information about a specific task or item within a trello workflow. this endpoint should be used when you have both the board id and card id and need the most current state of the card. it does not modify the card or board in any way, making it safe for frequent calls to keep local data in sync with trello’s servers. however, it’s important to note that this endpoint only returns data for a single card; for bulk operations or retrieving multiple cards, other endpoints would be more appropriate.
Removes a specific colored label from a trello card. this endpoint allows you to delete an existing label from a card, reducing its categorization or changing its status. it’s useful for updating the organization of tasks when a particular classification no longer applies. the operation is permanent and cannot be undone through this endpoint. use this when you need to declutter a card’s labels or when a task’s category or status has changed. note that this endpoint only removes the association between the label and the card; it does not delete the label itself from the trello board.
Removes a specified member from a trello board. this endpoint is used when you need to revoke a user’s access to a particular board, effectively ending their ability to view, edit, or interact with the board’s content. it’s particularly useful for managing team changes, project completions, or access control. the operation is permanent and cannot be undone through the api, so it should be used with caution. note that removing a member does not delete their contributions to the board, but it does remove their access to any automations they may have created.
Retrieves a list of memberships for a specific trello board. this endpoint allows you to fetch detailed information about the users associated with the board, including their roles (e.g., member, admin, observer) and permissions. use this endpoint when you need to audit board access, manage team members, or gather information about the board’s collaboration structure. it’s particularly useful for large teams or when transitioning project ownership. note that this endpoint only provides membership data and does not include other board details or the actual content of the board.
Retrieves a specific field from the organization associated with a trello board. this endpoint allows you to fetch targeted information about the organization that owns or is linked to a particular board, without retrieving all organization details. it’s useful when you need a specific piece of organization data in the context of a board, such as the organization’s name or description. this tool should be used when you need to quickly access a single organization attribute related to a board, rather than fetching and parsing full organization details. note that the available fields are limited to those defined in the trello api for organizations, and you must know the board’s id to use this endpoint.
Retrieves information about members who have been invited to a specific trello board but have not yet joined. this endpoint is useful for tracking pending invitations and managing board access. it allows you to view details of invited members, such as their names, email addresses, and the status of their invitations. use this when you need to review or follow up on outstanding board invitations. note that this endpoint only provides information about invited members, not active board members or other board details.
Retrieves a filtered list of members for a specific trello board. this endpoint allows you to fetch a subset of board members based on certain criteria, such as their role or status within the board. it’s particularly useful for managing large boards, performing targeted actions on specific groups of members, or auditing board membership. the endpoint requires the board’s unique identifier and a filter parameter to specify which members to return. it should be used when you need to analyze or manipulate board membership data programmatically. note that this endpoint only provides member information and does not allow for modifying member status or permissions directly.
Retrieves a specific field of information about members invited to a particular trello board. this endpoint is useful when you need to access targeted details about invited members without fetching their full profiles. it can be used to gather information such as email addresses, usernames, or full names of invited members, depending on the specified field. the endpoint is particularly helpful for board administrators or integration tools that need to manage or review board invitations. note that this endpoint only provides information about invited members who have not yet joined the board, not current board members.
Retrieves all checklists associated with a specified trello board. this endpoint allows you to fetch a comprehensive list of checklists that have been created within the given board, providing an overview of task breakdowns and subtasks. use this endpoint when you need to gather all checklist data for a particular board, such as for reporting, analysis, or syncing with external systems. it’s particularly useful for project managers or team leads who want to review the structure and progress of tasks within a board. note that this endpoint only returns checklist metadata and does not include the status of individual checklist items; to get that level of detail, you would need to make additional api calls for each checklist or card.
Retrieves a list of members associated with a specific trello board. this endpoint allows you to fetch all users who have access to the board, including their roles and permissions. use this when you need to get information about the team members working on a particular board, manage access, or sync member data with other systems. the endpoint returns member details such as usernames, full names, and member types, but does not provide in-depth information about their activities on the board.
Retrieves detailed information about a specific user’s membership on a trello board. this endpoint allows you to fetch the membership details, including the member’s role, permissions, and any custom fields associated with their membership on the specified board. it’s particularly useful when you need to verify a user’s access level or retrieve specific attributes of their membership. the endpoint should be used when you require in-depth information about a single membership, rather than a list of all memberships on a board. note that this endpoint only provides read access to membership data and cannot be used to modify the membership.
Retrieves detailed information about the organization (workspace) associated with a specific trello board. this endpoint allows you to fetch organizational data such as the workspace name, description, visibility settings, and other relevant details directly linked to the specified board. use this endpoint when you need to understand the broader context of a board within its organizational structure, such as determining workspace-level permissions or identifying other boards that might be part of the same workspace. this tool is particularly useful for applications that manage multiple trello boards across different organizations or for those that need to sync organizational data with external systems. note that this endpoint only provides information about the organization and does not return data about the board itself or its contents.
Retrieves lists associated with a specific trello board. this endpoint allows users to fetch all lists or filter them based on their status (open, closed, or all). it’s particularly useful for getting an overview of a board’s structure, preparing for task management, or syncing board data with external systems. the endpoint supports filtering to efficiently retrieve only the required lists, which is especially beneficial for boards with numerous lists. however, it does not provide detailed information about the cards within each list; separate api calls would be needed for that level of detail.
Retrieves all lists associated with a specific trello board. this endpoint allows you to fetch the complete set of lists that exist on a given board, providing an overview of the board’s structure and organization. use this when you need to display or analyze the current layout of a board, such as when building a board overview or preparing for task management operations. the endpoint returns basic information about each list, typically including its id, name, and position on the board. note that this endpoint does not return the cards within the lists; to get that level of detail, you would need to make separate api calls for each list.
Retrieves the current user’s preferences for a specific trello board. this endpoint allows users to fetch their personalized settings and configurations for a particular board, such as notification preferences, background preferences, or custom field settings. it’s useful when you need to display or sync a user’s board-specific preferences in your application. the endpoint returns only the preferences for the authenticated user and the specified board, not for other members or boards. use this when you want to tailor the user experience based on their individual board settings or when implementing features that require knowledge of user-specific board configurations.
Deletes a specific webhook associated with a trello token. this endpoint is used to remove a webhook from trello’s system, effectively stopping any further notifications for the events that the webhook was monitoring. it’s particularly useful when you no longer need to receive updates about certain changes in trello, such as modifications to a board, list, or card. the deletion is permanent, so use this endpoint with caution. if you need to reinstate notifications later, you’ll have to create a new webhook.
Retrieves a list of actions associated with a specific trello card. this endpoint allows users to fetch the history of changes and events that have occurred on a particular card, providing valuable insights into the card’s lifecycle and team interactions. it can be used to track updates, comments, moves between lists, and other significant events related to the card. this tool is particularly useful for auditing purposes, understanding the progression of a task, or gathering data for project analytics. keep in mind that the number of actions returned may be limited, and very old actions might not be available through this endpoint.
Retrieves all attachments associated with a specific trello card. this endpoint allows users to fetch a comprehensive list of files, documents, or other media that have been added to a particular card. it’s useful for obtaining detailed information about the attachments, such as file names, urls, and metadata, without needing to access the card itself. this tool should be used when you need to review or analyze the attachments of a card programmatically, such as for reporting, backup purposes, or to display attachment information in an external system. note that this endpoint only provides attachment data and does not allow for adding, modifying, or deleting attachments.
This endpoint marks all notifications as read for the authenticated trello user. it is used to quickly clear the user’s notification list, improving organization and reducing clutter in the trello interface. the operation is performed by sending a post request to /notifications/all/read. this tool should be used when a user wants to mark all their unread notifications as read in one action, typically after reviewing their notifications or when starting with a clean slate. it’s important to note that this action cannot be undone, and all notifications will be marked as read regardless of their content or importance. the endpoint doesn’t provide any filtering options, so it will affect all notifications across all boards the user has access to.
Removes a specified power-up from a trello board. this endpoint should be used when you want to disable or uninstall a particular power-up from a board, perhaps due to changes in workflow requirements or to streamline board functionality. it’s important to note that removing a power-up may affect any data or configurations associated with that power-up on the board. before using this endpoint, ensure that you no longer need the power-up’s functionality and that removing it won’t disrupt ongoing work or integrations. this action cannot be undone through the api, so use it with caution.
Retrieves all cards assigned to a specific member on a particular trello board. this endpoint is useful for getting a comprehensive view of a team member’s tasks within a project context. it can be used to track individual workload, assess task distribution, or gather data for productivity analysis. the endpoint returns only cards that are currently assigned to the specified member on the given board, and does not include cards from other boards or unassigned cards. it’s particularly helpful for project managers or team leads who need to review or report on a team member’s current responsibilities within a specific project or workflow.
Removes a specific member’s vote from a trello card. this endpoint is used when you need to undo a member’s vote on a card, which can be useful for managing decision-making processes or cleaning up outdated votes. it should be called when a member wants to retract their vote or when an administrator needs to remove a vote on behalf of a member. the operation is irreversible, so it should be used with caution. this endpoint does not provide any information about the remaining votes on the card or confirm the previous existence of the vote; it simply attempts to remove the specified member’s vote from the specified card.
Retrieves the board associated with a specific trello action. this endpoint allows you to fetch detailed information about the board on which a particular action occurred. it’s useful when you need to understand the context of an action, such as determining which board a card was moved to or where a comment was added. this tool is particularly helpful for tracking the flow of work across different boards or for auditing purposes. note that while it provides board details, it doesn’t return information about the action itself or other board elements like lists or cards.
Retrieves a list of cards from a specified trello board, with optional filtering capabilities. this endpoint is essential for accessing and managing task information within a trello project. it allows users to fetch cards based on various criteria, enabling efficient organization and analysis of project tasks. the endpoint is particularly useful for integrations that need to sync trello data with other project management tools or for creating custom reports and dashboards. note that while this endpoint provides comprehensive card data, it does not modify any information on the board.<<DEPRECATED use get_boards_cards_by_id_board_by_filter>>
This endpoint allows you to upload a new logo for a specified trello organization. it’s used to set or update the visual branding of an organization within trello. the endpoint accepts a file parameter in the request body, which should contain the logo image data. use this when you need to customize the appearance of a trello organization or update its existing logo. the uploaded logo will be displayed in various places where the organization is represented, such as the organization’s page and associated boards. note that there may be size and format restrictions for the logo file, which are not specified in this schema but should be considered when preparing the upload.
Deletes a specific attachment from a trello card. this endpoint allows users to remove an attachment, such as a file or document, from a particular card on their trello board. it should be used when a user wants to permanently remove an attachment that is no longer needed or relevant to the card. the operation is irreversible, so it should be used with caution. this endpoint is particularly useful for managing card content and keeping information up-to-date by removing outdated or unnecessary attachments.
Deletes a specific webhook from the trello system using its unique identifier. this endpoint is used to permanently remove a webhook that is no longer needed or has become obsolete. once deleted, the webhook will stop receiving notifications about changes to the associated trello resources. this operation is irreversible, so it should be used with caution. it’s particularly useful for cleaning up webhooks that are no longer in use, reducing unnecessary api calls and maintaining a clean integration setup.
This endpoint allows dismissing a specific type of one-time message for a trello member. it’s used to mark certain notifications or alerts as acknowledged or no longer relevant for the user. this is particularly useful for managing user preferences and reducing notification clutter. the endpoint should be called when a member interacts with a one-time message, choosing to dismiss it. it helps in personalizing the user experience by remembering which introductory or special messages the user has already seen and acknowledged.
Creates a new saved search for a specified trello member. this endpoint allows users to store frequently used search queries for quick access and improved productivity. it’s particularly useful for team members who regularly need to filter and find specific cards, boards, or other trello items. the saved search will be associated with the member’s account and can be easily accessed and executed from the trello interface. this feature is typically available to paid subscribers and helps in personalizing the trello experience for individual users.
This endpoint deletes a specific comment from a trello card’s action history. it allows users to remove unwanted or outdated comments associated with a particular card. the endpoint should be used when there’s a need to clean up or manage the comment history of a card, such as removing inappropriate content or correcting mistakes. it’s important to note that this action is irreversible, and once a comment is deleted, it cannot be recovered through the api. this endpoint only deletes comments and does not affect other types of card actions. users should exercise caution when using this endpoint, as it permanently removes information from the card’s history.
Retrieves all cards associated with a specific trello board. this endpoint allows users to fetch a comprehensive list of cards, including their details such as names, descriptions, due dates, and other attributes, from a given board. it’s particularly useful for getting an overview of all tasks or items within a project or workflow. the endpoint should be used when you need to gather information about multiple cards at once, rather than querying individual cards separately. note that this endpoint may have limitations on the number of cards returned in a single request for boards with a large number of cards, and pagination might be necessary for complete retrieval.<<DEPRECATED use get_boards_cards_by_id_board>>
Creates a new trello organization with customizable properties and preferences. this endpoint allows you to set up an organization structure, including its name, description, website, and various visibility and access settings. use this when you need to establish a new collaborative workspace for teams or projects in trello. the endpoint provides extensive options for configuring organization-wide preferences, such as board visibility restrictions, external member access, and google apps integration. it’s particularly useful for setting up organizations with specific security and collaboration requirements.
Deletes a specific checklist from a trello board. this endpoint should be used when you want to permanently remove a checklist and all its associated items from a card. it’s particularly useful for cleaning up completed or obsolete checklists, or when restructuring card content. the operation is irreversible, so use it with caution. once deleted, the checklist and its items cannot be recovered. this endpoint does not return the deleted checklist data; it typically returns a success status code upon successful deletion.
Removes a specific board from a trello member’s list of starred boards. this endpoint is used when a user wants to unstar a board, effectively removing it from their quick access list of favorite boards. it’s particularly useful for decluttering a user’s starred boards list or when a board is no longer frequently accessed. the operation is immediate and irreversible, but it does not affect the board itself or the user’s membership on the board; it only removes the ‘star’ status for that member. this endpoint should be used cautiously as it directly affects the user’s personal organization of boards.
Retrieves all lists associated with a specific trello board. this endpoint allows you to fetch the complete set of lists that exist on a given board, providing an overview of the board’s structure and organization. use this when you need to display or analyze the current layout of a board, such as when building a board overview or preparing for task management operations. the endpoint returns basic information about each list, typically including its id, name, and position on the board. note that this endpoint does not return the cards within the lists; to get that level of detail, you would need to make separate api calls for each list.<<DEPRECATED use get_boards_lists_by_id_board>>
Creates a new card in a specified trello list with customizable attributes. this endpoint allows you to add a card to an existing list, optionally copying properties from another card, setting due dates, assigning members, adding labels, and more. use this when you need to programmatically create new tasks or items in your trello workflow. the endpoint is versatile, supporting simple card creation with just a name and list id, as well as complex scenarios involving multiple attributes and attachments. note that while many parameters are optional, at minimum, you must specify the ‘idlist’ where the card will be added.<<DEPRECATED use add_cards>>
Retrieves a specific field of a trello card. this endpoint allows you to fetch individual attributes of a card without retrieving the entire card object, which can be useful for targeted data retrieval and improved performance. it should be used when you need to access a particular piece of information about a card, such as its name, description, due date, or any other supported field. this tool is particularly helpful for checking specific card details or for integrations that need to monitor or sync certain card attributes. note that this endpoint will only return the value of the requested field; if you need multiple fields or the complete card data, you should use a different endpoint that returns the full card object.<<DEPRECATED use get_cards_by_id_card_by_field>>
Deletes a specific sticker from a trello card. this endpoint allows you to remove a single sticker from a card by providing both the card’s unique identifier and the sticker’s unique identifier. it’s useful for cleaning up or reorganizing visual elements on a card. the operation is permanent and cannot be undone, so use it with caution. this endpoint should be used when you need to programmatically remove stickers from cards, such as in automation workflows or when bulk-updating card appearances.
Updates an existing trello card with new attributes or modifications. this endpoint allows you to change various properties of a card, including its status, description, due date, attachments, board and list placement, labels, and assigned members. use this when you need to modify a card’s details, move it between lists or boards, or update its metadata. the endpoint is versatile, allowing for partial updates, so you can specify only the fields you want to change. it’s particularly useful for automating workflows, syncing card data with external systems, or bulk updating cards based on certain criteria. note that some updates, like changing the board or list, may affect the card’s visibility and accessibility to team members.<<DEPRECATED use update_cards_by_id_card>>
Adds a custom sticker to a specific trello member’s profile. this endpoint allows you to upload and associate a unique image as a custom sticker for the given member. custom stickers can be used to personalize cards and enhance visual communication within trello boards. use this endpoint when you want to programmatically add new custom stickers to a member’s collection, which can then be applied to cards across their trello boards. note that there may be limitations on the number of custom stickers a member can have, and the file size and format of the sticker image may be restricted by trello’s policies.
Deletes a specific label from a trello board. this endpoint is used when you want to permanently remove a label that is no longer needed or relevant to your board’s organization. it’s particularly useful for cleaning up old or unused labels to maintain a streamlined and efficient labeling system. once deleted, the label will no longer be available for assigning to cards, and any cards previously tagged with this label will have the label removed. use this endpoint with caution, as the deletion is permanent and cannot be undone through the api.
Retrieves detailed information about a specific trello card using its unique identifier. this endpoint allows you to fetch comprehensive data about a single card, including its name, description, due date, members, labels, and other associated metadata. use this endpoint when you need to access or display the full details of a particular card within your application or workflow. it’s particularly useful for scenarios where you need to show card details, update card information, or sync card data with external systems. note that this endpoint only provides read access to the card data and does not allow modifications.<<DEPRECATED use get_cards_by_id_card>>
Creates a new session in trello, associating it with a specific board and setting the user’s status. this endpoint is used to initialize a user’s interaction with a trello board, enabling real-time updates and status tracking. it’s particularly useful for applications that need to manage user presence and activity within trello boards. the created session allows trello to send appropriate notifications and updates based on the user’s status. note that this endpoint doesn’t handle authentication itself; ensure proper authentication is in place before calling this endpoint.
This endpoint deletes a specific saved search for a trello member. saved searches allow users to quickly access frequently used search terms and filters within trello. this operation permanently removes the saved search from the member’s account, freeing up space and decluttering their saved searches list. use this endpoint when a user wants to remove an outdated or no longer needed saved search. it’s important to note that this action cannot be undone, so confirmation from the user before deletion is recommended. the endpoint requires both the member’s id and the specific saved search id to ensure precise targeting of the item to be deleted.
This endpoint allows for the deletion of a specific custom board background associated with a trello member. it removes the background image from the member’s available board backgrounds, making it no longer accessible for use on their boards. this operation is permanent and cannot be undone, so it should be used with caution. the endpoint is particularly useful for managing storage space or removing outdated or unwanted background options for a member. it requires both the member’s id and the specific board background id to ensure precise targeting of the background to be deleted.
Retrieves detailed information about a specific trello board. this endpoint allows you to fetch comprehensive data about a board, including its name, description, members, lists, and other associated metadata. use this endpoint when you need to access or display the current state and configuration of a particular board. it’s particularly useful for applications that need to sync board data, display board information, or perform operations based on the board’s current state. note that this endpoint only provides a read-only view of the board; it cannot be used to modify the board’s properties. the response will likely include all visible elements of the board, but may not include certain private or restricted information depending on the authentication level and permissions of the api key used.<<DEPRECATED use get_boards_by_id_board>>
Deletes a specific custom sticker associated with a trello member. this endpoint is used to permanently remove a custom sticker from a member’s collection, freeing up space in their custom sticker library. it should be used when a member no longer needs a particular custom sticker or wants to manage their sticker collection. once deleted, the custom sticker cannot be recovered, so use this endpoint with caution. this operation is only available for custom stickers within a paid trello workspace.
Retrieves the check item states for a specific trello card. this endpoint allows you to fetch the current status (e.g., complete or incomplete) of all checklist items associated with the given card. it’s useful for tracking the progress of tasks within a card or for syncing checklist data with external systems. the endpoint should be used when you need to monitor or update the completion status of checklist items for a particular card. note that this endpoint only provides the states of check items and does not return the full checklist or card details. to get comprehensive card information, you would need to use a separate endpoint.
Retrieves the list information for a specific card in trello. this endpoint allows you to determine which list a particular card belongs to on a trello board. it’s useful for understanding the current status or position of a task within a workflow. the endpoint should be used when you need to know the organizational context of a specific card, such as its current stage in a process or its categorization. it provides a quick way to locate a card within the board’s structure without having to fetch and search through all lists. note that this endpoint only returns information about the list containing the card and does not provide details about the card itself or other cards in the same list.
Retrieves the list of custom board backgrounds associated with a specific trello member. this endpoint allows you to fetch all personalized background images that the member has uploaded or created for use on their trello boards. it’s useful for applications that need to display or manage a member’s custom board background options. the endpoint returns details about each custom background, which may include image urls, dimensions, and other relevant metadata. use this when you need to access a member’s personal board customization options or integrate board background management into your application.
Retrieves the board information associated with a specific trello list. this endpoint allows you to fetch details about the board to which a particular list belongs. it’s useful when you need to understand the context or parent board of a list, especially in scenarios where you’re working with list ids and need to know their associated boards. this can be helpful for navigation, organization, or when you need to perform operations that require board-level information. the endpoint returns board details, which may include the board’s name, description, preferences, and other relevant metadata. use this when you have a list id and need to find out which board it’s on, or when you need to access board-level information starting from a list.
Retrieves a specific attachment from a trello card. this endpoint allows you to fetch detailed information about a single attachment associated with a particular card. it’s useful when you need to access or download files, documents, or other resources that have been added to a trello card. the endpoint requires both the card’s id and the attachment’s id to pinpoint the exact resource you’re looking for. use this when you need to retrieve or verify attachment details, such as file name, size, or download url, without fetching all attachments on the card.
Retrieves a list of boards that a specific trello member has been invited to but may not have joined yet. this endpoint is useful for tracking pending board invitations for a user, allowing them to see which boards they have access to join. it can be used to display a list of available boards to a user, helping them manage their trello workspace connections. the endpoint does not provide information about boards the member is already part of, focusing solely on outstanding invitations. use this when you need to show a user their pending board invitations or to check if a specific invitation exists for a member.
Retrieves a filtered list of cards associated with a specific trello member. this endpoint allows you to fetch cards based on their status (open, closed) or visibility to the member. it’s particularly useful for getting an overview of a member’s tasks or responsibilities across different boards. the endpoint can be used to gather data for personal task management, team progress tracking, or generating reports on member activities. note that the results are limited to cards the authenticated user has permission to view, and the response may be paginated for large sets of cards.
Retrieves a list of actions associated with a specific trello list. this endpoint allows you to fetch the activity history and changes made to a particular list, such as card movements, comments, or updates. use this endpoint when you need to track the timeline of events for a list or monitor recent activities. it’s particularly useful for auditing purposes or creating activity logs. the endpoint returns actions in chronological order, with the most recent actions first. note that the number of actions returned may be limited, and pagination might be required for lists with extensive history.
Retrieves a specific field of the board associated with a given trello card. this endpoint is useful when you need to access board-level information starting from a particular card, without fetching the entire board object. it allows for efficient retrieval of single board attributes, such as the board’s name, description, or url. this endpoint should be used when you have a card’s id and need to quickly obtain a specific piece of information about its parent board. it’s particularly helpful for applications that need to display or process board details in the context of card operations. note that this endpoint only provides read access to board fields and cannot be used to modify board information.
Retrieves the board associated with a specific checklist in trello. this endpoint allows you to fetch detailed information about the board that contains the specified checklist. it’s useful when you need to understand the broader context of a checklist, such as which project or workflow it belongs to. the endpoint returns board details, which may include the board’s name, description, members, and other relevant information. use this when you have a checklist id and need to know more about its parent board, particularly for tasks involving board-level operations or cross-referencing checklist data with board data.
Retrieves a specific field of information from all boards that a trello member has been invited to join. this endpoint is useful for gathering particular details about boards where the member has a pending invitation, without fetching all board data. it can be used to quickly check certain attributes across multiple invited boards, such as their names, ids, or last activity dates. this tool is particularly helpful when you need to analyze or display specific information about a member’s board invitations efficiently. note that this endpoint only provides data for boards with pending invitations and does not include boards where the member is already active.
Retrieves a specific field of a trello card. this endpoint allows you to fetch individual attributes of a card without retrieving the entire card object, which can be useful for targeted data retrieval and improved performance. it should be used when you need to access a particular piece of information about a card, such as its name, description, due date, or any other supported field. this tool is particularly helpful for checking specific card details or for integrations that need to monitor or sync certain card attributes. note that this endpoint will only return the value of the requested field; if you need multiple fields or the complete card data, you should use a different endpoint that returns the full card object.
Retrieves detailed information about a specific trello card using its unique identifier. this endpoint allows you to fetch comprehensive data about a single card, including its name, description, due date, members, labels, and other associated metadata. use this endpoint when you need to access or display the full details of a particular card within your application or workflow. it’s particularly useful for scenarios where you need to show card details, update card information, or sync card data with external systems. note that this endpoint only provides read access to the card data and does not allow modifications.
Retrieves the custom emojis associated with a specific trello member. this endpoint allows you to fetch all custom emojis that a particular member has created or has access to within their trello account. custom emojis are special images that can be used in comments, card descriptions, and other text fields in trello. this endpoint is useful when you need to display or list the available custom emojis for a member, or when integrating custom emoji functionality into a third-party application. note that this endpoint only retrieves the custom emojis and does not provide information about standard emojis available to all trello users.
Retrieves a list of members associated with a specific trello card. this endpoint allows you to fetch all users who are assigned to or involved with a particular card, providing valuable information for task management and collaboration. use this when you need to know who is responsible for or working on a specific card. the endpoint returns member details but does not modify any card information or memberships. it’s particularly useful for tracking task assignments, generating reports on card participation, or displaying member avatars alongside card information in a user interface.
Retrieves a specific field from the board associated with a given checklist in trello. this endpoint allows users to access granular information about a board linked to a particular checklist, which can be useful for various integration and automation scenarios. it provides a way to fetch individual board attributes without retrieving the entire board object, potentially improving efficiency for targeted data retrieval. the endpoint should be used when you need to access specific board details in the context of a checklist, but it will not provide information about the checklist itself or other board fields not specified in the request.
Retrieves the board information associated with a specific trello card. this endpoint allows you to fetch details about the parent board of a given card, providing context about where the card is located within your trello workspace. use this when you need to understand the broader organizational structure a card belongs to or when you want to access board-level information starting from a specific card. this is particularly useful for applications that need to navigate from card-level operations to board-level views or actions. note that this endpoint only returns information about the board and does not provide details about other cards or lists on that board.
Retrieves a list of organizations associated with a specific trello member, filtered by the given criteria. this endpoint is useful for obtaining information about a user’s organizational affiliations within trello, which can be valuable for user management, permissions setting, or displaying relevant workspaces. the filter parameter allows for narrowing down the results based on the member’s relationship to the organizations. this endpoint should be used when you need to gather information about a user’s organizational context within trello, but it will not provide detailed information about the organizations themselves beyond basic identifiers.
Retrieves a specific saved search associated with a trello member. this endpoint allows you to fetch the details of a particular saved search by providing both the member’s id and the saved search id. it’s useful for applications that need to display or manage a user’s saved searches within trello. the endpoint returns the full details of the saved search, which may include the search query, any filters applied, and other relevant metadata. use this endpoint when you need to access or display the specifics of a single saved search for a given trello user. note that this endpoint only retrieves the saved search information and does not execute the search itself.
Retrieves a specific field of a trello list. this endpoint allows you to fetch detailed information about a particular aspect of a list by providing the list’s unique identifier and the name of the field you want to retrieve. it’s useful when you need to access or verify a single piece of information about a list without retrieving all of its details. this endpoint should be used when you require quick access to a specific list attribute, such as its name, associated board id, or position. it’s important to note that this endpoint returns only the requested field’s value and not the entire list object. therefore, it’s not suitable for retrieving multiple fields simultaneously or for getting a comprehensive view of the list.
Retrieves a list of organizations associated with a specific trello member. this endpoint is useful for obtaining an overview of all the organizations a member belongs to, which can be helpful for managing user permissions, generating reports, or building user interfaces that display organization memberships. the endpoint returns basic information about each organization, likely including the organization’s id, name, and possibly the member’s role within it. it should be used when you need to gather information about a member’s organizational affiliations within trello. note that this endpoint does not provide detailed information about the organizations themselves; for that, you would need to use a separate endpoint specific to organization details.
Retrieves all saved searches for a specific trello member. this endpoint allows you to fetch the list of search queries that a member has saved for quick access within their trello account. it’s useful for applications that need to display or manage a user’s saved searches, enabling features like quick filtering of boards, cards, or other trello elements. the endpoint should be used when you need to access a member’s search preferences or want to implement functionality that leverages their saved search history. note that this endpoint only retrieves the saved searches and does not execute them; to perform an actual search, you would need to use a separate search endpoint with the retrieved query parameters.
Retrieves a specific field of the list associated with a given trello card. this endpoint allows you to fetch targeted information about the list containing a particular card without retrieving the entire list object. it’s useful when you need quick access to a single attribute of the list, such as its name or position on the board. this tool should be used when you have a card’s id and want to know a specific detail about the list it’s in. it’s particularly efficient for scenarios where you don’t need comprehensive list data. note that this endpoint only provides information about the list, not the card itself or other cards in the list.
Retrieves all tokens associated with a specific trello member. this endpoint allows you to fetch the authentication tokens that have been issued for a particular user, which can be useful for managing api access and auditing purposes. it returns a list of token objects, each representing an active token for the specified member. use this endpoint when you need to review or manage the api access granted to a user’s account. note that this endpoint does not provide the actual token values for security reasons, but rather metadata about the tokens such as their id, creation date, and associated app information.
Retrieves a list of organizations that a specific trello member has been invited to join but has not yet accepted or declined. this endpoint is useful for tracking pending organization invitations for a given user. it can be used to display a list of outstanding invitations, allowing the member to review and take action on them. the endpoint does not provide information about organizations the member has already joined or invitations that have been declined. use this endpoint when you need to fetch all pending organization invitations for a particular trello member, such as for notification purposes or to prompt the user to act on outstanding invitations.
Retrieves a specific field of information about organizations that a trello member has been invited to join but has not yet accepted. this endpoint is useful for gathering detailed information about pending organization invitations for a user, allowing applications to display relevant data or make decisions based on the invited organizations’ attributes. it provides a focused way to access organization data without fetching all details, which can be more efficient when only specific information is needed. the endpoint should be used when you need to access particular details about organizations a member has been invited to, rather than retrieving full organization objects or listing all invitations.
Retrieves a specific field of the trello board associated with a given list. this endpoint allows users to access board information through one of its lists, providing a way to navigate the trello hierarchy from list to board. it’s particularly useful when you have a list id and need to fetch details about the board it belongs to without knowing the board id directly. the endpoint returns only the requested field of the board, making it efficient for targeted data retrieval. however, it’s limited to one field per request, so multiple calls may be necessary to gather comprehensive board information.
Retrieves detailed information about a specific trello list using its unique identifier. this endpoint allows you to fetch the properties and metadata of a single list, such as its name, associated board, position on the board, and whether it’s archived. use this endpoint when you need to access or verify the current state and details of a particular list in your trello workflow. it’s particularly useful for applications that need to display list information, check list status, or prepare for operations on the list. note that this endpoint only provides information about the list itself and does not return the cards contained within the list.
Retrieves detailed information about a specific custom board background for a given trello member. this endpoint allows you to fetch the properties and metadata of a particular custom background that a member has associated with their account. it’s useful when you need to display or verify the details of a custom background, such as its dimensions, file type, or any custom attributes trello might associate with it. the endpoint should be used when you have both the member’s id and the specific board background id, typically in scenarios where you’re managing or displaying user-specific board customizations. note that this endpoint only provides information about the background and does not return the actual image file itself.
This endpoint retrieves a specific field of the board associated with a given trello notification. it allows users to fetch targeted information about the board context of a notification without retrieving all board details. use this when you need a particular board attribute in the context of a specific notification. note that it only returns a single field, not the entire board object.
Retrieves the custom board backgrounds associated with a specific trello member. this endpoint allows you to fetch all the personalized background images that a member has uploaded or selected for use on their trello boards. it’s useful for applications that need to display or manage a user’s board customization options. the endpoint returns an array of board background objects, likely including details such as image urls, colors, and other relevant attributes. use this when you need to access or display a member’s available board backgrounds, for example, when allowing a user to choose a background for a new board or when syncing customization settings across devices.
Retrieves a specific field of a trello notification. this endpoint allows you to fetch targeted information about a notification without retrieving the entire notification object. it’s useful when you need quick access to a particular attribute of a notification, such as its type, date, or associated data. the endpoint requires both the unique identifier of the notification and the name of the field you want to retrieve. it’s ideal for scenarios where bandwidth is a concern or when only a specific piece of notification data is needed. note that the response will contain only the requested field’s value, not the full notification object.
Retrieves detailed information about a specific checklist in trello using its unique identifier. this endpoint allows users to fetch the complete data of a checklist, including its name, items, completion status, and any other associated metadata. it’s particularly useful when you need to access or display the full contents of a checklist within your application. the endpoint should be used when you have the checklist’s id and require its current state or details. it does not modify the checklist and is ideal for read-only operations or before performing updates to ensure you have the latest data.
Retrieves the board associated with a specific trello notification. this endpoint allows you to fetch detailed information about the board where a notification-triggering action occurred. it’s particularly useful when you need to provide context or additional details about a notification, such as the board’s name, background, or other relevant attributes. use this endpoint when you want to quickly access the board related to a notification without having to make separate api calls. note that this endpoint only provides board information and does not include details about the notification itself or other board components like lists or cards.
Retrieves a list of members who have voted on a specific trello card. this endpoint is part of the voting power-up feature and is useful for tracking team preferences or decision-making processes within a project. it provides insight into which team members have participated in voting on a particular card, helping to gauge engagement and consensus. use this endpoint when you need to review voting participation for a card or analyze team involvement in decision-making processes. note that this endpoint only returns information about who voted, not the specific votes cast or voting results.
Retrieves detailed information about a specific trello notification. this endpoint allows you to fetch the full details of a single notification based on its unique identifier. use this when you need to access comprehensive information about a particular notification, such as its type, related board or card, creation time, and any associated data. this is particularly useful for displaying notification details in your application or for processing specific notifications as part of your workflow automation. the endpoint will only return data for the specified notification and does not provide a way to fetch multiple notifications in a single request.
Retrieves all cards within a specified trello list. this endpoint allows users to fetch detailed information about cards in a particular list, providing a comprehensive view of tasks or items within that list. it’s particularly useful for applications that need to synchronize trello data, build custom views of trello boards, or perform bulk operations on cards within a specific list. the endpoint returns an array of card objects, each containing details such as the card’s name, description, due date, and any custom fields. use this endpoint when you need to get an up-to-date snapshot of all cards in a list, but note that it doesn’t provide real-time updates or webhook functionality for card changes.
Retrieves a specific field of a member associated with a given trello notification. this endpoint is useful when you need to access detailed information about the member involved in a particular notification, such as the member who triggered the notification or the member who received it. it allows for granular data retrieval, fetching only the specified field rather than all member information. this can be particularly helpful when you need to quickly access a specific piece of member data in the context of a notification, without the overhead of retrieving all member details. the endpoint should be used when you have a notification id and need to extract a particular attribute of the related member. it will not provide information about the notification itself or other members not associated with the specified notification.
Retrieves all checklists associated with a specific trello card. this endpoint is useful for obtaining detailed information about the tasks and subtasks within a card, allowing users to track progress and manage workflows effectively. it should be used when you need to fetch the complete set of checklists for a particular card, such as when displaying card details or syncing card information with another system. the endpoint returns an array of checklist objects, each containing items that represent individual tasks or steps. note that this endpoint only provides checklist data and does not include other card details like comments or attachments. it’s particularly valuable for applications that need to monitor or update task progress within trello cards.
The getchecklistfield endpoint retrieves a specific attribute or field of a trello checklist. it allows users to fetch detailed information about a particular aspect of a checklist without retrieving the entire checklist object. this endpoint is useful when you need to access or verify a single piece of information about a checklist, such as its name, associated card id, or position. it should be used when you require only one specific detail about a checklist, rather than its complete data. note that this endpoint will not provide information about the check items within the checklist; it focuses solely on the checklist’s properties.
Retrieves a specific field of information about the member who created a particular notification in trello. this endpoint is useful when you need detailed information about the user responsible for generating a specific notification, without fetching their entire profile. it allows for efficient, targeted data retrieval, which can be particularly beneficial when building notification-centric features or conducting user activity analysis. the endpoint should be used when you have a notification id and need to access a specific attribute of its creator. it will not provide information about the notification itself or other members.
Retrieves the card information associated with a specific trello notification. this endpoint is useful when you need to access details about the card that triggered a particular notification. it allows you to fetch comprehensive information about the card, such as its title, description, members, labels, and other relevant data. use this endpoint when you want to display or process card information in the context of a notification, for example, to show users more details about an action that occurred on a card they’re watching. note that this endpoint only provides card data and does not include information about the notification itself or other related entities like boards or lists.
This endpoint retrieves a specific field from a list associated with a given trello notification. it allows users to access granular information about the list context of a notification, which can be useful for tracking changes or gathering specific details without fetching the entire list object. the endpoint should be used when you need to quickly access a particular attribute of a list that’s linked to a notification, such as its name, id, or status. it’s particularly efficient when you don’t need the full list data and want to minimize data transfer. however, it’s important to note that this endpoint is limited to retrieving a single field at a time, so multiple calls may be necessary if you need several fields from the same list.
Retrieves information about the member who created a specific trello notification. this endpoint is useful for obtaining details about the user responsible for triggering a particular notification, providing context to the notification’s origin. it should be used when you need to identify or get more information about the member behind a notification action. the endpoint focuses solely on the creator’s details and does not provide information about the notification content itself or other related data. keep in mind that accessing this information may be subject to permission settings and the user’s role within the trello board or organization.
Retrieves all stickers associated with a specific trello card. this endpoint allows you to fetch the visual elements (stickers) that have been added to a card for categorization, emphasis, or decoration purposes. it’s useful when you need to review or analyze the visual metadata of a card, such as identifying specific tags or markers represented by stickers. the endpoint returns an array of sticker objects, likely including details such as the sticker’s id, image url, and position on the card. use this when you need to inventory or process the stickers on a particular card, but note that it doesn’t modify the stickers or provide information about other card elements.
Retrieves a specific custom board background for a given trello member. this endpoint allows you to fetch detailed information about a particular board background associated with a member’s account. it’s useful when you need to display or use the properties of a specific custom background, such as its image url, dimensions, or any custom attributes. this endpoint should be used when you have both the member’s id and the specific board background id. it will not provide information about other board backgrounds or modify the background in any way.
Retrieves the member information associated with a specific trello notification. this endpoint allows you to get details about the user who is related to a particular notification, such as the member who created a card that triggered the notification. use this endpoint when you need to identify or gather information about the member involved in a specific trello notification event. it’s particularly useful for tracking user activities, auditing notification sources, or displaying member details alongside notification content in your application. note that this endpoint only provides member data directly linked to the specified notification and does not return the notification content itself or other board-wide member information.
Retrieves a filtered set of cards from a specific trello list. this endpoint allows you to fetch cards based on a given list id and apply a filter to narrow down the results. it’s particularly useful when you need to access a subset of cards within a list, such as all open cards or cards matching certain criteria. the endpoint should be used when you want to efficiently retrieve specific cards from a known list without fetching all cards and filtering them client-side. note that the exact filtering options available depend on the trello api’s supported filters, which are not fully specified in the given schema.
This endpoint retrieves a specific field of the organization associated with a given trello notification. it allows users to access detailed information about the organization context of a notification without fetching the entire organization object. this can be particularly useful when you need quick access to a single piece of organization data related to a notification, such as the organization’s name or description. the endpoint should be used when you have a notification id and need to extract a particular organization detail linked to that notification. it’s important to note that this endpoint will only return data for notifications that are associated with an organization; personal board notifications may not return any data.
Retrieves the organization information associated with a specific trello notification. this endpoint allows you to fetch details about the organization context in which a particular notification was generated. it’s useful when you need to understand the broader organizational scope of a notification, such as determining which workspace or team the notification is related to. the endpoint should be used when you have a notification id and need to retrieve the corresponding organization data. note that this endpoint only provides organization information and does not return details about the notification itself or other related entities like boards or cards.
Retrieves a specific custom emoji associated with a trello member. this endpoint allows you to fetch detailed information about a particular custom emoji that a member has added to their trello account. it’s useful when you need to access or display a specific custom emoji in your application, or when you want to verify the existence and details of a custom emoji for a given member. the endpoint requires both the member’s id and the custom emoji’s id to uniquely identify and retrieve the correct emoji. note that this endpoint only retrieves information about the emoji and does not modify or delete it.
Retrieves a specific field or attribute of a trello organization. this endpoint allows you to fetch targeted information about an organization without retrieving all of its details. it’s useful when you need a particular piece of data, such as the organization’s name, description, or website. the endpoint requires the organization’s unique identifier and the name of the field you want to retrieve. it’s efficient for quick lookups and can be used to verify or display specific organization information in integrations or automation workflows. however, it won’t return multiple fields in a single call, so for comprehensive organization data, you might need to use a different endpoint.
Retrieves the recent changes (deltas) for a specified trello organization. this endpoint is used to fetch updates or modifications made within the organization, such as changes to boards, lists, or cards. it’s particularly useful for keeping external systems in sync with trello data or for auditing purposes. the endpoint returns delta information, which may include creation, updates, or deletion of various elements within the organization. note that the specific format and content of the delta information are not detailed in the provided schema.
Retrieves detailed information about a specific sticker on a particular trello card. this endpoint allows you to fetch the properties of a single sticker, such as its image, position on the card, and any other metadata associated with it. it’s useful when you need to access or verify the details of a specific sticker, perhaps for display purposes or to confirm its current state. this tool should be used when precise information about an individual sticker is required, rather than for bulk retrieval of all stickers on a card. note that this endpoint does not modify the sticker; it only retrieves its current state.
Retrieves a list of actions performed within a specific trello organization. this endpoint allows you to fetch a comprehensive log of activities and changes made across all boards, lists, and cards within the organization. it’s particularly useful for auditing purposes, tracking team productivity, or monitoring recent changes. the actions returned may include card creations, list movements, comment additions, and other significant events. use this endpoint when you need a detailed history of organizational activities or want to analyze patterns in team workflows. note that the response may be paginated for large organizations with extensive action histories, and you might need to make multiple requests to retrieve the complete set of actions.
Retrieves a list of all memberships for a specified trello organization. this endpoint allows you to fetch detailed information about users who are members of the organization, including their roles and permissions. it’s particularly useful for organization administrators who need to manage team members, audit access levels, or gather data about the organization’s composition. the endpoint returns membership details for all users associated with the organization, regardless of their specific role or active status. note that this endpoint does not provide information about board-specific memberships or detailed user profiles; it focuses solely on organizational-level memberships.
Retrieves a list of boards that a specific trello member has starred. this endpoint allows you to fetch the favorite or most important boards for a given user, as indicated by their “star” status. it’s particularly useful for applications that need to prioritize or highlight a user’s preferred boards. the endpoint returns only the starred boards, not all boards the member has access to. use this when you need to quickly access a user’s most relevant or frequently used boards without fetching their entire board list.
Retrieves detailed information about a specific membership within a trello organization. this endpoint allows you to fetch the membership details of a particular user in a given organization, providing insights into their role, permissions, and other relevant information. it’s useful for auditing organization members, verifying a user’s status, or retrieving specific membership attributes. the endpoint requires both the organization id and the membership id to pinpoint the exact membership record. note that this endpoint only retrieves information and does not modify any data.
Retrieves all cards associated with a specific checklist in trello. this endpoint allows you to fetch the cards that contain the specified checklist, providing a way to see which tasks or items (represented by cards) are linked to a particular set of subtasks or criteria (represented by the checklist). it’s useful for tracking progress on complex tasks or viewing all cards that share a common checklist. the endpoint returns an array of card objects, each containing details about the card such as its id, name, description, and other relevant metadata. use this when you need to find all cards related to a specific checklist, which can be helpful for project management, task organization, or generating reports on task dependencies.
Retrieves a filtered list of members belonging to a specified trello organization. this endpoint allows you to fetch member information based on certain criteria, making it useful for managing team rosters, analyzing organization structure, or performing member-specific operations. the endpoint requires both the organization id and a filter parameter, enabling precise control over the returned member set. it’s particularly valuable when you need to access specific subsets of an organization’s membership, such as all active members or only administrators. however, it does not modify any data and should be used solely for retrieving member information. note that the exact filtering options and the structure of returned member objects are not specified in the schema, so refer to the latest trello api documentation for the most up-to-date details on available filters and response format.
Retrieves a list of actions performed by a specific trello member. this endpoint allows you to fetch a chronological history of activities such as creating cards, moving items between lists, adding comments, and other interactions within trello boards and cards. it’s useful for tracking a member’s contributions, auditing changes, or building activity feeds. the actions returned may be limited based on the member’s privacy settings and the permissions of the authenticated user making the request. note that this endpoint may not return all historical actions and might be subject to rate limiting for extensive action histories.
Retrieves all custom stickers associated with a specific trello member. this endpoint allows you to fetch the unique, personalized stickers that a member has created or uploaded for use on their trello cards. it’s particularly useful when you need to display or manage a member’s custom sticker collection. the endpoint returns a list of custom stickers, including their images and metadata. note that this only retrieves custom stickers, not the standard trello stickers available to all users. use this endpoint when you need to access a member’s personalized sticker set, such as for displaying in a sticker picker or for inventory management purposes.
Retrieves a specific field of a card associated with a given trello notification. this endpoint is useful when you need to access particular details of a card that triggered a notification, without fetching the entire card object. it can be used to quickly obtain relevant information for displaying in notification summaries or for processing notification-related actions. the endpoint is particularly valuable for applications that handle trello notifications and need to provide context about the associated cards. note that this endpoint only returns the requested field’s value, not the entire card object, which makes it efficient for targeted data retrieval but limited if you need comprehensive card information.
Retrieves all boards associated with a specific trello organization. this endpoint allows users to fetch a comprehensive list of boards within a given workspace, providing an overview of all projects and tasks managed by the organization. it’s particularly useful for administrators or team leads who need to monitor or manage multiple boards across their organization. the endpoint returns basic information about each board, such as its name, url, and id, enabling further actions or queries on individual boards if needed. use this when you need a high-level view of an organization’s project structure or when preparing to perform bulk operations on multiple boards within the same workspace.
Retrieves a list of members belonging to a specific trello organization. this endpoint allows you to fetch detailed information about all users who are part of the organization, including their roles and permissions. it’s particularly useful for organization administrators who need to manage team members, audit access, or gather information for reporting purposes. the endpoint returns member data such as usernames, full names, and membership status, but does not provide sensitive information like email addresses or personal account details. use this when you need a comprehensive overview of an organization’s membership or when integrating member management features into your application.
Retrieves all cards associated with a specific member within a trello organization. this endpoint allows you to fetch a comprehensive list of cards that a particular member is involved with in the context of a given organization. it’s useful for getting an overview of a member’s tasks or responsibilities across various boards within the organization. the endpoint returns card data without any sorting or filtering options, providing a complete picture of the member’s card assignments. use this when you need to audit a member’s workload, track their contributions, or gather data for reporting purposes within an organizational context.
Retrieves cards associated with a specific checklist in trello. this endpoint allows users to fetch cards that are linked to a particular checklist, providing a way to see all tasks or items related to a checklist across different cards or boards. the endpoint is useful for tracking progress on checklist items, identifying which cards are using a specific checklist, or gathering information for reporting purposes. it’s particularly helpful when managing complex projects with interrelated tasks spread across multiple cards. the endpoint supports filtering to customize the returned set of cards, allowing for more precise data retrieval based on the user’s needs.
Retrieves a list of members who have been invited to join a specific trello organization but have not yet accepted the invitation. this endpoint is useful for organization administrators to track pending invitations and manage membership. it provides information about invited users, which may include details such as their username, full name, and invitation status. use this endpoint when you need to review or audit the list of outstanding invitations for an organization. note that this endpoint only returns data about invited members; it does not include information about active members or provide functionality to send new invitations.
Retrieves a specific field of information for members who have been invited to join a trello organization. this endpoint is useful for getting targeted details about pending invitations without fetching all information about invited members. it can be used to check the status of invitations, gather contact information, or verify invitation details. the endpoint is particularly helpful when you need to audit or manage the invitation process for a trello organization. note that this endpoint only provides information about invited members who have not yet joined the organization; it does not include data about active members.
Retrieves detailed information about a specific trello token. this endpoint allows you to fetch the properties and permissions associated with a given token, which is crucial for understanding the level of access granted to an application or user. use this endpoint when you need to verify token validity, check its permissions, or gather metadata about the token. it’s particularly useful for auditing api access or troubleshooting authentication issues. note that this endpoint does not provide information about other tokens or allow modification of the token itself.
Searches for trello members based on the provided query string. this endpoint allows you to find users by their name, username, or email address, making it useful for user discovery and member management within trello. the search is performed across all accessible trello members, with optional filters for specific boards or organizations. use this endpoint when you need to locate trello users, verify member existence, or gather member information for collaboration purposes. the search results are paginated and can be limited to control the response size.
Retrieves a filtered list of boards associated with a specific trello organization. this endpoint allows users to fetch boards based on various criteria such as membership, status, visibility, and more. it’s particularly useful for getting an overview of boards within an organizational context or for finding specific types of boards (e.g., public boards, starred boards). the endpoint supports customization through the filter parameter, enabling precise queries to match user requirements. note that the response will only include boards that the authenticated user has permission to view within the specified organization.
Retrieves the display information for a specific trello notification. this endpoint allows you to fetch detailed data about how a notification should be presented to the user, including its content, associated card or board information, and any relevant formatting details. use this endpoint when you need to access the visual representation or formatted data of a particular notification, such as when building a custom notification display in your application or integrating trello notifications into another platform. the endpoint focuses solely on display-related data and does not modify the notification’s read status or provide extensive metadata about the notification itself.
Establishes a websocket connection to receive real-time updates from trello. this endpoint allows clients to maintain an open connection for receiving push notifications about changes to boards, lists, cards, and other trello objects without the need for constant polling. it’s particularly useful for applications that need to stay synchronized with trello in real-time. the connection provides a stream of events, which may include updates to boards, creation of new cards, or changes in list order. note that this endpoint doesn’t accept any parameters, as it’s primarily used to initiate the websocket handshake.
Retrieves a specific field of information for a given trello authentication token. this endpoint allows developers to access granular details about a token, which can be useful for token management, verification, or debugging purposes. it provides a way to check individual attributes of a token without fetching all associated information. the endpoint should be used when specific token-related data is needed, rather than full token details. note that this endpoint does not modify the token in any way; it only retrieves information.
Retrieves the details of a specific custom sticker associated with a trello member. this endpoint allows you to fetch information about a particular custom sticker, such as its image url, dimensions, and any other metadata associated with it. it’s useful when you need to display or manipulate a specific custom sticker in your application. the endpoint requires both the member’s id and the custom sticker’s id to uniquely identify the requested resource. note that this endpoint only provides information about the sticker itself and does not include data about its usage on cards or boards.
Retrieves a specific field of information for a trello member associated with the given api token. this endpoint allows for granular access to member data, enabling the retrieval of individual attributes rather than the entire member object. it’s particularly useful when you need to quickly fetch a single piece of information about a member, such as their username or email, without the overhead of retrieving all member details. the endpoint should be used when precise, field-specific member information is required, and can help in reducing data transfer and processing when only particular member attributes are needed. note that the available fields and the information returned may depend on the permissions associated with the provided token and the privacy settings of the member in question.
Retrieves detailed information about a specific board star for a given trello member. a board star represents a member’s favorite or frequently accessed board. this endpoint allows you to fetch the properties of a particular board star, such as the associated board, its position in the member’s star list, and when it was created or last modified. use this endpoint when you need to access or verify the details of a specific board star for a member, for example, to check if a board is still starred or to retrieve its current position in the member’s favorites. this endpoint is read-only and does not modify any data.
Retrieves all checkitems associated with a specific checklist in trello. this endpoint allows you to fetch the complete list of items within a given checklist, providing details such as the item’s name, state (complete or incomplete), and position within the checklist. use this endpoint when you need to review or process all tasks within a particular checklist, such as for progress tracking or task management. it’s particularly useful for applications that need to sync or display trello checklist data. note that this endpoint only retrieves existing checkitems and does not create, update, or delete them.
Retrieves all webhooks associated with a specific trello api token. this endpoint allows developers to list and monitor active webhooks for a particular trello integration or application. it’s useful for managing webhook subscriptions, verifying active notifications, and troubleshooting webhook-related issues. the endpoint returns details about each webhook, likely including their callback urls, target models, and current status. use this when you need to audit or manage the webhooks tied to a specific trello api token.
Retrieves detailed information about the trello member associated with the provided api token. this endpoint allows you to access the profile data of the authenticated user, including their username, full name, initials, and other relevant account details. it’s particularly useful when you need to verify the identity of the token owner or gather user-specific information for personalization purposes. the endpoint should be used when you need to retrieve up-to-date information about the authenticated trello user. note that this endpoint only provides information about the member linked to the given token and does not offer data about other trello users or board members.
The searchtrello endpoint allows users to perform a comprehensive search across their trello workspace, including boards, cards, and lists. it’s designed to help users quickly find specific items or information within their trello ecosystem. this endpoint is particularly useful when you need to locate content across multiple boards or when you’re unsure which board contains the information you’re seeking. the search functionality is versatile, matching keywords in titles, descriptions, and other text fields of trello objects. while it provides a powerful way to find information, it’s important to note that the search results are limited to the user’s accessible trello content and may not include recently created or modified items due to indexing delays.
Retrieves detailed information about a specific trello webhook associated with the given token. this endpoint allows developers to fetch the current state and configuration of a webhook, including its callback url, the model it’s watching (e.g., board, list, or card), and its active status. it’s particularly useful for verifying webhook settings, troubleshooting notification issues, or auditing webhook configurations. the endpoint should be used when you need to inspect or confirm the details of an existing webhook. it does not modify the webhook or create new ones, and it won’t return information about other webhooks associated with the token.
Retrieves detailed information about a specific webhook in trello. this endpoint allows you to fetch the current configuration and status of a webhook, including its callback url, the model it’s monitoring, and its active status. use this endpoint when you need to verify a webhook’s settings, check its status, or gather information for webhook management. it’s particularly useful for troubleshooting webhook issues or auditing your webhook configurations. the endpoint returns the full webhook object but does not provide information about past notifications sent through this webhook.
Retrieves all boards associated with a specific trello member. this endpoint allows you to fetch a comprehensive list of boards that the member has access to, including boards they own, are members of, or have been invited to. it’s particularly useful for applications that need to display or work with a user’s trello boards, such as for data synchronization, board management, or creating board-related features. the response typically includes details like board ids, names, and other metadata. use this endpoint when you need to get an overview of a member’s trello workspace or when implementing board selection features in your application. note that it only provides board-level information and does not include details about lists or cards within the boards.
Retrieves the entities associated with a specific trello notification. this endpoint allows you to fetch detailed information about the objects (such as boards, lists, cards, or members) that are related to or affected by a particular notification. it’s useful when you need to gather more context about a notification or update your application’s state based on the notification details. the endpoint should be used when you have a notification id and need to know what trello entities are involved in that notification. it will not provide information about notifications themselves, only the related entities.
Retrieves detailed information about a specific check item within a particular checklist in trello. this endpoint is used when you need to access the properties of an individual task or subtask represented by a check item, such as its name, completion status, or position within the checklist. it’s particularly useful for applications that need to display or process individual checklist items, for example, to show task progress or to update task details in an external system. this operation only fetches data and does not modify the check item or checklist. note that you must have appropriate permissions to access the specified checklist and its items.
Retrieves the list associated with a specific trello notification. this endpoint allows you to fetch details about the list that is linked to a particular notification, providing context for the notification event. use this endpoint when you need to access information about the list where an action triggering a notification occurred. it’s particularly useful for understanding the broader context of a notification, such as which list a card was moved to or where a comment was added. the endpoint returns data specific to the list and does not provide the full notification details or board information. keep in mind that access to this data may depend on the user’s permissions within the trello workspace.
Retrieves detailed information about a specific trello label using its unique identifier. this endpoint allows you to fetch the properties of a label, such as its name, color, and associated board. use this when you need to access or verify the details of a particular label within your trello workflow. the endpoint returns only the data for the specified label and does not provide information about other labels or the board structure. it’s particularly useful for applications that need to display or process individual label information.
Retrieves notifications for a specific trello member. this endpoint allows you to fetch all notifications associated with the given member, including alerts about new comments, card movements, mentions, and other board activities. use this endpoint when you need to display or process a member’s recent notifications, such as for creating a notification center or syncing member activities across platforms. the endpoint returns notifications in reverse chronological order, with the most recent notifications first. note that this endpoint may be subject to rate limiting and pagination for members with a large number of notifications.
The getmemberfield endpoint retrieves a specific attribute or property of a trello member. it allows you to fetch granular information about a user without retrieving their entire profile. this endpoint is particularly useful when you need only a single piece of information about a member, such as their full name, username, or a custom field value. it can be used to efficiently update or display specific member details in your application. however, it’s important to note that this endpoint will only return the value of the requested field and not provide any additional context or related information about the member.
Retrieves a specific field of a board associated with a given label in trello. this endpoint is useful when you need to access particular information about a board that is linked to a certain label, without fetching all board data. it can be used for quick lookups of board properties based on label associations, which is helpful for organizing and filtering board information. the endpoint is particularly efficient when you only need one piece of information about the board, rather than its entire data structure. however, it’s important to note that this endpoint will only return data for boards that are actually associated with the specified label; if no such association exists, the response may be empty or return an error.
Retrieves detailed information about the trello board associated with a specific label. this endpoint allows you to find out which board a particular label belongs to, which is useful for organizing and managing labels across multiple boards. use this when you need to trace a label back to its source board or when you want to understand the context of a label within the broader trello workspace. the endpoint returns comprehensive board data, including its name, url, members, and other relevant details. it’s particularly helpful for applications that need to manage or analyze label usage across different boards in a trello workspace.
Retrieves detailed information about a specific trello type using its unique identifier. this endpoint allows developers to fetch the characteristics and properties of various trello object types, such as boards, lists, or cards. it’s useful when you need to understand the structure or capabilities of a particular trello type, which can be essential for working with trello’s data model or implementing type-specific features in your application. the endpoint returns only the type information and does not provide instance-specific data or content related to individual trello objects.
Retrieves filtered notifications for a specific trello member. this endpoint allows users to fetch notifications based on a specified filter, enabling targeted information retrieval about updates, changes, or activities relevant to the member. it’s particularly useful for staying informed about specific aspects of trello boards, lists, or cards that the member is involved with. the endpoint should be used when needing to access a member’s notifications with custom filtering, but it won’t provide real-time updates or modify the notification status.
Retrieves a list of all changes (deltas) made by a specific trello member. this endpoint allows you to track the history of updates and modifications a particular user has made across trello boards, lists, and cards they have access to. it’s useful for auditing user activity, understanding workflow patterns, or syncing changes with external systems. the endpoint returns a chronological list of delta objects, each representing a distinct change made by the member. it should be used when you need a comprehensive view of a user’s actions within trello. note that this endpoint may not provide real-time updates and there might be a slight delay in reflecting the most recent changes.
Retrieves a filtered list of boards associated with a specific trello member. this endpoint allows you to fetch boards based on various criteria such as their status (open, closed), visibility (public), organizational association, or member’s relationship to the board (starred, invited). it’s particularly useful for applications that need to display or manage a subset of a member’s boards, enabling more focused and efficient data retrieval. the endpoint requires the member’s unique identifier and a filter parameter to customize the query. it should be used when you need to access or display a specific category of boards for a given trello user, rather than fetching all boards indiscriminately.
Retrieves all cards associated with a specific trello member across all boards they have access to. this endpoint is useful for getting a comprehensive view of a member’s tasks and responsibilities, regardless of which boards the cards are on. it can be used to create personal task lists, track workload, or analyze a member’s contribution across multiple projects. the endpoint returns card details such as title, description, due dates, and board/list information, but does not include comments or attachments. use this when you need to aggregate all of a member’s cards in one api call, rather than fetching cards board by board.
Retrieves detailed information about a specific trello member. this endpoint allows you to access a member’s profile data, including their username, full name, initials, avatar, and other public information associated with their trello account. it’s useful when you need to display member details in your application or verify a member’s identity. the endpoint provides read-only access to member information and should be used when you require up-to-date data about a particular trello user. note that this endpoint may not return sensitive or private information, and the level of detail in the response may depend on the authentication and permissions of the requesting user.
Retrieves detailed information about a specific trello organization. this endpoint allows you to fetch comprehensive data about an organization, including its name, description, members, boards, and other relevant attributes. use this endpoint when you need to access or display organization-level information within your application or workflow. it’s particularly useful for scenarios where you need to verify organization details, list associated boards, or manage organization-wide settings. note that this endpoint only provides read access to the organization data and does not allow modifications.
Updates the permission level preference for a specific trello board. this endpoint allows you to change the visibility of a board between private and public settings. use this when you need to modify the access control of a board, either to restrict access to invited members only (private) or to make it visible to anyone with the link (public). this operation is particularly useful when the collaboration needs of a project change, requiring either increased privacy or broader visibility. note that changing a board to public may have significant implications for data visibility and should be done with caution.
Updates the name of the purple label on a specific trello board. this endpoint allows you to customize the purple label’s name to better fit your project’s needs or organizational system. use this when you want to change how the purple label is displayed across all cards on a particular board. this action affects only the purple label and does not modify other color labels or any other board properties. the new label name will be immediately reflected on all cards using the purple label on the specified board.
Retrieves all cards within a specified trello list. this endpoint allows users to fetch detailed information about cards in a particular list, providing a comprehensive view of tasks or items within that list. it’s particularly useful for applications that need to synchronize trello data, build custom views of trello boards, or perform bulk operations on cards within a specific list. the endpoint returns an array of card objects, each containing details such as the card’s name, description, due date, and any custom fields. use this endpoint when you need to get an up-to-date snapshot of all cards in a list, but note that it doesn’t provide real-time updates or webhook functionality for card changes.<<DEPRECATED use get_lists_cards_by_id_list>>
Retrieves a filtered list of boards associated with a specific trello member. this endpoint allows you to fetch boards based on various criteria such as their status (open, closed), visibility (public), organizational association, or member’s relationship to the board (starred, invited). it’s particularly useful for applications that need to display or manage a subset of a member’s boards, enabling more focused and efficient data retrieval. the endpoint requires the member’s unique identifier and a filter parameter to customize the query. it should be used when you need to access or display a specific category of boards for a given trello user, rather than fetching all boards indiscriminately.<<DEPRECATED use get_members_boards_by_id_member_by_filter>>
Updates the invitation preferences for a specific trello board. this endpoint allows you to control who can invite new members to the board by setting the ‘value’ parameter to either ‘admins’ or ‘members’. use this when you need to restrict or expand invitation privileges on a board. for example, set it to ‘admins’ to limit invitations to board administrators only, or ‘members’ to allow all board members to invite others. this setting affects the entire board and may impact team collaboration dynamics.
Retrieves detailed information about a specific trello list using its unique identifier. this endpoint allows you to fetch the properties and metadata of a single list, such as its name, associated board, position on the board, and whether it’s archived. use this endpoint when you need to access or verify the current state and details of a particular list in your trello workflow. it’s particularly useful for applications that need to display list information, check list status, or prepare for operations on the list. note that this endpoint only provides information about the list itself and does not return the cards contained within the list.<<DEPRECATED use get_lists_by_id_list>>
Creates a new list within a specified trello board. this endpoint allows users to add a custom list to their board, optionally copying from an existing list, setting its position, and defining its initial state. it’s particularly useful for organizing tasks, creating new workflow stages, or expanding board structure. the new list can be created open or closed, and the creating user can choose to subscribe to it for notifications. this tool should be used when setting up new projects, restructuring workflows, or expanding existing boards. it doesn’t modify existing lists or move cards between lists.<<DEPRECATED use add_lists>>
Deletes a specific check item from a checklist within a trello card. this endpoint allows for the removal of individual tasks or items from a checklist, helping to manage and organize the progress of a card. it should be used when a task is no longer relevant, has been completed and needs to be removed, or was added by mistake. the operation is permanent and cannot be undone through the api, so it should be used with caution. this endpoint is particularly useful for automating task management workflows or cleaning up completed items in a checklist.
Updates the attributes of a specific sticker on a trello card. this endpoint allows you to modify various properties of an existing sticker, including its image, position, rotation, and layer order. use this when you need to adjust the appearance or layout of stickers on a card, such as repositioning, changing the image, or altering the stacking order. the endpoint requires the unique identifiers for both the card and the sticker. it’s important to note that while some parameters are typed as strings, they may represent numeric values (e.g., for positioning or rotation). this endpoint is particularly useful for fine-tuning the visual organization of card information in trello boards.
This endpoint allows users to update the subscription status for a specific trello card. by subscribing to a card, users can receive notifications about any changes or updates made to that card, such as comments, attachments, or movements between lists. this is particularly useful for staying informed about important tasks or collaborating effectively with team members. the endpoint should be used when a user wants to start or stop receiving notifications for a particular card. it’s important to note that this endpoint only toggles the subscription status and does not affect the card’s content or position within a board or list.
Retrieves all boards associated with a specific trello member. this endpoint allows you to fetch a comprehensive list of boards that the member has access to, including boards they own, are members of, or have been invited to. it’s particularly useful for applications that need to display or work with a user’s trello boards, such as for data synchronization, board management, or creating board-related features. the response typically includes details like board ids, names, and other metadata. use this endpoint when you need to get an overview of a member’s trello workspace or when implementing board selection features in your application. note that it only provides board-level information and does not include details about lists or cards within the boards.<<DEPRECATED use get_members_boards_by_id_member>>
Updates the position of a specific trello card within its current list. this endpoint allows you to move a card to the top, bottom, or a specific position in its list, helping to reorganize tasks and priorities. use this when you need to change the order of cards in a list without changing the list itself. the new position is specified using either keywords (‘top’, ‘bottom’) or a numeric value, providing flexibility in card arrangement. this operation is particularly useful for reordering tasks, adjusting priorities, or maintaining a specific workflow sequence within a trello board.
Retrieves the board information associated with a specific trello list. this endpoint allows you to fetch details about the board to which a particular list belongs. it’s useful when you need to understand the context or parent board of a list, especially in scenarios where you’re working with list ids and need to know their associated boards. this can be helpful for navigation, organization, or when you need to perform operations that require board-level information. the endpoint returns board details, which may include the board’s name, description, preferences, and other relevant metadata. use this when you have a list id and need to find out which board it’s on, or when you need to access board-level information starting from a list.<<DEPRECATED use get_lists_board_by_id_list>>
Updates the orange label name for a specific trello board. this endpoint allows you to customize the name of the orange label, which can be used to categorize and prioritize cards on the board. the new label name can be any string up to 16384 characters, including an empty string to remove the current name. use this when you need to modify the orange label’s meaning or purpose for a particular board, enhancing your team’s organization and workflow. note that this only updates the name of the orange label and does not affect any cards currently using this label.
This endpoint allows you to update the “selfjoin” preference for a specific trello board. the “selfjoin” preference determines whether users can join the board on their own or if they need an invitation. when set to ‘true’, users can join the board without an invitation, while ‘false’ requires an invitation from a board admin. this is particularly useful for managing access control and collaboration settings on your trello boards. use this endpoint when you need to change the board’s accessibility, either opening it up for self-joining or restricting access to invite-only.
Retrieves a specific field of a trello webhook. this endpoint allows you to fetch individual pieces of information about a webhook without retrieving its entire data structure. it’s useful for quickly checking or verifying specific webhook properties, such as its callback url, associated model id, or active status. the endpoint should be used when you need to access or validate a particular attribute of a webhook without the overhead of fetching all of its details. note that this endpoint doesn’t modify the webhook; it only retrieves information.
Updates the “show sidebar board actions” preference for a specific trello board. this endpoint allows users to customize their board view by choosing whether to display or hide board actions in the sidebar. it’s particularly useful for managing the visual clutter on a board, especially for boards with high activity. the preference is user-specific, meaning each board member can have their own setting without affecting others. use this endpoint when a user wants to change their personal view of the board’s sidebar actions.
Updates the closed status of a specific trello list. this endpoint allows you to close or reopen a list within a trello board by setting its ‘closed’ attribute. use this when you need to archive a list (by closing it) or restore a previously closed list (by reopening it). this action helps in organizing and managing the visibility of lists on a trello board. note that closing a list doesn’t delete it or its cards; it simply hides the list from the main board view. closed lists can be viewed in the board menu and can be reopened at any time.
Updates the attributes of an existing trello list identified by its unique id. this endpoint allows for modifying various aspects of a list, including its name, position on the board, closed status, board association, and subscription status. it can also be used to copy content from another list. this tool is particularly useful for reorganizing boards, managing list visibility, and maintaining up-to-date list information. it provides granular control over list properties, allowing for partial updates where only specified attributes are modified.
Updates the position of a specific check item within a checklist on a trello card. this endpoint allows you to reorder check items by moving them to the top, bottom, or a specific position within the checklist. it’s useful for prioritizing tasks or reorganizing workflow steps. the update is applied immediately, affecting the order of items as seen by all users with access to the card. use this when you need to change the order of tasks in a checklist without modifying their content or completion status.
Updates the position of a specific trello list within its board. this endpoint allows you to reorder lists by moving them to the top, bottom, or a specific position on the board. it’s useful for reorganizing workflows, prioritizing certain lists, or maintaining a specific order of task stages. the new position is specified using the ‘value’ parameter, which accepts ‘top’, ‘bottom’, or a positive number as a string. note that this endpoint only changes the list’s position and does not modify any other attributes of the list or its contents.
This endpoint updates the board association and position of a specific trello list. it allows you to move a list from one board to another and set its position on the new board. this is particularly useful for reorganizing workflows, transferring task lists between projects, or restructuring boards. the endpoint requires the list id, the new board id, and optionally, the desired position on the new board. it’s important to note that this operation can significantly impact the organization of tasks and should be used carefully, especially in collaborative environments.
Updates the user’s preference for showing or hiding the sidebar on a specific trello board. this endpoint allows users to customize their board view by toggling the sidebar visibility. it should be used when a user wants to change their personal sidebar display preference for a particular board. the change only affects the current user’s view and does not impact other team members’ preferences. this tool is useful for users who want to maximize their workspace or prefer a cleaner board interface.
This endpoint allows you to update the name of a specific trello list. it’s used when you need to rename a list, perhaps due to changes in project scope, team reorganization, or simply to correct a typo. the endpoint accepts the list’s unique identifier and the new name as parameters. it’s important to note that while this operation changes the list’s name, it doesn’t affect the cards within the list or its position on the board. use this endpoint when you need to quickly update a list’s name without making any other changes to its contents or location.
Updates a specific check item within a checklist on a trello card. this endpoint allows for modifying various attributes of a check item, including its name, position, completion state, and even moving it to a different checklist on the same card. it’s useful for task management and progress tracking within trello cards. the endpoint requires the ids of the card, current checklist, and check item to be updated, which should be provided in the url path. only the attributes that need to be changed should be included in the request body, allowing for partial updates.
This endpoint allows you to update the attributes of an existing trello label. it can be used to modify the color, name, or board association of a label. the endpoint is particularly useful when you need to reorganize your trello boards, refine your labeling system, or simply make changes to existing labels. you can update any combination of the label’s color, name, or board association in a single request. note that all parameters are optional, allowing for partial updates. if a parameter is not included in the request, that attribute of the label will remain unchanged. this endpoint should not be used to create new labels or to delete existing ones, as separate endpoints exist for those operations.
Updates the board of a trello card, effectively moving the card to a different board and list. this endpoint is used when you need to transfer a task or item (represented by a card) from one project or workflow (board) to another. it allows for reorganizing work across different contexts while maintaining the task’s details. the operation requires specifying both the target board and the specific list within that board where the card should be placed. this ensures that the card is properly categorized in its new location. use this endpoint when you need to shift priorities, reassign tasks to different teams, or reorganize your workflow structure. note that moving a card to a new board may affect integrations or automations tied to the original board, so use with caution in automated workflows.
Updates the subscription status of a specified trello list. this endpoint allows users to subscribe to or unsubscribe from a list, controlling whether they receive notifications about changes to that list. it’s useful for managing notification preferences on a per-list basis, helping users stay informed about relevant updates while avoiding unnecessary notifications. the endpoint should be used when a user wants to change their subscription status for a specific list, either to start receiving updates or to stop receiving them.
Deletes a specific custom board background for a trello member. this endpoint allows you to remove a personalized background image that a member has previously uploaded or set for their trello boards. use this when a member wants to remove a custom background from their available options. the deletion is permanent and cannot be undone, so it should be used with caution. this operation only affects the specified background for the given member and does not impact other members or default trello backgrounds.
Updates the name or text associated with the red label on a specific trello board. this endpoint allows users to customize the red label’s text to better categorize and organize cards on their board. it’s particularly useful when you want to give more meaningful names to color-coded labels, enhancing visual organization and filtering capabilities. the update is applied immediately, affecting all cards that use the red label on the specified board. this endpoint should be used when you need to change the red label’s text without altering its color or creating a new label. note that this operation only affects the red label and does not impact other color labels on the board.
This endpoint updates the name of a specific check item within a checklist on a trello card. it allows users to rename individual tasks or items in their checklists, providing better organization and clarity for their project management. the endpoint requires the unique identifiers for the card, checklist, and check item, ensuring precise targeting of the item to be renamed. it’s useful for maintaining up-to-date and accurate task descriptions within trello boards, especially when project requirements or task details change over time.
This endpoint updates the name of the yellow label on a specific trello board. it allows users to customize the yellow label’s text to better categorize and organize their cards. the endpoint should be used when you need to change the display text for the yellow label on a particular board, either to give it a more meaningful name or to remove its current name. it’s important to note that this operation only affects the yellow label and doesn’t modify other color labels on the board. the new label name can be up to 16384 characters long, providing flexibility for detailed labeling, but it can also be set to an empty string to remove the current name.
Updates the cover image of a specific trello card using an existing attachment. this endpoint allows you to change the visual appearance of a card by setting one of its attachments as the cover or removing the cover entirely. use this when you want to highlight important information or make a card more visually distinctive within a trello board. the cover image can help team members quickly identify and prioritize cards. note that this operation only works with attachments that already exist on the card; it cannot add new attachments or use images not associated with the card.
Updates the avatar source for a specific trello member. this endpoint allows you to change how a member’s avatar is displayed by specifying the source of the avatar image. it’s useful for customizing a member’s profile appearance or removing an existing avatar. the endpoint should be used when you need to programmatically manage a member’s avatar settings, such as during user onboarding or profile updates. note that setting the value to ‘upload’ doesn’t actually upload a new image; it only indicates that a custom upload should be used if available. to upload a new avatar image, you would need to use a separate endpoint (not specified in this schema).
Updates the bio of a specified trello member. this endpoint allows you to modify the personal or professional description associated with a member’s profile. it’s particularly useful for maintaining up-to-date information about team members within a trello workspace. the bio can be used to provide context about a member’s role, expertise, or any other relevant information that helps in team collaboration. this endpoint should be used when there’s a need to change or refresh a member’s bio information. note that while the bio can be set to an empty string, it has a maximum length of 16,384 characters, allowing for quite detailed descriptions if needed.
This endpoint updates the board associated with a specific board star for a trello member. it allows you to change which board a member has starred by providing a new board id. this is useful for reorganizing a member’s starred boards or correcting mistakenly starred boards. the endpoint takes the member id and board star id as path parameters, and requires the new board id in the request body. use this when a user wants to move their star from one board to another without removing and re-adding the star. note that this operation doesn’t create new board stars or affect the member’s permissions on either the old or new board; it only updates the existing star’s board association.
Retrieves detailed information about the trello member associated with the provided api token. this endpoint allows you to access the profile data of the authenticated user, including their username, full name, initials, and other relevant account details. it’s particularly useful when you need to verify the identity of the token owner or gather user-specific information for personalization purposes. the endpoint should be used when you need to retrieve up-to-date information about the authenticated trello user. note that this endpoint only provides information about the member linked to the given token and does not offer data about other trello users or board members.<<DEPRECATED use get_tokens_member_by_token>>
Updates the members of a specific trello card by adding a new member. this endpoint allows you to assign a user to a card, which is essential for task allocation and team collaboration within trello boards. use this when you need to add a team member to a specific task or card in your trello workflow. the endpoint accepts a single member id at a time, so multiple calls may be necessary to add several members to the same card. note that this operation adds a member to the card’s existing member list; it does not replace or remove other members already assigned to the card.
Updates the list assignment of a specific trello card. this endpoint allows you to move a card from one list to another within the same board. it’s particularly useful for updating the status or progress of a task represented by the card. the operation is idempotent, meaning that moving a card to its current list will not cause any changes. this endpoint should be used when you need to programmatically update the position of a card in your trello workflow. it’s important to note that this operation only changes the list assignment and does not modify any other attributes of the card.
The searchtrello endpoint allows users to perform a comprehensive search across their trello workspace, including boards, cards, and lists. it’s designed to help users quickly find specific items or information within their trello ecosystem. this endpoint is particularly useful when you need to locate content across multiple boards or when you’re unsure which board contains the information you’re seeking. the search functionality is versatile, matching keywords in titles, descriptions, and other text fields of trello objects. while it provides a powerful way to find information, it’s important to note that the search results are limited to the user’s accessible trello content and may not include recently created or modified items due to indexing delays.<<DEPRECATED use get_search>>
Updates the attributes of a specific board star for a trello member. this endpoint allows you to modify which board is starred or adjust the position of the star in the member’s list of starred boards. use this when a user wants to change their board star preferences, such as re-ordering their starred boards or starring a different board in place of an existing star. the endpoint requires the member’s id and the specific board star id to be updated. you can change the associated board by providing a new board id and adjust the star’s position using the ‘pos’ parameter. this operation directly modifies the user’s board star settings, so use it judiciously based on user intent.
This endpoint allows you to update the color of a specific trello label. it is used when you need to change the visual appearance of a label on trello cards and boards. the endpoint takes the label id as a path parameter and accepts a json payload with the new color value. you can use this to categorize or prioritize cards more effectively by adjusting their label colors. it’s important to note that setting the color to null will remove the color from the label, essentially making it a text-only label. this endpoint should be used for single label color updates; for bulk updates, consider using batch api calls if available.
Updates the position of a specific board star for a trello member. this endpoint allows you to change the order of starred boards in a member’s list of favorites. use this when a member wants to reorganize their starred boards, prioritizing certain boards by moving them up or down in the list. the position can be set to predefined values like ‘top’ or ‘bottom’, or a specific numerical position. this operation only affects the order of starred boards for the specified member and does not impact the board itself or its visibility to other members.
Updates the attributes of a specified trello member. this endpoint allows modification of various profile settings and preferences for a user, including their avatar source, biography, full name, initials, color blind mode, locale, notification frequency, and username. it’s particularly useful for allowing users to customize their trello experience or for administrators to manage user profiles. the endpoint requires the member’s id and accepts multiple optional parameters to update different aspects of the member’s profile. note that some attributes, like username, have specific constraints and changing them may affect how the user interacts with or is identified within trello.
Updates the user’s preference for showing or hiding sidebar members on a specific trello board. this endpoint allows users to customize their view of the board by controlling the visibility of the member list in the sidebar. it should be used when a user wants to change their personal setting for displaying board members. this preference is specific to the authenticated user and does not affect other board members’ views. the change takes effect immediately and persists across sessions until changed again.
Updates the attributes of a specific membership for a trello board. this endpoint allows you to modify a user’s role on a board or retrieve specific member information. it’s particularly useful for changing a member’s permissions or accessing detailed member data within the context of a board. the endpoint requires the board id and membership id to be specified in the url path. use this when you need to promote or demote a user’s role on a board, or when you need to fetch customized member information. note that this endpoint doesn’t add or remove members from a board; it only modifies existing memberships.
Updates the name of a specific trello board. this endpoint allows you to change the title of an existing board, which is useful for renaming projects, updating team workspaces, or refining board organization. it should be used when you need to modify the name of a board without altering its content or structure. the endpoint requires the board’s unique identifier (idboard) in the url path and accepts a new name value in the request body. note that this operation only affects the board’s name and does not impact its members, lists, or cards.
Updates the attributes of a specific board background for a trello member. this endpoint allows customization of a member’s board background, including its brightness, image file, and tiling option. use this when a user wants to modify the visual appearance of their trello board background. the endpoint is particularly useful for enhancing the user experience by allowing personalized board aesthetics. note that this operation modifies an existing board background and does not create a new one. ensure that the member has the necessary permissions to modify board backgrounds before using this endpoint.
This endpoint allows you to update the initials of a specified trello member. it is used when you need to change or set a member’s initials, which are often displayed as a visual representation of the user in various trello interfaces. the update is performed by sending a put request to the ‘/members/{idmember}/initials’ endpoint with the new initials value. this tool is particularly useful for maintaining accurate and up-to-date member information, especially after name changes or when customizing user representations. note that the new initials must adhere to specific formatting rules: they must be between 1 and 4 characters long and cannot start or end with a space.
Updates the attributes of a specific member on a trello board. this endpoint allows you to modify a member’s email address, full name, and role (type) associated with a particular board. use this when you need to change a member’s information or adjust their permissions on the board. it’s particularly useful for administrative tasks such as updating contact information or changing a member’s role. note that this endpoint only affects the member’s attributes for the specified board and does not modify their global trello account settings. be cautious when changing member roles, as it directly impacts their access and capabilities on the board.
Updates the full name of a specified trello member. this endpoint allows you to change the display name of a user in the trello system. it should be used when a member’s name needs to be corrected, updated due to a legal name change, or adjusted for any other valid reason. the endpoint requires the member’s unique identifier and the new full name value. it’s important to note that this operation only updates the full name and does not affect other profile information. be cautious when using this endpoint, as it directly modifies a user’s identifying information.
This endpoint allows you to update the name of a specific label in trello. it is used when you need to rename a label to better reflect its purpose or categorization. the endpoint requires the unique identifier of the label and the new name you want to assign to it. it’s particularly useful for maintaining organized and descriptive labels across your trello boards. keep in mind that while you can set an empty name, this doesn’t delete the label itself, only its text. this operation only affects the name attribute of the label and doesn’t modify other properties like color or visibility.
Updates the locale preference for a specific trello member. this endpoint allows you to change the language and regional settings for a user’s trello interface. use this when a member wants to switch their trello experience to a different language or adapt it to their local region. the change affects how dates, times, and other localized content are displayed for the user. note that this update only affects the user interface language and regional settings; it does not translate existing content within boards or cards.
Updates the attributes of labels on a specific trello card. this endpoint allows you to modify the color, name, and scope of labels associated with a card, enabling better organization and visual categorization of tasks. use this when you need to change the appearance or description of labels on a card, or when you want to update multiple labels at once. the endpoint is particularly useful for bulk updates or when synchronizing label information from external systems. note that this operation will override existing label attributes, so care should be taken to include all desired label information in the request.
Updates a specific saved search for a trello member. this endpoint allows you to modify the attributes of an existing saved search, including its name, position in the list of saved searches, and the actual query string. it’s useful for refining search criteria, reorganizing saved searches, or updating search names to reflect changes in projects or workflows. the endpoint requires the member id and the saved search id to be specified in the url path. only the fields you want to update need to be included in the request body, allowing for partial updates. this tool should be used when a user needs to modify an existing saved search rather than creating a new one or when the search criteria or organization needs to be adjusted over time to match evolving project needs.
Updates the color blind preference for a specific trello member. this endpoint allows you to enable or disable the color blind mode, which adjusts the color scheme of trello boards and cards for better visibility for users with color vision deficiencies. use this endpoint when a member needs to change their accessibility settings for improved usability. the change takes effect immediately across all of the member’s trello boards and interfaces. note that this preference is specific to the individual member and does not affect other users or the overall appearance of shared boards for other team members.
This endpoint updates the position of a specific saved search within a trello member’s list of saved searches. it allows for reordering saved searches to prioritize frequently used ones or organize them according to the member’s preference. the endpoint should be used when a member wants to change the order of their saved searches, either by moving a search to the top or bottom of the list, or by specifying a numeric position. this operation is particularly useful for members who have multiple saved searches and want to optimize their workflow by having their most important or frequently used searches easily accessible. note that this endpoint only updates the position of the saved search and does not modify any other attributes of the search or the member’s profile.
Updates a trello member’s preference for the frequency of summary notifications. this endpoint allows you to modify how often a user receives summary updates from trello. it’s particularly useful for customizing a member’s notification settings to match their workflow and information needs. the tool should be used when a user wants to change their summary notification frequency or disable summaries altogether. it’s important to note that this setting only affects summary notifications and does not impact other types of trello notifications.
Updates the attributes of a specific member on a trello board. this endpoint allows you to modify a member’s email address, full name, and role type (admin, normal, or observer) associated with a particular board. use this when you need to change a member’s information or permissions without removing and re-adding them to the board. the update is applied only to the specified board and doesn’t affect the member’s global trello account settings. note that you must have appropriate permissions (typically admin) on the board to make these changes. this endpoint is useful for managing team members, adjusting roles, or updating contact information within a specific trello board context.
This endpoint allows you to update the name of a specific saved search for a trello member. it’s used when a user wants to rename one of their existing saved searches, making it easier to organize and identify their frequently used search queries. the endpoint requires the member’s id and the id of the saved search to be updated, both of which should be provided in the url path. this tool is particularly useful for maintaining an organized workspace in trello, especially for users who rely heavily on saved searches to quickly access specific sets of cards or boards. note that this feature is typically available only to paid trello subscribers, and updating a saved search name doesn’t affect the search criteria itself, only its identifier.
Updates the username of a specific trello member. this endpoint allows you to change a member’s username, which is used for identification and mentions within trello. the new username must comply with trello’s naming conventions, including length and character restrictions. use this endpoint when a member needs to change their username, but be aware that the new username must be unique across all trello users. this operation may affect how the user appears in boards, cards, and notifications, so use it cautiously.
This endpoint allows you to update the attributes of a specific trello action, particularly its text content. it is used when you need to modify the description or details of an existing action, such as editing a comment or updating activity details. the endpoint accepts a put request with the action’s unique identifier in the url and the new text content in the request body. it’s important to note that this endpoint only updates the text of the action and cannot be used to change other properties or to create new actions. the updated text must adhere to the length constraints specified in the schema.
Updates the name of a specific trello card. this endpoint allows you to modify the title of an existing card, which is useful for renaming tasks, updating project status, or refining card descriptions. use this when you need to change a card’s name without altering its other attributes or position. the new name must be between 1 and 16384 characters long, providing flexibility for both short labels and detailed titles. note that this operation only affects the card’s name; other properties like description, due date, or attachments remain unchanged.
This endpoint updates the read status of a specific trello notification. it allows users to mark a notification as read or unread, which is essential for managing notification states and keeping track of important updates. the endpoint should be used when a user interacts with a notification, such as viewing it or deciding to keep it unread for later review. it’s particularly useful for applications that need to sync notification states between trello and external systems. note that this endpoint only updates the ‘unread’ status and cannot modify other attributes of the notification.
Updates the email position preference for a specific trello board. this endpoint allows you to set where new cards created via email integration will be placed within their designated list. use this when you want to change how email-generated cards are organized on your board. the setting affects all future email-to-board cards but does not reorganize existing cards. this tool is particularly useful for teams that frequently use email integration to create new tasks or items on their trello boards.
Updates the attributes of a specific custom board background for a trello member. this endpoint allows for the modification of the background’s brightness, file, and tiling options. it should be used when a member wants to change the appearance of their custom board background without creating a new one. this tool is particularly useful for personalizing the visual aspect of a trello board to suit individual preferences or improve visibility. note that this endpoint only modifies existing custom backgrounds and cannot be used to create new ones or apply changes across multiple boards.
Updates the background preference for a specific trello board. this endpoint allows users to change the visual appearance of their board by setting a new background. the background can be either a standard option provided by trello or a custom background previously uploaded by the user. this tool is useful for personalizing the look of a board, which can help in organizing and categorizing different projects or workflows. it should be used when a user wants to refresh the appearance of their board or align it with a specific theme or branding. note that updating the background is a cosmetic change and does not affect the functionality or content of the board itself.
Retrieves detailed information about a specific trello member. this endpoint allows you to access a member’s profile data, including their username, full name, initials, avatar, and other public information associated with their trello account. it’s useful when you need to display member details in your application or verify a member’s identity. the endpoint provides read-only access to member information and should be used when you require up-to-date data about a particular trello user. note that this endpoint may not return sensitive or private information, and the level of detail in the response may depend on the authentication and permissions of the requesting user.<<DEPRECATED use get_members_by_id_member>>
This endpoint allows you to update the unread status of a specific trello notification. it’s used to programmatically mark a notification as read or unread, which can be helpful for managing notification states in integrations or automated workflows. the endpoint takes the notification’s unique identifier and a boolean value to set its unread status. this tool is particularly useful for keeping trello notifications in sync with external systems or for bulk management of notification states. note that this endpoint only updates the unread status and does not modify any other attributes of the notification.
Updates the display name of a specific trello organization. this endpoint allows you to change how an organization appears within trello, which is useful for rebranding, correcting typos, or updating the organization’s name to reflect changes in the real world. the new name must be at least one character long and cannot start or end with a space. use this when you need to modify how an organization is presented across all trello boards and workspaces associated with it. note that this operation only affects the display name and does not alter any other organization attributes or its underlying structure.
Updates the voting preferences for a specific trello board. this endpoint allows you to control who can vote on cards within the board by setting the voting permission level. use this when you need to change the board’s voting access, such as restricting voting to members only or opening it up to the public. the change affects all cards on the board and can be useful for managing decision-making processes or gathering feedback from different groups. note that this endpoint only updates the voting preference and does not affect other board settings or permissions.
Updates the query of a specific saved search for a trello member. this endpoint allows you to modify the search terms of an existing saved search without changing other attributes of the saved search. it’s useful when you need to refine or adjust a frequently used search query. the endpoint requires the member’s id and the saved search id as path parameters, and accepts a new query value in the request body. use this when a user wants to update their saved search criteria without creating a new saved search or altering other saved search properties.
This endpoint updates the attributes of a user’s membership within a trello organization. it allows for modifying specific member fields and changing the membership type, providing fine-grained control over user roles and information. use this endpoint when you need to adjust a member’s details or permissions within an organization, such as promoting a user to admin status or updating their profile information. the endpoint requires the organization id and membership id to identify the specific membership to be updated. it’s important to note that this endpoint only modifies existing memberships and cannot be used to create new ones or remove users from an organization.
Updates an existing trello card with new attributes or modifications. this endpoint allows you to change various properties of a card, including its status, description, due date, attachments, board and list placement, labels, and assigned members. use this when you need to modify a card’s details, move it between lists or boards, or update its metadata. the endpoint is versatile, allowing for partial updates, so you can specify only the fields you want to change. it’s particularly useful for automating workflows, syncing card data with external systems, or bulk updating cards based on certain criteria. note that some updates, like changing the board or list, may affect the card’s visibility and accessibility to team members.
Updates the email list preference for a specific trello board. this endpoint allows you to change the designated list where new cards created via email will be placed. use this when you want to modify the default location for email-generated cards on a particular board. the update affects the ‘my prefs’ settings of the board, specifically the ‘id email list’ attribute. this is particularly useful for managing workflow automation and ensuring that email-to-board integrations place new tasks in the desired list. note that this operation only changes the preference and does not affect existing cards or lists.
Updates the text content of a specific trello action. this endpoint allows you to modify the text associated with an existing action, such as editing a comment or updating a description. it should be used when you need to correct, clarify, or expand upon the information in an action’s text. the endpoint is particularly useful for maintaining accurate and up-to-date records of activities and communications within trello boards and cards. note that this operation only affects the text content and does not change other properties of the action or its relationships to cards, boards, or other trello elements.
Updates the calendar feed enabled preference for a specific trello board. this endpoint allows you to enable or disable the calendar feed feature, which provides a calendar view of cards with due dates and allows for integration with external calendar applications. use this when you want to toggle the visibility of board tasks in calendar format or control the availability of the icalendar feed for the board. this operation is particularly useful for teams that rely on calendar views for project management or need to sync trello tasks with external calendar tools. note that enabling this feature may have privacy implications, as it potentially makes board data accessible through calendar feeds.
Updates the state of a specific check item within a checklist on a trello card. this endpoint allows you to mark a check item as complete or incomplete, which is essential for tracking task progress within a card’s checklist. use this when you need to update the status of a single task in a trello workflow. the endpoint is particularly useful for automating task updates or syncing task statuses with external systems. note that this operation only affects the state of the check item and does not modify other properties of the check item, checklist, or card.
This endpoint allows you to update various attributes and settings of a trello organization. use it to modify organization details, adjust visibility and permission settings, manage google apps integration, and control member access. the endpoint is particularly useful for organization administrators who need to fine-tune their trello workspace settings or update organization information. keep in mind that some changes, like modifying board visibility restrictions or disabling external members, can have significant impacts on collaboration within the organization. ensure you have the necessary permissions before making changes, as these updates can affect all members of the organization.
Updates the subscription status of a specific trello board for the authenticated user. this endpoint allows users to subscribe to or unsubscribe from a board, controlling whether they receive notifications for board activities. it’s useful for managing notification preferences on a per-board basis, enabling users to stay informed about important boards while reducing noise from less relevant ones. the endpoint should be used when a user wants to change their subscription status for a particular board, either to start or stop receiving updates about board activities.
This endpoint allows you to update the text of an existing comment on a specific trello card. it is used when you need to modify the content of a previously made comment, such as correcting information, adding details, or revising the message. the endpoint requires the unique identifiers for both the card and the specific comment (action) being updated, ensuring precise targeting of the comment to be changed. it’s important to note that this endpoint only updates the text content of the comment and does not affect other attributes like timestamps or authorship. the updated text must adhere to trello’s length restrictions for comments.
Updates the “show list guide” preference for a specific trello board. this endpoint allows users to toggle the visibility of the list guide feature, which provides guidance and tips for using lists on the board. use this when you want to enable or disable the list guide for a particular board, helping to customize the board’s appearance and user experience. the change applies immediately and affects all users who have access to the board. note that this preference is board-specific and does not affect other boards or global trello settings.
This endpoint updates the closed status of a specific trello card. it allows you to mark a card as closed (completed) or open (active) by setting its ‘closed’ attribute. use this endpoint when you need to change the completion status of a task represented by a trello card. the operation is particularly useful for automating workflow processes, such as closing cards when tasks are finished or reopening them if further action is required. note that closing a card doesn’t delete it or move it to the archive; it simply marks it as completed within its current list. this endpoint should be used judiciously as it directly affects the visible state of cards on trello boards.
Updates the closed status of a specified trello board. this endpoint allows you to either close an active board or reopen a closed board by setting the ‘value’ parameter to ‘true’ or ‘false’ respectively. use this when you need to archive a completed project or bring back a previously closed board for further use. it’s important to note that closing a board doesn’t delete it, but rather makes it inactive and inaccessible for normal operations. this action can be reversed by using the same endpoint to reopen the board.
Updates the description of a specific trello card. this endpoint allows you to modify or set the detailed text description of a card, providing more context or information about the task or item represented by the card. use this when you need to add, edit, or remove explanatory text for a card. the update replaces the entire existing description, so include all desired content in the request. this endpoint is particularly useful for automating workflows, synchronizing card details with external systems, or programmatically managing card information.
Updates the card aging preference for a specific trello board. this endpoint allows users to toggle between ‘pirate’ and ‘regular’ card aging modes, which visually represent card inactivity on the board. use this when you want to change how inactive cards are displayed, either for better visibility or to align with team preferences. the change affects all cards on the specified board. note that this endpoint only modifies the card aging setting and does not impact other board preferences or card contents.
Updates the position of a specific checklist within a trello card. this endpoint allows you to reorder checklists by moving them to the top, bottom, or a specific position within the card. use this when you need to prioritize or reorganize checklists on a card. the new position is specified using either keywords (‘top’, ‘bottom’) or a numeric value, providing flexibility in organizing your workflow. note that this operation only changes the checklist’s position and does not modify its contents or other attributes.
This endpoint updates the card covers preference for a specific trello board. it allows you to enable or disable the display of card covers, which are visual elements (images or colors) shown on the front of trello cards. use this endpoint when you want to change the appearance of cards across an entire board, either to show more visual information at a glance or to create a more streamlined view. the change affects all users viewing the board. note that this update only controls the visibility of existing card covers; it does not add or remove cover images from individual cards.
Updates the description of a specified trello organization. this endpoint allows you to modify the textual description associated with an organization, providing more context or information about its purpose, goals, or any other relevant details. use this when you need to change or refresh the description of an organization to better reflect its current state or focus. the new description can be up to 16384 characters long, allowing for detailed information, but it can also be set to an empty string if no description is needed.
Updates the description of a specified trello board. this endpoint allows you to modify the textual description of a board, providing context or information about its purpose and contents. use this when you need to add, change, or remove explanatory text for a board. the update is immediate and will be visible to all board members. keep in mind that while you can set an empty description, a well-crafted description can significantly improve board organization and team communication. this endpoint does not affect any other board properties or contents such as lists, cards, or members.
Updates the attributes of an existing trello checklist. this endpoint allows you to modify various properties of a checklist, including its associated board, card, name, and position. you can also use it to copy items from another checklist. use this endpoint when you need to change the details of a checklist, move it to a different card or board, rename it, reorder it, or populate it with items from another checklist. this is particularly useful for reorganizing tasks, updating project structures, or duplicating checklists across different cards or boards. the endpoint requires the id of the checklist to be updated, which should be provided in the url path.
Updates the name of a specific trello checklist. this endpoint allows you to modify the name of an existing checklist within a trello board or card. it’s useful when you need to rename a checklist to better reflect its purpose or content. the endpoint requires the unique identifier of the checklist and the new name value. it should be used when a checklist’s name needs to be changed without altering its items or other properties. note that this operation only affects the checklist’s name and does not modify any other attributes or items within the checklist.
Updates the due date of a specific trello card. this endpoint allows you to set or modify the deadline for a task represented by a card. it’s useful for managing timelines and priorities within your trello boards. the endpoint accepts a new date value or null to remove the due date. use this when you need to adjust task deadlines or remove time constraints from a card. note that this operation only affects the due date and does not modify other card attributes.
Updates the organization of a specified trello board. this endpoint allows you to move a board from one organization to another by changing its organization id. use this when you need to reorganize your trello workspace structure or when a project needs to be transferred to a different team or department. the operation requires the id of the board to be updated and the id of the new organization. it’s important to note that this action may affect board visibility and access permissions, so ensure that the board members have appropriate access to the new organization before making the change. this endpoint doesn’t return the updated board details, so you may need to fetch the board information separately to confirm the change.
Updates the name of the green label for a specific trello board. this endpoint allows you to customize the text associated with the green label, which can be used to categorize and filter cards on the board. use this when you want to change the meaning or purpose of the green label across the entire board. the update affects all existing and future cards using the green label. keep in mind that this change is board-wide and may impact existing workflows or filters based on the green label name. the endpoint does not allow changing the color of the label, only its textual representation.
Updates the comment preferences for a specific trello board, controlling who can add comments to cards. this endpoint allows you to change the comment permissions, ranging from completely disabling comments to allowing public access. use this when you need to adjust the collaboration settings of a board, either to restrict or expand commenting abilities. the changes apply immediately to all current and future cards on the board. note that this endpoint only modifies comment preferences and does not affect other board settings or permissions.
Updates the name of the blue label on a specific trello board. this endpoint allows you to customize the blue label’s name to better suit your project’s needs and improve organization. use this when you want to change or set the name of the blue label on a particular board. the new name can be any string up to 16384 characters long, including an empty string to remove the current name. this operation only affects the blue label and does not modify any other labels or board properties. keep in mind that changes to label names are visible to all board members and may impact existing workflows or filters based on label names.
This endpoint updates the attributes of an existing trello board. it allows you to modify various aspects of the board, including its name, description, visibility, organization affiliation, and numerous preferences. use this endpoint when you need to change board settings, update its status (e.g., open or closed), modify permissions, or enable/disable features like power-ups. the endpoint is flexible, allowing for partial updates by specifying only the attributes you wish to change. note that some changes, particularly to permission levels, can significantly affect who can access and interact with the board, so use with caution. this endpoint does not create new boards or manage board content (lists, cards) directly.
Updates the user’s preference for showing or hiding sidebar activity on a specific trello board. this endpoint allows users to customize their board view by toggling the visibility of the sidebar activity feed. it’s useful for personalizing the user experience on a per-board basis, allowing users to focus on the board content or stay informed about recent activities. the change only affects the view for the user making the api call and does not impact other board members’ preferences.
Updates the card associated with a specific checklist in trello. this endpoint allows you to move a checklist from one card to another, which is useful for reorganizing tasks or transferring checklists between different cards in your trello boards. it’s particularly helpful when restructuring workflows or when a set of tasks (represented by the checklist) needs to be reassigned to a different card. the operation requires the id of the checklist to be moved and the id of the destination card. note that this action will remove the checklist from its current card and attach it to the specified new card.
Updates the google apps domain associated with a specific trello organization. this endpoint allows administrators to link or change the google workspace domain connected to their trello organization, enabling integration features such as single sign-on (sso) and automatic user provisioning. use this when setting up or modifying the organization’s integration with google workspace. the update affects organization-wide settings and should be used cautiously, as it may impact user access and authentication methods.
Updates an existing webhook in trello, allowing you to modify its attributes such as description, active status, callback url, and the model it’s monitoring. this endpoint is used when you need to change the configuration of a webhook, such as activating or deactivating it, updating the url where notifications are sent, or changing which trello object it’s tracking. it’s particularly useful for maintaining and managing long-lived integrations between trello and external systems. the update is performed by sending a put request with the new webhook attributes in the request body.
This endpoint updates the description of a specific trello webhook. it allows users to modify the textual description associated with a webhook, providing context about its purpose or any relevant notes. the endpoint should be used when there’s a need to change or clarify the purpose of an existing webhook. it’s important to note that this operation only affects the description and does not modify other attributes of the webhook such as its callback url or active state. the description can be set to any string, including an empty string to remove the existing description.
The updatetrellosession endpoint allows you to update the attributes of a specific trello session. it is used to keep track of a user’s current activity within the trello application, including which board they are viewing and their overall session status. this endpoint is crucial for maintaining real-time updates and user presence information across the trello platform. you should use this endpoint when a user switches to a different board or when their session status changes (e.g., becoming idle or disconnecting). it helps trello optimize performance by focusing updates on active boards and users. however, be aware that updating the session too frequently may impact system performance, so it’s best to call this endpoint only when there are meaningful changes in the user’s activity or board focus. note that this endpoint does not provide any information about the board or user beyond what is updated. it is solely for updating session attributes and does not return detailed board or user data.
Updates the model (board, list, or card) that a specific trello webhook is monitoring. this endpoint allows you to change the focus of an existing webhook to a different trello entity, enabling dynamic adjustment of webhook targets without creating new webhooks. use this when you need to redirect a webhook’s notifications to a different board, list, or card, such as when project structures change or when implementing flexible monitoring systems. the endpoint requires the webhook’s id and the new model’s id to make the change. note that this operation only updates the monitored model; it does not affect other webhook properties like the callback url or description.
This endpoint allows you to update the active status of a specific trello webhook. it is used to either activate or deactivate a webhook, controlling whether it should receive notifications about changes to the associated trello model (board, list, or card). the endpoint is particularly useful when you need to temporarily pause notifications or re-enable a previously deactivated webhook without deleting and recreating it. note that this endpoint only modifies the active status; it does not alter other properties of the webhook such as the callback url or the model being monitored.
Updates the attributes of a specific member within a trello organization. this endpoint allows you to modify a member’s email address, full name, and role type (admin, normal, or observer) within the organization. use this when you need to change a member’s information or adjust their permissions within the organization. it’s particularly useful for onboarding, offboarding, or role changes within a team. note that this endpoint only updates the specified fields; any fields not included in the request will remain unchanged. ensure you have the necessary permissions within the organization to make these changes.
Updates the attributes of an existing trello webhook associated with a specific token. this endpoint allows you to modify the webhook’s description, callback url, or the trello model it monitors. use this when you need to change the configuration of a previously created webhook, such as updating the notification target or refining its monitoring scope. it’s particularly useful for maintaining and adjusting your application’s integration with trello as your needs evolve. note that this endpoint updates an existing webhook; it does not create a new one.
Updates the name of a specified trello organization. this endpoint allows you to change the unique identifier of an organization, which is used across the trello platform. it should be used when you need to rebrand or rename an organization. the new name must follow strict formatting rules to ensure consistency and avoid conflicts with other organizations. this operation is irreversible and will immediately affect all members and boards associated with the organization, so use it cautiously. note that this endpoint only updates the organization’s name and does not modify any other attributes or settings of the organization.
This endpoint updates the board visibility restriction preferences for a specific trello organization. it allows administrators to control who can change the visibility settings of boards within the organization. use this endpoint when you need to modify the organization-wide policy for board visibility changes, such as restricting these changes to admins only or allowing all members to modify board visibility. the change affects all boards within the organization and may impact collaboration and security settings. note that this endpoint requires appropriate administrative permissions to execute successfully.
Updates the deactivation status of a specific member within a trello organization. this endpoint allows organization administrators to activate or deactivate a member’s access to the organization’s resources. use this when you need to temporarily remove a member’s access without permanently deleting their account from the organization. the endpoint is particularly useful for managing team changes, offboarding processes, or controlling access during extended leaves. note that deactivation does not delete the member’s data or remove them from the organization entirely; it simply suspends their access until reactivated.
This endpoint updates the invite restriction preferences for a trello organization. it allows administrators to control who can invite new members to the organization by specifying an email address, domain, or special value. use this endpoint when you need to change the organization’s policy on member invitations, such as restricting invites to specific email domains or individuals. this tool is particularly useful for maintaining security and managing growth in large or sensitive trello organizations. note that this endpoint only updates the preference and does not directly add or remove members.
This endpoint allows you to update the attributes of an existing webhook in trello. webhooks are used to receive real-time notifications about changes to specified trello models (boards, lists, or cards). by updating a webhook, you can modify its description, activate or deactivate it, change the callback url, or update the model it’s monitoring. this is useful for maintaining and adjusting your integration’s event listening capabilities without having to create new webhooks for each change. use this endpoint when you need to modify webhook settings, such as changing the notification destination or adjusting which trello model is being monitored.
This endpoint allows you to update the attributes of existing members within a trello organization (workspace). it can be used to modify a member’s email address, full name, or membership type, providing flexibility in managing user information and access levels within your organization. the endpoint is particularly useful for administrative tasks such as updating contact information or changing a member’s role. note that you can update one or more attributes in a single request, but you must have the necessary permissions to make these changes. be cautious when modifying membership types, as this directly affects a user’s access and capabilities within the organization.
Updates the permission level preferences for a specified trello organization (workspace). this endpoint allows administrators to control the visibility and accessibility of the organization by setting it to either private or public. use this when you need to change the organization’s privacy settings, such as making it more restricted or opening it up for broader access. the change affects all boards and workspaces within the organization, so it should be used carefully. note that this endpoint only modifies the permission level and does not alter other organization settings or board-specific permissions.
Updates the ‘externalmembersdisabled’ preference for a specified trello organization. this endpoint allows you to control whether external members (users who are not part of the organization) can be added to the organization’s boards. when set to ‘true’, only existing organization members can be added to boards, enhancing privacy and security. use this endpoint when you need to modify the organization’s policy on external collaborators. it’s particularly useful for managing access control in corporate or sensitive project environments. note that this setting applies organization-wide and may affect existing boards with external members.
Updates the status of a specific trello session. this endpoint allows you to change the current state of a user’s session, which can be useful for managing user activity, handling timeouts, or updating session information. use this when you need to reflect changes in a user’s interaction state with trello, such as when a user becomes idle or reconnects after a disconnection. the endpoint is particularly useful for applications that need to maintain accurate session states or implement session management features. note that updating a session status does not create or authenticate a new session; it only modifies the state of an existing one.
This endpoint allows you to update the callback url for an existing trello webhook. use this when you need to change the destination where trello sends event notifications for a specific webhook. the new url must be valid and reachable with a head request to ensure it can receive webhook payloads. this operation is useful for maintaining the functionality of your trello integration, especially when your server infrastructure changes. note that only the callback url is updated; other webhook attributes remain unchanged. ensure your new endpoint is properly configured to handle trello’s webhook requests before updating.
Updates the google apps version preference for a specific trello organization. this endpoint allows you to change the version of google apps integration used by the organization, which can affect how trello interacts with google apps services. use this when you need to upgrade or downgrade the google apps integration for an entire organization. the change affects all members and boards within the organization. note that this endpoint only supports versions 1 and 2 of the google apps integration, and changing this setting may impact existing integrations and workflows.
This endpoint updates the visibility restriction preferences for private boards within a specific trello organization. it allows organization administrators to control who can change the visibility of private boards. use this endpoint when you need to modify the organization-wide policy for private board visibility changes. the endpoint is particularly useful for maintaining security and access control in enterprise environments where board visibility management is crucial. note that this setting only affects private boards and does not change the visibility of existing boards; it only restricts who can modify their visibility in the future.
Updates the website url associated with a specific trello organization. this endpoint allows you to modify or remove the external website link for an organization, which can be useful for maintaining up-to-date references to team or company websites. use this when you need to change the url displayed on the organization’s trello page or remove it entirely. the update is applied immediately, and all members of the organization will see the new website link (or its absence) upon the next page refresh. note that this endpoint only modifies the website url and does not affect any other organization attributes.
This endpoint updates the board visibility restriction preferences for public boards within a trello organization. it allows organization administrators to control who can create or change boards to public visibility. this setting is crucial for managing the organization’s data exposure and collaboration boundaries. use this endpoint when you need to modify the organization-wide policy for public board creation. it’s particularly useful for enhancing security, managing workspace settings, or adjusting collaboration policies as the organization’s needs evolve.