Integrations / Your own APIs
Custom API
Connect any system with an ordinary HTTP API by telling Jigward about it. Nobody writes an integration.
What Jigward can do in Custom API
-
Draft operations from the documentation
It reads the API's documentation on the public web and works out the operations it needs, named and described for its later work.
-
Change the draft by talking
In plain language, on the integration's page. Nobody edits a definition.
-
Call operations from any work
Tasks, Chats, mentions and a Duty's wakes in the integration's Context can call what an admin applied.
-
Show what changes data
An operation whose method is not GET or HEAD is marked as changing data, for the admin and for Jigward.
-
Sign in the way the API does
A header, a query parameter, a user name and password, or a client id and secret exchanged for a short-lived token.
-
Record every request
Before it is sent, with its operation, its path and the outcome, for members to see.
How teams use it
-
Let a Duty use a service you rely on
Say what to connect and why. Jigward drafts the operations, an admin applies them, and the Duty can call them on every wake.
For example: The asteroid weather service we use, so a Duty can warn us about meteor showers on our routes.
-
Start it where you are
Any member can start one from Integrations, in a Chat, by giving a Task, or by mentioning Jigward in a channel.
For example: Connect our status page's API so you can check it before a release.
What you need
- An HTTP API on a public address, with its documentation on the public web.
- Its key or credential, and an admin to enter it.
Not built yet, by the product's own list. MCP servers, webhooks from these systems, and OAuth that needs a browser redirect.
Connecting it
- A member says what to connect and what it is for. The integration's page opens with Jigward already working.
- Jigward drafts the operations there. Change them by talking to it.
- An admin enters the API's address and key in a form and applies the draft.
Security and access
-
An admin applies it
Jigward drafts and says where the API lives. An admin enters the address and key, so an address found on a page never gets a key on Jigward's word alone.
-
The key never reaches the model
Stored encrypted and bound to the addresses it was entered for. Jigward puts it into the request itself, and masks it in whatever the API answers.
-
Never shown again
The key is never returned or logged, and a short-lived token lives in memory only.
-
Public addresses only
A call to an address that is not public is refused, and so is a redirect.
-
A draft only reads
Trying out a draft is held to reads. The operations in use keep working until an admin applies a new one.
-
Every request on the record
Recorded before it is sent, without its query, headers, body or answer. Members see the list on the integration's page.
Jigward never does these in Custom API
- Send a key to an address it was not entered for.
- Call a private address, or follow a redirect.
- Try out a write while the draft is only a draft.
Other integrations
Custom API is a trademark of its owner, and naming it does not mean it endorses Jigward.
Meet your next engineering coworker
Bring a question
from your own project.
See how Jigward can help your team understand the system and move the next task forward.
Jigward is in closed testing. Accounts are created by hand; sending a request does not create one.