API Overview
How the Aiinak REST APIs are organized, base URLs per product and common conventions.
How the APIs are organized
Every Aiinak product exposes a REST API under its own base URL. All APIs share the same authentication, pagination and error conventions, so once you have integrated with one product the others feel familiar.
| Product | Base URL |
|---|---|
| AiMail | https://api.aiinak.com/email/v1 |
| AI Search | https://api.aiinak.com/search/v1 |
| Smart Drive | https://api.aiinak.com/drive/v1 |
| AI Meeting | https://api.aiinak.com/meetings/v1 |
| AI Recruit | https://api.aiinak.com/recruit/v1 |
| Enterprise AI | https://<tenant>.inflowerp.com/api/v1 |
| Admin / Analytics | https://api.aiinak.com/admin/v1 |
Enterprise AI is tenant-scoped: requests go to your tenant subdomain and are isolated to your tenant database.
Conventions
JSON everywhere
Requests and responses use JSON. Send Content-Type: application/json.
Cursor pagination
List endpoints return a next_cursor; pass it as ?cursor= to fetch the next page.
Consistent errors
Errors return an error object with code, message and a request_id for support.
Versioned paths
Breaking changes ship as a new /v2 path; /v1 keeps working for at least 12 months.