Meeting scheduling that gets out of the way. Routing forms qualify the lead, availability is computed from real calendars, and the meeting lands on the right person's day.
Everything public lives in 42min-developers:
| REST API | https://api.42min.us/v1 |
| OpenAPI 3.1 | api.42min.us/openapi.yaml |
| MCP server | https://api.42min.us/mcp |
| Documentation | 42min.us/help/api |
Point a client generator, Postman, or a coding agent straight at the OpenAPI URL.
Connecting an AI assistant? The MCP server exposes 35 scheduling tools over OAuth, and any compliant client can connect without a plugin: it publishes its own protected-resource metadata. There is a Cursor plugin if you want the editor integration ready-made.
Handling webhooks? Start from the receiver example. Signature verification is where these integrations break, and the usual cause is verifying a re-serialized body instead of the raw bytes.
Open an issue for API bugs or specification errors. Security reports go to plus@42min.us, never to the issue tracker.