Go straight to the source.
Find the official documentation referenced by the ListAPI.com guides, including Google, Trello, Obsidian, Mailchimp, Mailman, Asana, Anki, and more.
These official references support the provider-specific distinctions discussed in the journal. Each article links to its own reference and separates that documentation from our proposed architecture and workflow guidance. Reviewed September 11, 2026.
- Notion: retrieve block childrenUsed in Note Taking List API
- Google Tasks: task resourceUsed in To Do List API
- Google Calendar: events.listUsed in Calendar Listing API
- Atlassian: Trello nested resourcesUsed in Trello List API
- Obsidian Help: propertiesUsed in Obsidian List Email
- Mailchimp: manage subscribersUsed in Email Newsletter List API
- GNU Mailman: membership REST APIUsed in Mailing List API
- Gmail API: users.messages.listUsed in Mail List API
- Google People API: people.connections.listUsed in Contacts List API
- OWASP: authorization cheat sheetUsed in Friend List API
- Snipe-IT: list hardwareUsed in Asset Listing API
- Anki Manual: notes, cards, and decksUsed in Flashcard List API
- Asana: get tasks from a projectUsed in Project Management List API
- Chrome for Developers: bookmarks APIUsed in Bookmark List API
How to use a reference
Read the provider’s current authentication, versioning, limits, and method details before writing a real integration. A guide’s example field names are not interchangeable with production parameters. For historical behavior, locate documentation or release notes for the version and date in question.
How the topics were chosen
The directory groups the requested list concepts by their actual record type: productivity, knowledge, communication, people, and assets. Official documentation helped distinguish terms such as a message list, a membership roster, and a subscriber audience. No search-volume, ranking, or keyword-difficulty figures are claimed.