innos API

Name: innos API
Brand: innos API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationapiKey3 EndpointsREST

For Agents

Submit, list, and vote on ideas in the innos innovation management platform.

Install Jentic One Beta

Connect the innos API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the innos API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with innos API.

List all ideas currently in the innos workspace via GET /ideas

Submit a new idea on behalf of a user via POST /ideas

Cast a vote on an existing idea via POST /ideas/{id}/vote

Pull innos ideas into reporting tools or dashboards for innovation tracking

GET STARTED

Start building with innos API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use innos API for, with concrete tasks.

★ Idea Intake from External Channels

Capture ideas wherever they originate — Slack, email, an internal form — and submit them to innos without requiring the contributor to log into another tool. POST /ideas accepts the idea fields and returns the new idea ID. Lowers the friction of contribution and increases the volume of ideas captured by innovation programmes.

POST /ideas with title 'Switch lobby lighting to motion-sensor LEDs' and description from a Slack message thread.

Innovation Programme Reporting

Read ideas out of innos into a central reporting layer to track submission volume, vote distribution, and triage progress over time. GET /ideas returns the current list. Useful for innovation programme leads who need to demonstrate engagement and outcomes to executive sponsors.

Call GET /ideas, group results by submission month, and summarise total ideas and vote counts.

Voting Automation

Cast votes on behalf of users when promising ideas surface — for example, an executive sponsor automatically endorsing the top idea in a quarterly review, or a Slack reaction translating into an innos vote. POST /ideas/{id}/vote registers the vote against the supplied idea.

POST /ideas/{id}/vote on the idea ID 'idea-456' to register an endorsement from the authenticated user.

AI Agent for Innovation Coordination

An LLM agent acts as an innovation programme assistant — collecting ideas from conversations, deduplicating against existing submissions returned by GET /ideas, and posting new ones via POST /ideas. Through Jentic, the agent searches by intent and executes without holding the raw API key.

Compare a new idea draft against the list returned by GET /ideas; if no near-duplicate exists, POST /ideas to submit it.

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for innos api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/ideas

List all ideas

POST

/ideas

Submit a new idea

POST

/ideas/{id}/vote

Vote on an existing idea

GET

/ideas

List all ideas

POST

/ideas

Submit a new idea

POST

/ideas/{id}/vote

Vote on an existing idea

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The innos API key is stored encrypted in the Jentic vault (MAXsystem) and injected at execution time. Agents call innos operations through scoped Jentic credentials and never hold the raw key.

Intent-based discovery

Agents search Jentic with intents like 'submit an idea' or 'vote on an idea' and Jentic returns the matching innos operations with their input schemas, removing the need to read the docs for a small but specific API surface.

Time to first call

Direct innos integration: under an hour given the small surface area. Through Jentic: minutes — credentials and schema lookup are handled centrally.

FAQs

Specific to using innos API through Jentic.

Why is there no official OpenAPI spec for innos API?

innos does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call innos API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the innos API use?

The innos API uses an API key passed in the 'Authorization' header on every request. Through Jentic, the key is stored encrypted in the MAXsystem vault and injected at runtime so the agent never sees the raw value.

Can I submit an idea to innos through the API?

Yes. POST /ideas accepts the idea fields (title, description) and returns the new idea ID. The same endpoint is used whether the submission originates from a chatbot, an intake form, or an internal automation.

What are the rate limits for the innos API?

Rate limits are not encoded in the spec; they are enforced per API key on the innos side. Contact innos support via innos.io for the current limits applied to your account.

How do I cast a vote on an idea through Jentic?

Search Jentic for 'vote on an innos idea' to find POST /ideas/{id}/vote. Load the schema, supply the idea ID, and execute. The vote is recorded against the authenticated API key's user. Get started at https://app.jentic.com/sign-up.

Can I retrieve a single idea by ID?

The current spec exposes GET /ideas (list), POST /ideas (submit), and POST /ideas/{id}/vote (vote). Retrieving a single idea is done by listing and filtering on the client side, or by inspecting the response of POST /ideas at submission time.

innos API

Connect the innos API to your agent

Capabilities

Start building with innos API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs