Who can connect 44API for the company?

A company connection is installed by an administrator.

Can I connect 44API just for myself?

Anyone can install a personal connection within the plan’s limit and use it in their own conversations.

Do I use my 44API account or a company account?

Yours: 44API requires an API key, and each person registers their own, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.

Does Skyller do everything on that action list?

The list is what the vendor offers. What the AI uses in your company is what the administrator turned on, for the groups they defined — Skyller never widens the connector's access.

Does an action in 44API happen without anyone approving it?

Reads happen within permission. Write actions have a risk level; sensitive ones show a confirmation card before running and are recorded. The company adjusts the classification when needed.

44API does not show up in my company's catalog.

The administrator may have hidden the integration for your company, or the vendor may have discontinued it — in that case it leaves the catalog on the next synchronization, without deleting what was already connected. Talk to whoever administers Skyller in your company.

Integration · Finance and payments

44API in Skyller.

Connect 44API to Skyller and the AI starts reading from and acting in it through the functions your company enables — with each person's own login, approval before sensitive actions and a record of every call. Below, the actions and events the vendor publishes, what it takes to start and where this fits into the work.

Try it free Book a demo

Actions and events

44API

Finance and payments

44API validates VAT and tax identifiers, returns available company details, and manages account IP whitelists.

Actions: 4
Events: 0

Source: Composio catalog
Login: API key
Country: Global — no specific country
Actions list: re-read from the vendor every 24 hours
Official site: 44api.dev

Description and action names are the ones the vendor publishes, in English; action descriptions are shown summarized. Skyller does not alter that content.

4 ACTIONS

published by the vendor; the company enables only the necessary ones

0 EVENTS

triggers the system can send, when the vendor offers them

API KEY

each person signs in with their own credential, encrypted

APPROVAL BY RISK

sensitive actions show a card before running

Live proof

One request, one query in 44API and one approval.

The scene shows the path of a request; the exact actions depend on the functions your company enables in 44API.

Input
A team member asks, in the conversation, for something that today requires opening 44API — inside their area's space, with their login.
What Skyller does
1. 01Picks, among the enabled functions, a query action and looks the information up in 44API with the person's own credential.
2. 02If the request requires writing something in 44API, shows the card with what it is about to do and waits for Approve.
3. 03Returns the result in the conversation and records who asked, which action was used and when.
Result
44API stops being an open tab and starts answering inside the conversation — through the functions your company enabled.

What this scene does not promise

The available actions are the ones the vendor publishes for 44API; in your company only the functions turned on by the administrator are available.
If a write action is not classified as sensitive, it may run without a card; the classification is adjustable by the company.
Being in this catalog does not mean being installed, with a valid login, working in your company.

Illustrative scene with fictitious data; no action is named because the choice depends on the functions your company enables.

Where this helps your work

44API inside the conversation where the work happens.

Three common situations for people who use 44API every day. What Skyller does in each one depends on the functions your company turns on.

Reconciling

“Which September charges are still open?”

The analyst asks and Skyller queries 44API with her login and lists the pending charges, checking them against the published collection policy.

Charges in the conversation

Recording

“Create the charge for this customer.”

Creating a charge is a sensitive action: Skyller shows the card with customer, amount and due date and only creates it in 44API after Approve.

Charge with approval

Administering

“Reading is fine; refunding only with approval and only for the right role.”

The administrator turns on reading for the team and keeps refund and cancellation off or restricted to a group. Every call to 44API goes in the record.

Function by function

Actions and events

What the vendor offers in 44API.

Names as the vendor publishes them, in English, with the description summarized to its first sentence. In your company, the administrator turns on only the necessary actions; none of them runs without permission, and sensitive ones go through approval.

Showing 4 of 4

Add Whitelisted IP
44API_ADD_WHITELISTED_IP
Add one IPv4 or IPv6 address to the account whitelist using a verification email address. Requires an Enterprise 44API plan. The request contract is documented, but a successful addition has not been live-verified.
List Whitelisted IPs
44API_LIST_WHITELISTED_IPS
List IP addresses currently allowed by the account whitelist. This operation requires an Enterprise 44API plan; the API rejects lower-tier accounts.
Remove Whitelisted IP
44API_REMOVE_WHITELISTED_IP
Remove one IPv4 or IPv6 address from the account whitelist. This destructive operation changes account access controls and requires an Enterprise 44API plan.
Validate VAT Number
44API_VALIDATE_VAT_NUMBER
Validate one VAT or tax ID for a supported country and return its validity plus any company details available on the connected plan.

Before you start

What your company needs to use 44API.

Login: Each person enters their own 44API API key, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.
Who installs: An administrator connects 44API for the company and shares it with people or groups. Anyone can connect just for themselves, within the plan's limit.
Functions: 4 published actions: the administrator turns on only the necessary ones. Sensitive ones ask for confirmation before running.
Plan: Counts as a company or personal connection within the plan's allowance; the larger plans have no cap. The connections-per-plan table is on the catalog page.

Questions from the people who decide