What authentication does the Basecamp 3 API use?

Basecamp 3 uses OAuth 2.0 bearer tokens, sent in the Authorization header. Through Jentic, your token is stored encrypted by your own Jentic One instance and injected at execution time, so the agent never handles raw client secrets or refresh tokens.

Can I create and complete to-dos with the Basecamp 3 API?

Yes. POST /todolists/{todoListId}/todos.json creates a to-do with content, due date, and assignees, POST /todos/{todoId}/completion.json marks it complete, and DELETE /todos/{todoId}/completion.json reopens it. Repositioning is handled by PUT /todos/{todoId}/position.json.

What are the rate limits for the Basecamp 3 API?

Basecamp applies several limits and adjusts them dynamically, with separate limits for GET and POST requests and per-second, per-hour and per-day windows. The first one you commonly meet is 50 requests per 10 second period per IP address. Exceeding any limit returns 429 Too Many Requests, and the Retry-After response header gives the number of seconds to wait, so respond to it dynamically rather than hard-coding a delay.

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

Install Jentic One on the machine that will host it, register your agent from a separate machine, and import the Basecamp 3 API from the API Directory. Your agent then searches 'post a basecamp message', loads the createMessage operation, supplies messageBoardId plus a subject and HTML content body, and executes. Your OAuth token is injected at call time by your own instance.

Does the Basecamp 3 API require an account ID in every request?

Yes. The base URL is https://3.basecampapi.com/{accountId}, and every endpoint path is appended to that account-scoped prefix. The account ID does not come back with the access token: once you hold a token, make a separate authenticated request to https://launchpad.37signals.com/authorization.json, which lists the accounts the user can access, then pick the account whose product is bc3 and use its href as the base URL.

Is there a Basecamp 3 API MCP server?

You do not need an MCP server to give your agent the Basecamp 3 API. Jentic connects it directly from the API Directory: import the API, store your OAuth token once, and your agent calls the operations it needs. Nothing extra is loaded into the agent's context, because operations are discovered on demand rather than registered up front as tool definitions.

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

Yes. Because you run Jentic One yourself, your own rules decide which Basecamp 3 operations and credentials the agent may use. Basecamp 3 carries the project and recording id in the URL path (for example /projects/{projectId}/... and /todolists/{todoListId}/todos.json), so a rule can pin the agent to a single project where it adds to-dos via POST /todolists/{todoListId}/todos.json and posts to a board via POST /message_boards/{messageBoardId}/messages.json and nothing else. You also pick the exact operations it may call, so an action like granting project access through PUT /projects/{projectId}/people/users.json stays off unless you add it.