Reference · built on requestConnectorERP & finance

Infor CloudSuite

ERP application APIs from Infor CloudSuite, brokered by the Infor OS API Gateway (ION API) with OAuth 2.0 tokens.

Request accessPricing ↗

About

Infor CloudSuite is a family of industry ERP suites that run on Infor OS. Their APIs are not called directly. API Gateway, also called ION API, sits in front of them as a reverse proxy with one base URL per tenant, one authentication server, and a catalogue of API suites. Each suite is a set of endpoints with its own documentation, and a tenant sees only the suites it is authorized to use.

An operator on Fibric holds an authorized app in your tenant, reads endpoints from the suites you grant, and proposes writes or API Flow runs for your approval. Each proposal leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Infor CloudSuite and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Endpoints of Infor Provisioned API suites, read through the tenant's ION API base URL
  • Per-endpoint REST documentation at the endpoint path plus /ionapi-doc, or ?WSDL for SOAP endpoints
  • Active API flows built in ION, listed as endpoints in the Infor API Flows suite
  • Non-Infor API suites you add to the gateway, including on-premises targets reached through Enterprise Connector
  • Gateway monitoring, request-response logging, and API suite tracing for calls made through the tenant

Proposed actions

  • Target capability: propose a POST to a write endpoint of a granted Infor API suite, using the operation the endpoint documentation lists
  • Target capability: propose running an API flow endpoint synchronously, or with ionapiRespStyle=async and result pickup within 2 hours

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Match a receipt to its order and invoice

    Read purchase orders, receipts, and supplier invoices from your CloudSuite suite and propose a match or a hold for the reviewer.

    With Three-Way Match, Receipt Not Invoiced

  • Draft a replenishment order from the ERP's own numbers

    Read on-hand stock and open orders through the suite endpoints, draft a purchase order, and post it only after approval.

    With Purchase Order Draft, Reorder Point

  • Chase late inbound orders

    Compare promised dates on open purchase orders with receipts and propose a supplier follow-up with the order lines attached.

    With PO Chase, Inbound Delay

Requirements

  • An Infor OS tenant with API Gateway and a user holding the IONAPI-Administrator security role to register the app
  • A backend service authorized app; its downloaded credentials file holds the tenant, client ID, secret, and base URLs
  • A service account (SAAK and SASK) for back-channel token requests with grant_type=password
  • If scopes are enforced in the tenant, the service account must carry the scopes the token request names
Authentication
An authorized app registered in API Gateway (OAuth 2.0 client ID and secret) plus a service account access key and secret key for the resource owner grant.

Limits

  • Access tokens last about two hours; a refresh token is needed for longer sessions
  • The gateway waits 60 seconds for a target API by default, extendable to 5 minutes by policy; 504 on timeout
  • Quota and Throttling policies on a suite return 429 once the configured request count in a period is reached
  • Buffered policies cap payloads at 10 MB; Enterprise Connector to on-premises targets caps them at 5 MB

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Infor CloudSuite ↗

Questions and answers

Which grant type does a server-to-server integration use?
The resource owner grant. The app posts grant_type=password to the token endpoint with the service account access key as username, the secret key as password, and its own client ID and secret. No user is present for the exchange.
Where is each endpoint documented?
In API Gateway under Available APIs: open the suite, then Endpoints, then Documentation. Programmatically, append /ionapi-doc to a REST endpoint path or ?WSDL to a SOAP endpoint. Both documentation URLs need the same bearer token as the endpoint itself.
Can the gateway reach an on-premises application?
Yes, through Enterprise Connector on Cloud Edition. The API Gateway hybrid service runs inside the connector, needs no direct inbound network connection, supports payloads up to 5 MB, and requires the enterprise location to be provisioned in ION first.
Ask about Infor CloudSuite

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Infor CloudSuite through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy