What does Pandium require from developers?

When collaborating with Pandium, your developers have a singular task: coding the business logic and configurations for your product integrations. Even a junior developer can accomplish this task in just a few hours.

The Pandium platform takes care of everything else, including authentication, logging, hosting, alerting, versioning, runtime environment, and sync triggers.

If your development resources are limited, our Integration Team can do this work for you.

How does Pandium fit into existing dev processes?

Developers have the flexibility to code the business logic for an integration using any preferred language or text editor. Pandium connects to different repositories like Github, Gitlab, Azure DevOps, and Bitbucket to manage configurations and sync options within Pandium's (user interface) UI.

Once configuration and sync options are pushed to Pandium’s UI, Pandium Administrator users —whether technical or non-technical—can make informed decisions. They can select specific flows or integration versions for deployment, add tenants, review sync history, adjust configurations, and run manual syncs.

Additionally, connectors, release versions, and configurations in Pandium can be reused to launch future integrations faster.

What programming languages do you support?

Pandium is a language-agnostic platform, offering the flexibility to write integrations in a variety of common languages. This includes but is not limited to Clojure, Go, Java, JavaScript, TypeScript, PHP, Python, and Ruby.

Our commitment extends to consistently supporting the Long-Term Support (LTS) versions of each language. If you notice anything that seems outdated or malfunctioning, please let us know!

How does the integration script code get into Pandium?

Pandium sets up a Source Control process with your source code repository. Pandium ingests your script when relevant code is updated in your repository. A new release will then be created that you can apply to your tenants as soon as you are ready.

Do you support webhooks and event-based integrations?

Absolutely, we do. Webhooks serve as just another trigger within our system, and we go a step further by consolidating sequentially firing webhooks into a single run for enhanced efficiency.

Webhooks, essentially HTTP callbacks, are processed and sent to Pandium through a designated URL. A webhook request sends a payload that can be used in the context of a Pandium sync, agnostic of scheduling. Typically, each webhook has a resource, outliningthe information payload, and an event, which serves as a trigger for sending the request.

Note on creating webhooks:

*If your API supports programmatic creation of webhooks, they can be created and corresponding events can be selected directly within the Pandium UI.

Does Pandium support batch/polling style integrations?

Yes, you and your users have the flexibility to establish discrete sync schedules per integration or tenant, allowing for customization based on specific requirements.

How many tenants can you have on a single integration?

Pandium offers the flexibility of accommodating an unlimited number of tenants to operate on a single integration.

The exception to this is lies in Pandium Lite, where the account is limited to 25 tenants.

What is a Connector in Pandium?

A connector in Pandium is an integral component added to an integration, empowering Pandium to furnish the necessary encrypted secrets or tokens to the combination of integration and tenant.

In contrast to many integration platforms, Pandium’s connectors do not interact with external APIs beyond authorization, authentication and receiving webhooks. This design choice eliminates the existence of a "Pandium version" or an additional layer as a "wrapper" around third-party APIs.

A Pandium connector will respect the authentication needs of partner systems, whether that is an OAuth protocol, a simple API key, or something proprietary or bespoke.

Learn more about our connectors here.

How do you store secrets?

Secrets within Pandium are encrypted both at rest and in transit. They are dynamically injected at run-time as environment variables after being refreshed, if needed, ensuring a robust and secure handling of sensitive information

What if a partner API changes? How is that handled?

All changes needed to support authentication and authorization will be handled by Pandium.

Changes in shapes of data or versions of an API are handled by the writer of the integration.

Simply update your script and push to your repository, triggering the creation of a new release on the platform

Does Pandium need a public API to work?

Pandium is agnostic to whether an API is public or private. It accommodates public or private APIs, SFTP connections, or even direct database connections,, as long as we have appropriate access.

How are the frontends handled for our in-app marketplace or integration?

Pandium takes care of generating a user-facing frontend automatically based on the associated Pandium.yaml. This enables your customers to begin using your integration on the very day the script is published to the platform.

Pandium features a set of theming options in our UI to enable your marketing team to customize the marketplace with your branding. Additionally, options are available for managing and updating marketing copy or instructions throughout the marketplace installation experience.

Does Pandium offer a sandbox or developer account?

Yes, Pandium provides a sandbox account as part of the onboarding process. This account offers a secure environment for building and testing integrations and other features without impacting live data.

What Makes Pandium Scalable?

Pandium's scalability is attributed to a unique design approach. Unlike many integration platforms, Pandium's connectors exclusively handle tasks related to authorization, authentication, and receiving webhooks. Meaning, there is no “Pandium version” or “wrapper” around third-party APIs.

This allows access to the full flexibility of the systems you are connecting. Learn more about how Pandium’s platform structure supports this here.

Once an integration and its configurations are surfaced on Pandium, they can be effortlessly reused and deployed to numerous users. This offers options for deploying customer-specific configurations, streamlining the process of launching integrations and contributing to a faster deployment cycle.

How is logging handled? Can you send info to an APM?

Logs printed to stderr in your script are automatically captured by the platform, visible to Pandium users and end customers for inspection.

If you want to send any logging information to an Application Performance Management (APM) system such as AppInsights, Coralogix, HubSpot, or others, Pandium supports this and will seamlessly integrate it into your system to ensure you have access to the necessary information.

How can I Pass State between runs?

Integration scripts can pass their state between successful runs by writing a JSON-encoded string to stdout. This string will be presented to the next invocation of your script as an Environment Variable.

You can use this process to save the sync state between runs, facilitating the ability to run large syncs and pick up from where the last operation left off.

Last updated