How do I access the Managelify API?
Create an API key in one click from Settings → Developer, set its scope (permission range) and expiration date. Send the key to REST endpoints with the 'Authorization: Bearer ...' header. The OAuth 2.0 (Authorization Code + PKCE) flow is also supported — third-party apps that act on a user's behalf connect this way. With the sandbox environment you can test without touching production.
Which resources can I access via the API?
All WRM modules in Managelify are accessible through one consistent REST schema: projects and tasks, subtasks, customers and the sales pipeline, quotes, product/service catalog, forms, contracts, calendar and meetings (Meet/Zoom/Teams), meeting recordings + transcripts, files and versions, message channels, team and roles. Every resource shares the same pagination, filter, sorting and error format — learning one endpoint means learning them all.
How do webhooks work, which events can I subscribe to?
Register a webhook URL and select the events you care about (e.g. task.created, project.status_changed, customer.created, deal.stage_changed, meeting.ended, transcript.ready, file.uploaded). When the event fires, a JSON payload is POSTed to your server; every request is signed with HMAC SHA-256 and you verify it with your secret. Failed requests are retried with exponential backoff; all events are logged in the panel and can be replayed manually — no event is missed.
How are rate limits and quotas managed?
Each API key has a per-minute and per-hour quota; the standard plan is around 600 requests per minute and increases with the plan. As you approach the quota, the X-RateLimit-Remaining header warns you; when exceeded, a 429 response is returned with a Retry-After header. For bulk operations use batch endpoints — instead of N calls for N records, one request handles thousands of rows efficiently.
How is API security ensured?
OAuth 2.0 (PKCE) and API keys are both supported. Every key is scoped (read/write/admin), restricted by resource (project/team) and optional IP allowlist; an expiration date can be set. All traffic flows over TLS 1.2+; every call lands in the audit log with who, when, which resource and the outcome. When an employee leaves or a key leaks, you can revoke/rotate it in one click. KVKK & GDPR compliant, aligned with SOC 2 principles.
Is there integration with n8n, Zapier or Make?
Yes. While official connectors are in progress, the Managelify API works seamlessly today with the standard HTTP nodes in n8n / Zapier / Make — the OpenAPI schema and ready-made templates are live. Example workflow JSONs are shared for typical flows (form → CRM, payment → task, calendar → Slack notification); when Mana AI hears 'do this when that happens' in natural language, it drafts the n8n / Zapier chain.
Where are the SDK and documentation?
The OpenAPI 3.1 schema, interactive documentation and quick-start guides live in the Developer portal. JavaScript/TypeScript and Python SDKs are released first; Go, PHP and Ruby are being built with the community. Every endpoint comes with cURL, JS and Python examples and real payload templates. With the Postman collection and the sandbox environment you can test the entire flow without touching production and finish the integration quickly with mock data.
How does API access connect to the rest of Managelify?
API access is the door through which the Work Relationship Management (WRM) core opens to the outside. Automation & Actions builds webhook triggers visually; Create Tasks by Command auto-generates tasks from webhook events; Permissions & Access Control manages API scopes alongside team roles under the same umbrella; Mana AI drafts call chains from natural language; CRM, Task Management, Calendar, Recording & Transcript modules push data out and pull external events in through the same API. One flow: project + task + communication + CRM + calendar — the API is embedded as the programmatic layer of that flow.