A Celigo APIs connection gives your flows one place to reach everything Celigo hosts in your account — custom APIs, listeners, standard integrator.io APIs, and now Celigo Storage as a built-in file provider.
Celigo APIs enable connection to custom APIs and listeners built within your account, as well as standard Celigo APIs, without requiring authentication using a Celigo API token.
Note
Only account owners or administrators can set up a connection to Celigo APIs.
After you start the connection, you have to configure it in the Create connection panel and must complete all of the required * authentication settings:
| Setting | Instructions |
|---|---|
| Name your connection * | Enter a clear and distinguishable name. Throughout Celigo integrator.io imports and exports, you will have the option to choose this new connection. A unique identifier will prove helpful later when selecting it from a list of the connections in your account. |
| Scope * | Grant the connection Full access to every custom API, listener, and integrator.io REST API in your account or use Custom to tailor access to specific APIs and listeners. |
| APIs | Select the API(s) you want this connection to access. Any user in your account will be able to invoke the selected API(s) when using this connection. |
| Listeners | Select the listener(s) you want this connection to access. Any user in your account will be able to invoke the selected listener(s) when using this connection. |
| Integrations | Select the integrations this connection can access. Appears when Integration access is selected. Non-admin users can select only the integrations they manage. |
| File storage paths | Limit the connection's Celigo Storage access to specific folders. Appears under Custom. Enter a comma-separated list of folder paths; matching is prefix-based with no wildcards, so each path also grants access to everything beneath it. Enter / to allow all paths. Leave empty for no path restriction. Existing Custom connections with no paths specified are unaffected. |
PGP encryption
The Celigo APIs connection supports PGP (Pretty Good Privacy) encryption for Celigo Storage files. When you enable PGP, flow imports can encrypt files as they're written, and exports and lookups can decrypt files as they're read. Configure PGP under Advanced settings.
- Enable PGP cryptographic — Turns PGP on for the connection. When off, the encrypt and decrypt options on flow steps are disabled.
- PGP public key - The public key used to encrypt files on import.
- PGP private key - The private key used to decrypt files on export and lookup.
- PGP passphrase - The passphrase that protects the private key.
- Compression algorithm - The algorithm used to compress files before encryption.
- ASCII armor - Turns ASCII-armored output on or off.
You can also configure PGP through the API. PGP keys and the passphrase are encrypted at rest, must be re-entered when you edit the connection, and are never returned in API responses, written to logs, or displayed after you save them.
Concurrency
- Borrow concurrency from (optional): Select another connection from the list. By default, all data flowing through a connection record is submitted to the respective endpoint application at the concurrency level configured for that connection record. There are cases, however, where multiple integrator.io connections need to share the same concurrency level, and this field allows you to specify which connection you would like to borrow from. With borrowed concurrency, the data flowing through both connections will be submitted to the endpoint application together, via a shared concurrency model.
-
Auto-recover rate limit errors: This setting is enabled by default with a predefined value for Target concurrency level. You can disable the setting if required. To set or make changes in any of these settings, you must have admin or manage permissions.
- Concurrency level: When Auto-recover rate limit errors is checked, you can't modify the concurrency level because it matches the value set by the connected platform's runtime. When Auto-recover rate limit errors is not checked, you can enter a value to limit the number of concurrent API requests allowed by the connection resource. See also, Setting currency level on a connection.