canonical: https://jentic.com/apis/scalekit.com/scalekit # Scalekit APIs Overview The Scalekit API is a RESTful API that enables you to manage organizations, users, and authentication settings. All requests must use HTTPS. All API requests use the following base URLs: Scalekit operates two separate environments: Development and Production. Resources cannot be moved between environments. Quickstart The Scalekit API uses OAuth 2.0 Client Credentials for authentication. C. The API exposes 87 endpoints secured with oauth2 authentication. ## For AI agents Programmatically create a connected account, list connected accounts. Covers 87 operations with oauth2 authentication. ## Scope Does not handle payments, communications, or crm - use for e-commerce only. ## Capabilities - Create a connected account - List connected accounts - Update connected account credentials - Get connected account details - Generate authentication magic link - Delete a connected account - Search connected accounts ## Use cases ### E-Commerce Operations Use the Scalekit APIs to perform e commerce operations programmatically. The API provides 87 endpoints covering core functionality including create a connected account, list connected accounts, update connected account credentials. Example prompt: Call POST `/api/v1/connected_accounts` to create a connected account ### Automated Organizations Management Automate organizations operations by combining multiple Scalekit APIs endpoints. Agents can list connected accounts and then update connected account credentials in a single workflow. Example prompt: Call GET `/api/v1/connected_accounts` to list connected accounts, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Scalekit APIs endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually. Example prompt: Search Jentic for 'create a connected account', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/api/v1/connected_accounts` | Create a connected account | | GET | `/api/v1/connected_accounts` | List connected accounts | | PUT | `/api/v1/connected_accounts` | Update connected account credentials | | GET | `/api/v1/connected_accounts/auth` | Get connected account details | | POST | `/api/v1/connected_accounts/magic_link` | Generate authentication magic link | | POST | `/api/v1/connected_accounts:delete` | Delete a connected account | | GET | `/api/v1/connected_accounts:search` | Search connected accounts | | GET | `/api/v1/connections` | List connections | ## Key resources - **Organizations** — Organization represents a customer or a tenant of your product. This is the top level entity and all - **Permissions** — Permission management for defining and controlling access to system resources. Create, retrieve, upd - **Users** — Comprehensive user management operations including user lifecycle, organization memberships, and inv - **Connections** — Manage enterprise connections for your Scalekit environment. This service provides endpoints for ret - **Directory** — Directory management for viewing and controlling external identity provider connections in your Scal ## Why Jentic - **Setup:** Wiring the Scalekit APIs by hand means running the OAuth2 client-credentials flow for a token, substituting your subdomain into the host, and managing connected accounts and connections yourself. Through Jentic you install once, import the Scalekit APIs from the API Directory, store the client credentials once, and your agent calls it. - **Permission scoping:** These operations act on connected accounts through the request body and colon-suffixed actions rather than a resource id in the URL path, so you limit the agent to the operations it needs, such as listing or searching connected accounts, and you leave out write operations like creating an account, sending a magic link, or the delete action unless you add them. Every operation the agent runs is one you chose. - **Credential handling:** Your Scalekit client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a connected account' or 'search connected accounts', and Jentic returns the matching Scalekit operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Shopify** — Alternative e commerce API - **Stripe** — Alternative e commerce API ## FAQ ### What authentication does the Scalekit APIs use? The Scalekit APIs uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I create a connected account with the Scalekit APIs? Yes. Use the POST `/api/v1/connected_accounts` endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Scalekit APIs? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I create a connected account through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a connected account'. Jentic returns the matching Scalekit APIs operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Scalekit APIs have? The Scalekit APIs exposes 87 endpoints covering organizations, permissions, users operations. ### Can I limit what my agent is allowed to do with the Scalekit API? Yes. Because you run Jentic One yourself, your own rules decide which Scalekit operations and credentials the agent can use, and it can only call the ones you allow. Since these operations act on connected accounts through the request body and colon-suffixed actions rather than a resource id in the path, you can grant read-only work like listing or searching connected accounts while leaving out write operations such as creating an account, sending a magic link, or the delete action. Every Scalekit call the agent makes is one you explicitly chose to enable.