With Affix API, implementation teams at HR/Payroll companies can enable new customers to extract their data from their former HR or Payroll system in just a few seconds.

As you likely know, your customers' former provider doesn't want to make it easier for customers to churn, and as such likely doesn't provide access to their official API.
‍
Instead of using the official API of the provider, Affix builds its own API into these systems, accessing the public but non-documented APIs that connect the systems frontend to the back end.

As a result, data extraction can now happen via API. Customers can simply extract their data in 4-clicks, by selecting their former provider and entering their username and password to their former system, in a Plaid-like interface. You get the data back in 30 seconds. Because it's effortless for customers, you no longer have implementation delays.

You get the data back in one standardized format, no matter where customers are coming from. We map the providers' data models to ours, so you only need to work off of the Affix data model. You can get the data back in a CSV. If you want to go further, you can bring in an engineer to add the Affix API, so your team receives the data in the customers' new account, automating the ETL process.

We enable you to get all the data you need, without the back and forth. We have expected values in our schema to ensure you only get the data you'd expect to receive, where you'd expect to see it. And, we can enable you to extract all the data you need. We have full access to these systems, so even if you don't see the data you need in our docs, we can add a new field or endpoint to provide access to it. This means no more back and forth, and slashed operational costs.
‍
In summary: with Affix API, you get the data back in seconds, in a standardized format, accurately. Without delays and without the implementation costs.

No. Any cloud system, even if it doesn’t have a publicly available API, still has an API that connects the systems’ back-end to its front-end. Affix uncovers this internal API, and integrates directly into it, rather than using the API of the underlying provider. Our engineers have deep experience in this space, and there is no quick way for a company to block it. The result is you can use this API to migrate data for new customers without doing so in a manual, costly, process.

Affix is designed to be extremely intuitive. Your customers will click a button in your dashboard that links to the Affix connect flow. Affix will ask them to enter their credentials for their payroll or HRIS. They connect once, providing long-lived access. This will take them less than 20 seconds. You can see it in action here.

Nope. To your competitor, it’ll simply look like the user had logged in. Your customer can port their data out of their system and into yours in under 30 seconds, and your competitor will be none-the-wiser.

In your onboarding flow, your new customer would click a button to migrate their data, and the Affix modal would pop up. The user would be prompted to select their system, enter their credentials, and provide consent to you to use Affix to migrate their data. Affix would then pull their data into your system in less than 30 seconds. 

Just one, with us. You integrate with Affix once, and you’ll have integrations with dozens of other payroll and HRIS out of the box. Any integration you need that Affix doesn’t have, we build it for you. When compared to negotiating integrations with the provider themselves, and the labor cost of spending weeks integrating, the time difference is massive.

Adding Affix is easy. If you have a developer that is familiar with Oath, they should be able to add it in an hour or so. If you already use OAuth integrations, such as Plaid, it’s very easy to integrate Affix, as there are familiar paths to follow. 

It's on your team to know where you'll migrate the data to in your product. This may take a little longer, maybe a couple weeks, depending on your system and how clear your product team is on where the data is going.

We have a sandbox token publicly on our docs that your engineers can start using and integrating right now: https://docs.affixapi.com/#topic-sandbox-keys-developer-mode

‍We also have SDKs in whichever language you use for your back end. For the front end, we have a drop-in React library– you just add it to your dependency, which gives you a button to allow users to connect their HR/Payroll system. We also have an html snippet you can add to your page. 

In addition to our sandbox, we also have a pre-production environment, as well as a starter kit to provide code examples. 

We provide all the resources to make adding Affix easy.

Yes! We have both a development environment (also referred to as pre-prod or staging environment) and a production environment, as well as a sandbox. Additionally we have demo accounts for several systems which you can test.

The JSON Web Token (JWT) we issue has the scopes that our customer authorised. Our Authoriser service validates that 1 ) the JWT is correctly signed and 2) the JWTs contain the scopes to authorise the endpoint.

Yes! Use your own account to test our system or use one of our demo accounts. You can also use our sandbox.

Yes. Our uptime is between 99%  - 100% for the past three months, depending on the specific service. You can follow it here: https://status.affixapi.com/ 

You call our API. When you make a call to us, that turns into a live request to the provider. There is no “data sync/synchronisation process,” like other unified APIs. However, we do have webhooks. In this case, you don’t need to call our API for changes –  we’ll let you know when something’s been changed. 

You can get data back at any interval you’d like, and even in real-time. Our system is designed differently from other API aggregators’ like Merge and Kombo. We don’t store data and we don’t have a synchronisation process. You call our endpoint and you get the data back in real-time, or you can enable webhooks and we can let you know when something’s been changed. We can update you at any interval or in real-time.

No.

We have a disconnect endpoint. This will wipe all the data in the token.

Our system is designed differently from API aggregators’ like Merge/Kombo. We don’t store data and we don’t have a synchronisation process. You call our endpoint and you get the data back in real-time. When you make a call to us, that turns into a live request to the provider.

We also have webhooks - in which case we will let you know when something’s been changed, rather than you calling our endpoints. How this works is we configure JWTs to run at a certain interval, store data in a temporary cache (with TTL set); detect if there’s been a diff, and then send you the diff’d records. That interval can be 1 hour, 6 hours, 12 hours, once a day, or any other interval you’d like. 

Yes. Affix is ISO27001 compliant, and we’re currently undergoing our ISO ISO27001 audit to receive our certification, which should be by February 10, 2024 at the latest.

No. Affix does not scrape copyrighted data like photographs or text paragraphs for reproduction. The data collected by Affix wouldn't be subject to copyright as it doesn't meet the standard of originality, creativity, and authorship.

Affix doesn't infringe on database rights, because the data is factual or non-original.

No. Affix operates as an intermediary between the end user, the HR/payroll providers, and our customer. Any action taken by an HR/Payroll system would be against Affix, not its customers, and would be about a policy violation, rather than a legal one.

Affix is designed to avoid detection in the first place. From our experience, if the providers notice the activity, the most aggressive action they take is to increase the technical challenges Affix needs to make in order to access the data, such as bot challenges, or attempting to ban IP ranges of Affix’s servers.  Between the resources needed to do so, and the risk of churning their customers, the payroll providers are not too likely to, let alone discover it’s happening to begin with. However, even if they were to, that’s something Affix is experienced with and would be able to overcome in short-order.

Yes, Affix is GDPR compliant, does not violate copyright or trademark rights, and is built with security at the forefront of design decisions. While the areas of law are complex, Affix has barristers registered in England, Wales, and Ireland on its advisory council, is in good legal standing, and operates with due diligence. 

Yes– Affix has public indemnity insurance, cyber insurance, directors and officers insurance, and employer liability insurance as well. 

At Affix, our success is directly aligned with our customers. As such, we believe in fair and transparent terms. For any partnership we enter, we establish mutual agreements on pricing that provide protections from unfair price hikes, providing for long-term, mutually beneficial partnerships.

Affix is designed from the ground up by an engineer to be the API that an engineer would want to use. It makes data migrations easy. It's intuitive, it just works, and it gives you everything you could need such as canaries, industry standard endpoints, and webhooks.

And, it's secure and compliant. Affix is serverless and doesn't store sensitive employment data. If you enable webhooks, there's a brief cache, but it's heavily encrypted. We are GDPR compliant, and ISO 27001 certified.

Lastly we provide free, no-risk trials. No set up fee. No fee per API call. With pricing that fits your business.‍

Affix is live now. Claim your place for onboarding by booking a discovery call with our team below.