44API for AI agents
Agents read 44API at once. Changes and sends are held for a person's approval by default.
About 44API
44API validates VAT and tax identifiers, returns available company details, and manages account IP whitelists.
What an agent can do in 44API
Every 44API action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in 44API without asking first. 2 actions.
- List Whitelisted IPsList IP addresses currently allowed by the account whitelist. This operation requires an Enterprise 44API plan; the API rejects lower-tier accounts.
- Validate VAT NumberValidate one VAT or tax ID for a supported country and return its validity plus any company details available on the connected plan.
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 2 actions.
- Add Whitelisted IPAdd 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
- Remove Whitelisted IPRemove one IPv4 or IPv6 address from the account whitelist. This destructive operation changes account access controls and requires an Enterprise 44API plan. The shared whitelist endpoint's Enterprise
Changes wait in Needs you
Changes and sends in 44API are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
Related connectors
44API questions
Can an agent change data in 44API on its own?
Not by default. Changes and sends in 44API are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in 44API?
This connector lists 2 read actions. Reads run at once, without waiting for approval.
How does 44API connect?
It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.