Trello Getting Started: Create Account, Get Keys, First Request (2026)

Getting started overview

Integrating with Trello's API involves a sequence of steps designed to ensure secure access and proper interaction with Trello resources. The process begins with establishing an Atlassian account, which grants access to Trello. Subsequently, users generate the necessary API credentials—an API key and a token—from within their Trello developer settings. These credentials are then used to authenticate requests to the Trello REST API, enabling programmatic management of boards, lists, and cards.

Trello's API supports a RESTful architecture, allowing for standard HTTP methods (GET, POST, PUT, DELETE) to interact with resources. The API documentation provides a comprehensive guide to available endpoints and expected request/response formats. Successful integration typically culminates in making a first authenticated API call, such as retrieving a user's boards, which confirms that the setup is correct and credentials are valid.

Here's a quick reference table outlining the initial setup steps:

Create an account and get keys

To access the Trello API, an Atlassian account is required, as Trello is an Atlassian product. If you do not have an Atlassian account, you can create one through the Trello signup process. This account will serve as your primary credential for both the Trello web interface and API access management.

Once your account is established, you can proceed to obtain your API key and a server token. These are the primary methods for authenticating your API requests, particularly for initial exploration and development. Trello also supports OAuth 1.0a for more secure, user-delegated access, but for getting started, the API key and token are sufficient.

Obtaining your API Key:

1. Navigate to the Trello Power-Ups admin page.
2. Locate the section titled "Developer API Key". Your personal API key will be displayed here. Copy this key, as it is essential for all authenticated API calls.

Generating your Server Token:

1. On the same Trello Power-Ups admin page, find the text "Your Token".
2. Click on the blue link that says "Token" next to it. This will redirect you to a new page where you can generate a new server token.
3. Review the permissions requested for the token (read, write, etc.) and click the "Allow" button to generate it.
4. Copy the generated token. This token, along with your API key, will authenticate your requests to the Trello API. Keep both your API key and token secure, as they grant access to your Trello data.

Your first request

With your API key and token in hand, you can now make your first authenticated request to the Trello API. A common initial request is to retrieve information about the currently authenticated user or their boards. This verifies that your credentials are valid and correctly configured.

Example: Get your Trello boards

To retrieve a list of boards associated with your account, you can use the /members/me/boards endpoint. This endpoint requires your API key and token for authentication.

Using cURL:

Replace YOUR_API_KEY and YOUR_API_TOKEN with the credentials you obtained.

curl "https://api.trello.com/1/members/me/boards?key=YOUR_API_KEY&token=YOUR_API_TOKEN"

Expected Response (JSON format):

A successful response will return an array of JSON objects, each representing a Trello board. The structure will resemble the following, with various fields describing each board:

[
  {
    "id": "60c72f10d4c1a5001a1b1a1b",
    "name": "My First Trello Board",
    "desc": "A board for my initial projects.",
    "descData": null,
    "closed": false,
    "idOrganization": "60c72f10d4c1a5001a1b1a1c",
    "pinned": false,
    "url": "https://trello.com/b/exampleboardid/my-first-trello-board",
    "shortUrl": "https://trello.com/b/exampleboardid"
    // ... more board properties
  },
  {
    "id": "60c72f10d4c1a5001a1b1a1d",
    "name": "Team Collaboration Board",
    "desc": "Board for team tasks.",
    "closed": false,
    // ... more board properties
  }
]

If you receive a 200 OK status code and a JSON array containing your Trello boards, your setup is successful. If you encounter an error, refer to the troubleshooting section.

Common next steps

After successfully making your first API call, you can explore various functionalities offered by the Trello API. The official Trello REST API documentation provides detailed information on all available endpoints and their usage.

Common next steps include:

• Listing Lists and Cards: Once you have a board ID, you can retrieve its lists (columns) and the cards within those lists. This is fundamental for interacting with Trello's core structure.
• Creating New Resources: Experiment with creating new boards, lists, or cards programmatically. This demonstrates the write capabilities of the API.
• Updating Existing Resources: Modify properties of existing cards or boards, such as changing a card's description or moving it to a different list.
• Using Webhooks: For real-time updates, consider setting up Trello webhooks. Webhooks allow Trello to send automated notifications to your application when specific events occur (e.g., a card is moved, a comment is added). This is crucial for building reactive integrations.
• Implementing OAuth: For applications that interact with multiple Trello users or require more granular control over permissions, implementing OAuth 1.0a for Trello is recommended. This allows users to grant your application specific permissions without sharing their personal API key and token directly.
• Exploring Power-Ups: Trello Power-Ups extend Trello's functionality. While outside the direct scope of the REST API, understanding how Power-Ups interact with the Trello platform can inspire more advanced integrations.
• Reviewing Rate Limits: Be aware of Trello's API rate limits to avoid unexpected interruptions to your service. Plan your requests to stay within these limits, and implement exponential backoff for retries if necessary.

Troubleshooting the first call

If your initial API call does not return a successful response, several common issues could be at play. Review these points to diagnose and resolve problems:

• Incorrect API Key or Token: Double-check that you have copied the correct API key and token. Even a single character mismatch will result in an authentication failure. Re-generate your token if you are unsure.
• Missing Parameters: Ensure that both key and token parameters are correctly included in your URL query string for each request.
• Network Connectivity: Verify that your system has an active internet connection and can reach api.trello.com. Network firewalls or proxies might block access.
• HTTP Status Codes: Pay close attention to the HTTP status code returned in the API response. Common error codes include:
  • 401 Unauthorized: Indicates that your API key or token is missing or invalid.
  • 404 Not Found: The requested resource (e.g., a board ID) does not exist, or the endpoint URL is incorrect.
  • 400 Bad Request: Often means there's an issue with the format or content of your request.
  • 429 Too Many Requests: You have exceeded Trello's API rate limits. Implement a delay and retry logic.
• URL Encoding: Ensure that any special characters in your query parameters (if you're passing more than just key and token) are properly URL-encoded.
• Endpoint Availability: While rare, Trello's API might experience temporary outages. Check the Atlassian status page for any reported issues.
• Developer Tools: Use your browser's developer console (Network tab) or an HTTP client like Postman or Insomnia to inspect the full request and response, including headers and body, for more detailed error messages.