Ivalua

Bring-your-own-tenant Ivalua procurement: suppliers, requisitions, POs, invoices and contracts through guarded calls to your tenant's API.

5 actions token_login 1 read3 write1 destructive Calls www.ivalua.com

Connect

TypeScript

const conn = await setu.connections.initiate({ userId: "user_1", toolkit: "ivalua" });
console.log(conn.connectUrl); // show this to your user
await conn.waitUntilActive();

Permissions requested

This toolkit uses a single credential and requests no scopes.

Actions

Delete (Ivalua interface)destructiveivalua.deleteSend a DELETE request to an interface path of your Ivalua tenant to remove a record. Destructive. This is a generic, guarded call: Ivalua's web services are configured per tenant, so the real paths come from the customer's own interface list (or Swagger) and Setu has no built-in list of them. Typical object families an Ivalua tenant may expose: suppliers, requisitions, purchase orders, invoices, contracts, sourcing events and approvals. If you do not know the interface path for what the user wants, ask the user for it; never guess a path. The path is relative to the tenant's Ivalua API address and must start with /. The linked page is Ivalua's Integration Toolbox PDF, a capability description (REST/JSON web services), not an endpoint reference. Not verified against a live Ivalua tenant.

Input	Type		Description
`path`	string	Required	REST path of the interface, relative to the Ivalua API address, starting with / (given by the tenant's administrator; do not guess)
`query`	object	Optional	Plain query parameters (text or numbers) such as filters or paging, as the tenant's interface defines

TypeScript

await setu.execute({
  userId: "user_1",
  action: "ivalua.delete",
  input: {
    "path": "<path>"
  },
  confirm: true,
});

Get (Ivalua interface)readivalua.getRead data from your Ivalua tenant with a GET request to an interface path you were given. This is a generic, guarded call: Ivalua's web services are configured per tenant, so the real paths come from the customer's own interface list (or Swagger) and Setu has no built-in list of them. Typical object families an Ivalua tenant may expose: suppliers, requisitions, purchase orders, invoices, contracts, sourcing events and approvals. If you do not know the interface path for what the user wants, ask the user for it; never guess a path. The path is relative to the tenant's Ivalua API address and must start with /. The linked page is Ivalua's Integration Toolbox PDF, a capability description (REST/JSON web services), not an endpoint reference. Not verified against a live Ivalua tenant.

Input	Type		Description
`path`	string	Required	REST path of the interface, relative to the Ivalua API address, starting with / (given by the tenant's administrator; do not guess)
`query`	object	Optional	Plain query parameters (text or numbers) such as filters or paging, as the tenant's interface defines

TypeScript

await setu.execute({
  userId: "user_1",
  action: "ivalua.get",
  input: {
    "path": "<path>"
  },
});

Patch (Ivalua interface)writeivalua.patchSend a PATCH request to an interface path of your Ivalua tenant to change part of a record. Changes data in Ivalua. This is a generic, guarded call: Ivalua's web services are configured per tenant, so the real paths come from the customer's own interface list (or Swagger) and Setu has no built-in list of them. Typical object families an Ivalua tenant may expose: suppliers, requisitions, purchase orders, invoices, contracts, sourcing events and approvals. If you do not know the interface path for what the user wants, ask the user for it; never guess a path. The path is relative to the tenant's Ivalua API address and must start with /. The linked page is Ivalua's Integration Toolbox PDF, a capability description (REST/JSON web services), not an endpoint reference. Not verified against a live Ivalua tenant.

Input	Type		Description
`path`	string	Required	REST path of the interface, relative to the Ivalua API address, starting with / (given by the tenant's administrator; do not guess)
`query`	object	Optional	Plain query parameters (text or numbers) such as filters or paging, as the tenant's interface defines
`body`	object	Optional	JSON body, shaped as the tenant's interface defines

TypeScript

await setu.execute({
  userId: "user_1",
  action: "ivalua.patch",
  input: {
    "path": "<path>"
  },
});

Post (Ivalua interface)writeivalua.postSend a POST request to an interface path of your Ivalua tenant, for example to create a record or push data in. Changes data in Ivalua. This is a generic, guarded call: Ivalua's web services are configured per tenant, so the real paths come from the customer's own interface list (or Swagger) and Setu has no built-in list of them. Typical object families an Ivalua tenant may expose: suppliers, requisitions, purchase orders, invoices, contracts, sourcing events and approvals. If you do not know the interface path for what the user wants, ask the user for it; never guess a path. The path is relative to the tenant's Ivalua API address and must start with /. The linked page is Ivalua's Integration Toolbox PDF, a capability description (REST/JSON web services), not an endpoint reference. Not verified against a live Ivalua tenant.

Input	Type		Description
`path`	string	Required	REST path of the interface, relative to the Ivalua API address, starting with / (given by the tenant's administrator; do not guess)
`query`	object	Optional	Plain query parameters (text or numbers) such as filters or paging, as the tenant's interface defines
`body`	object	Optional	JSON body, shaped as the tenant's interface defines

TypeScript

await setu.execute({
  userId: "user_1",
  action: "ivalua.post",
  input: {
    "path": "<path>"
  },
});

Put (Ivalua interface)writeivalua.putSend a PUT request to an interface path of your Ivalua tenant to replace or update a record. Changes data in Ivalua. This is a generic, guarded call: Ivalua's web services are configured per tenant, so the real paths come from the customer's own interface list (or Swagger) and Setu has no built-in list of them. Typical object families an Ivalua tenant may expose: suppliers, requisitions, purchase orders, invoices, contracts, sourcing events and approvals. If you do not know the interface path for what the user wants, ask the user for it; never guess a path. The path is relative to the tenant's Ivalua API address and must start with /. The linked page is Ivalua's Integration Toolbox PDF, a capability description (REST/JSON web services), not an endpoint reference. Not verified against a live Ivalua tenant.

Input	Type		Description
`path`	string	Required	REST path of the interface, relative to the Ivalua API address, starting with / (given by the tenant's administrator; do not guess)
`query`	object	Optional	Plain query parameters (text or numbers) such as filters or paging, as the tenant's interface defines
`body`	object	Optional	JSON body, shaped as the tenant's interface defines

TypeScript

await setu.execute({
  userId: "user_1",
  action: "ivalua.put",
  input: {
    "path": "<path>"
  },
});