canonical: https://jentic.com/apis/vslcloud.com/vslcloud # Vslcloud Voyager Infinity API Recruitment CRM API for managing candidates, companies, contacts, jobs, and placements. The API exposes 25 endpoints secured with apiKey authentication. ## For AI agents Programmatically login to account, logout. Covers 25 operations with apiKey authentication. ## Scope Does not handle payments, communications, or developer tools - use for crm only. ## Capabilities - Login to account - Logout - Keep session alive - List databases - Create company - Get company ## Use cases ### CRM Operations Use the Voyager Infinity API to perform crm operations programmatically. The API provides 25 endpoints covering core functionality including login to account, logout, keep session alive. Example prompt: Call POST `/Account/Login` to login to account ### Automated Account Management Automate account operations by combining multiple Voyager Infinity API endpoints. Agents can logout and then keep session alive in a single workflow. Example prompt: Call POST `/Account/Logout` to logout, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Voyager Infinity API 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 apiKey tokens manually. Example prompt: Search Jentic for 'login to account', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/Account/Login` | Login to account | | POST | `/Account/Logout` | Logout | | GET | `/Account/KeepAlive` | Keep session alive | | GET | `/Database/Databases` | List databases | | GET | `/Entity/Companies` | List companies | | POST | `/Entity/Company` | Create company | | GET | `/Entity/Company` | Get company | | PUT | `/Entity/Company` | Update company | ## Key resources - **Account** — Operations related to Account - **Companies** — Operations related to Companies - **Contacts** — Operations related to Contacts - **Database** — Operations related to Database - **Locations** — Operations related to Locations ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 68 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 82 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 54 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 100 / 100 - **View full report:** https://jentic.com/apis/vslcloud.com/vslcloud/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring Voyager Infinity by hand means running its `/Account/Login` flow, carrying the session cookie against live.vslcloud.com, and keeping it alive yourself. Through Jentic you install once, import Voyager Infinity from the API Directory, store the credential once, and your agent calls it. - **Permission scoping:** Voyager Infinity carries its entity data in request bodies and query parameters rather than the URL path, so limit the agent to the operations it needs, such as listing or reading a company. You choose the allowed set, so company updates via the PUT are not included unless you add them. - **Credential handling:** Your Voyager Infinity credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'log in to an account' or 'list companies', and Jentic returns the matching Voyager Infinity operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Hubspot** — Alternative crm API - **Salesforce** — Alternative crm API - **Pipedrive** — Complementary crm API - **Zoho** — Complementary crm API ## FAQ ### What authentication does the Voyager Infinity API use? The Voyager Infinity API uses an API key passed in the `session` cookie. 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 login to account with the Voyager Infinity API? Yes. Use the POST `/Account/Login` endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Voyager Infinity API? 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 login to account through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'login to account'. Jentic returns the matching Voyager Infinity API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Voyager Infinity API have? The Voyager Infinity API exposes 25 endpoints covering account, companies, contacts operations. ### Can I limit what my agent is allowed to do with the Voyager Infinity API? Yes. Because you run Jentic One yourself, you decide which Voyager Infinity operations your agent may call and which credential it uses. Since the API carries its entity data in request bodies and query parameters rather than the URL path, you can allow read-only operations such as listing companies with GET `/Entity/Companies` or reading one with GET `/Entity/Company` while excluding the write paths. Company creation via POST `/Entity/Company` and updates via PUT `/Entity/Company` are not available to the agent unless you explicitly add them to the allowed set.