Every one of the 2196 endpoints the API exposes, grouped the way the product is. Each page lists the method, the path, what the endpoint is for, its parameters, the fields it accepts where those are published, and a command you can paste into a terminal.
These pages are generated from the document the running API publishes, so they describe what the software does rather than what somebody remembered it did.
By area
- Accountant endpoints: 46 endpoints across 13 resources.
- Accounting & finance endpoints: 87 endpoints across 14 resources.
- AI writing endpoints: 8 endpoints across 5 resources.
- Authentication endpoints: 30 endpoints across 20 resources.
- Boards endpoints: 1 endpoint across 1 resource.
- Calendar endpoints: 29 endpoints across 13 resources.
- Channel partners endpoints: 29 endpoints across 17 resources.
- Charcha endpoints: 82 endpoints across 24 resources.
- Collections endpoints: 8 endpoints across 5 resources.
- CRM endpoints: 200 endpoints across 15 resources.
- Documents endpoints: 52 endpoints across 11 resources.
- Email endpoints: 27 endpoints across 13 resources.
- Events and card scanning endpoints: 37 endpoints across 17 resources.
- Feedback & roadmap endpoints: 6 endpoints across 3 resources.
- Files endpoints: 7 endpoints across 4 resources.
- Integrations endpoints: 29 endpoints across 5 resources.
- Inventory endpoints: 234 endpoints across 26 resources.
- Live updates endpoints: 1 endpoint across 1 resource.
- Manufacturing endpoints: 57 endpoints across 8 resources.
- Mobile app endpoints: 10 endpoints across 6 resources.
- Modules you added endpoints: 16 endpoints across 8 resources.
- Notifications endpoints: 29 endpoints across 12 resources.
- Platform endpoints: 123 endpoints across 32 resources.
- Point of sale endpoints: 36 endpoints across 10 resources.
- Portal endpoints: 16 endpoints across 9 resources.
- Procurement endpoints: 123 endpoints across 7 resources.
- Projects endpoints: 56 endpoints across 18 resources.
- Quality endpoints: 101 endpoints across 7 resources.
- Reports endpoints: 19 endpoints across 11 resources.
- Sales documents endpoints: 296 endpoints across 14 resources.
- Service endpoints: 2 endpoints across 2 resources.
- Settings endpoints: 202 endpoints across 41 resources.
- Subscriptions endpoints: 158 endpoints across 41 resources.
- Vendors endpoints: 10 endpoints across 8 resources.
- Warranty endpoints: 29 endpoints across 17 resources.
Machine-readable
- Interactive reference: app.jaicrm.ai/docs. Every endpoint, callable from the page.
- OpenAPI document: /docs/json. Feed it to Postman, Insomnia, or a client generator.
Generating a client
The document is OpenAPI 3, so the usual generators work:
npx @openapitools/openapi-generator-cli generate
-i https://app.jaicrm.ai/docs/json
-g typescript-fetch
-o ./jai-client
The app is a client of this API. There is no privileged back channel, if a screen can do it, a request can do it, which is the simplest guarantee that the API stays complete.
Something missing or wrong here? Tell us. A question that needed asking usually means a page that needed writing.