Basecamp API

What authentication does the Basecamp API use?

Basecamp uses OAuth 2.0 with per-user access tokens scoped to a Basecamp account. Each request must include the Authorization header with the bearer token, and the URL contains the account ID in the path. When called through Jentic, the OAuth tokens are stored encrypted in your Jentic One instance and injected at execution time.

Can I create to-dos in a Basecamp project?

Yes. POST /todolists/{todolistId}/todos.json with the to-do content and optional assignees. The to-do list ID comes from listing to-do lists under a to-do set via /todosets/{todosetId}/todolists.json.

What are the rate limits for the Basecamp API?

Basecamp runs several limits at once, for example separate GET and POST limits and per-second, per-hour and per-day limits, and it adjusts them dynamically. The vendor describes the first limit you commonly encounter as 50 requests per 10 second period per IP address. Exceeding a limit returns 429 Too Many Requests; consult the Retry-After response header for how many seconds to wait before retrying, and batch read calls (for example, list /people.json once and cache rather than re-fetching per request).

How do I post a message to a Basecamp project through Jentic?

Install Jentic One, import the Basecamp API from the API Directory, then have your agent search for 'post a message to a basecamp project' and execute POST /message_boards/{messageBoardId}/messages.json with the message subject and content. Jentic injects the OAuth bearer token, calls Basecamp, and returns the created message record.

Does the Basecamp API expose campfire chat history?

Yes. Campfires are modelled as chat resources: GET /chats.json lists the campfires visible to the current user, GET /chats/{chatId}.json returns one campfire, and GET /chats/{chatId}/lines.json returns its chat lines. Posting is supported too, with POST /chats/{chatId}/lines.json. Reads are scoped by the campfire ID rather than the project ID.

Is there a Basecamp MCP server?

You do not need an MCP server to give your agent Basecamp. Jentic connects the API directly from the API Directory: import it, store your OAuth credential once in your self-hosted Jentic One instance, and your agent calls the 29 operations described here without loading another server's tool definitions into its context. Basecamp's own API reference points AI-agent users at Basecamp Skills and the Basecamp CLI. Either way, your rules decide which Basecamp operations the agent may call.

Can I limit what my agent is allowed to do with the Basecamp API?

Yes. Because Jentic One is self-hosted, your own rules decide which Basecamp operations and credentials the agent may use. Since Basecamp puts the account ID in the base path and the project ID in the URL path (for example /projects/{projectId}.json), you can pin the agent to a single account and its projects so it only reads and updates to-dos, messages, comments, and campfires within that scope. You also choose the exact operations it may call, so destructive actions like creating projects via POST /projects.json are excluded unless you explicitly allow them.