Integrating with Dyflexis turns the workforce data your customers already manage, schedules, worked hours, payroll, and absence, into something your product can act on automatically. Here's the value the partnership creates, before you work through the steps below.
For your shared customer
- Automation instead of manual work. Workforce data flows between Dyflexis and your product automatically, with no exports, re-keying, or copy-paste, so there's no double entry and far fewer errors.
- One source of truth. Schedules, worked hours, payroll, and absence stay in sync across both systems in near real time, so everyone is working from the same numbers.
- Onboarding that just works. The integration is connected once and runs in the background, with no project for the customer to manage.
What you gain as a partner
- Less churn. A live Dyflexis integration becomes part of the customer's daily workflow. Once their workforce data flows through your product, switching away means giving up that automation, so integrated customers are markedly more likely to stay.
- More automation to offer your customers. The API lets you remove manual steps from your customers' workforce processes, automation they can't get from your product on its own, which makes your offering measurably more valuable and harder to replace.
- A larger reachable market. Publishing to the Dyflexis Marketplace puts your integration in front of every Dyflexis customer looking to connect the tools they already run.
We want your experience working with Dyflexis to be quick and simple, so we make the process as automated and self-service as possible and minimise touchpoints with the Dyflexis team. You just need to follow these steps:
- Explore the APIs
- Let us know what you plan to do
- Develop and test your solution
- Get certified
- Go live with a pilot
- Join the Marketplace
If you have questions about the process, drop us a line at integrations@dyflexis.com.
First find out which of our endpoints you should be using. If you're not sure, take a look at the use cases for suggestions. Each resource has its own body of documentation in this reference, so you'll want to familiarize yourself with the guidelines and operations for the resources you'll be using.
Once you've had a chance to familiarize yourself with the APIs and the process, you will be asked to complete a short qualification step to answer some basic questions:
- Which endpoints will you be developing against?
- Is this a private integration (for just one enterprise customer) or a public integration (available through the Dyflexis Marketplace)?
- If this is a public integration, what will be the pilot customer?
- What is your estimated timescale for development?
Once we've worked through these questions together, Dyflexis provisions a dedicated sandbox tenant for your integration. The sandbox is an isolated Dyflexis environment with its own system name, API tokens, and seeded test data, so you can develop and test end-to-end without touching live customer data. You'll receive the sandbox system name and credentials in the partner portal as soon as provisioning is complete, and the sandbox stays available throughout development, certification, and the pilot.
When you've decided which endpoints to use and how, you'll develop against the sandbox tenant provisioned in Step 2; its credentials are available in the partner portal. All of the information you need to start developing and testing is in this reference: base URLs, authentication, scopes, and per-endpoint request/response schemas with multi-language code samples.
When you are finished developing and testing, it's time to get certified. Complete the certification form in the partner portal and we'll send you further instructions by email. As part of the certification process, you will be asked for some details about your integration, such as the endpoints you will be using and the request message frequency.
After successful certification, you will be sent a production Client Token for connection to live tenants, this token is unique to your application. To connect to a customer tenant, you will also need a tenant-scoped Access Token issued by that customer.
Tokens are sensitive. Tokens are your security keys to access customer data in Dyflexis. Store them safely and securely, do not share them, and do not put them into email communication.
- Public integration. If your integration is intended to be listed publicly in the Dyflexis Marketplace, Dyflexis will connect the integration to the agreed pilot customer and you will automatically be sent the relevant Access Token. The integration will need to run successfully for a period of time on the pilot site (typically 2 weeks) before we can progress to publication.
- Private integration. If this is a private integration to a single enterprise, Dyflexis will connect the integration to the relevant tenants and you will automatically be sent the relevant Access Tokens. Although there is no pilot site, we will still monitor the performance of the integration for a period of time to confirm everything is okay.
If your integration is intended to be listed publicly in the Dyflexis Marketplace, then after the agreed monitoring period of successful operation at the pilot customer, you will automatically be notified by email with final instructions. Your solution will be listed on the Dyflexis Marketplace and you can roll it out to all customers that want to integrate.