Building Custom Integrations with the REST API
Use Curyloop's REST API to build custom integrations, automate workflows, and connect with your existing tools.

Why use the API?
While Curyloop's web interface and browser extension cover most use cases, the REST API unlocks custom workflows that go beyond what the UI offers:
- Automate item creation from other tools
- Build custom dashboards and reports
- Integrate Curyloop into your existing workflows
- Sync data between Curyloop and other platforms
Getting started
Authentication
All API requests require an API key. Generate one from your account settings:
- Go to Settings > API
- Click Generate API Key
- Copy and store the key securely - it won't be shown again
Include the key in your request headers:
Authorization: Bearer your-api-key-here
Base URL
All API endpoints are available at:
https://api.curyloop.com/v1
Common use cases
Adding items programmatically
Create items in a session from any source:
curl -X POST https://api.curyloop.com/v1/sessions/{sessionId}/items \
-H "Authorization: Bearer your-api-key" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com/article",
"note": "Relevant to our Q1 research",
"tags": ["research", "competitor"]
}'
Fetching session data
Pull session data for custom reporting:
curl https://api.curyloop.com/v1/sessions/{sessionId} \
-H "Authorization: Bearer your-api-key"
Listing group sessions
Get all sessions for a group:
curl https://api.curyloop.com/v1/groups/{groupId}/sessions \
-H "Authorization: Bearer your-api-key"
Integration ideas
| Integration | What it does |
|---|---|
| Slack bot | Post a link in Slack and it gets added to the current session |
| RSS reader | Automatically add items from RSS feeds |
| GitHub | Save notable issues, PRs, or discussions |
| CRM | Connect customer feedback to research sessions |
| CI/CD | Add release notes and changelogs to a team knowledge base |
Building a Slack integration
A simple example: a Slack bot that saves shared links to Curyloop.
- Create a Slack app with the
links:readevent - When a link is shared in a designated channel, your bot captures the URL
- Use the Curyloop API to create an item in the active session
- Reply in the Slack thread confirming the save
This workflow turns your Slack channels into automatic content feeds for Curyloop.
Rate limits and best practices
- Rate limit: 100 requests per minute per API key
- Pagination: Use
cursorparameters for listing endpoints - Error handling: Always check response status codes and handle 429 (rate limit) gracefully
- Idempotency: Use the
urlfield to avoid creating duplicate items
Next steps
- Automation with n8n for no-code workflow automation
- MCP Setup for AI tool integrations
- Managing Multiple Groups for scaling your setup
Ready to try it yourself?
Start building your team's knowledge base today. Free to start, no credit card required.