How to Integrate Fuuz with another product or another API

How to Integrate Fuuz with another product or another API

This document guides users, customers, prospects, partners, and employees through the journey of identifying and gaining access to another software application using API calls. If you are unfamiliar with the general idea of APIs, it is recommended to start here: What is an API?

FAQ

1. I would like to integrate Workday with Acumatica — why am I reading this document?
   • In order to get data from one system into another, you must call Workday from Fuuz, then push the data from Fuuz into Acumatica.
2. I googled "Company Name API" and could not find an API — how do I integrate?
   • This doesn't mean an API doesn't exist; some companies hide their APIs.
   • Smaller companies don't have public access to APIs.
3. The company said they "support integration but they don't write APIs." How is that possible?
   • Most companies that support integration in some form have an API.
   • What the company probably means is that they don't write "integrations" or calls to other companies. That is how we help.
4. Company A (source of data, e.g. Workday) introduced us to Company B (partner/integration company, e.g. Bob's Consulting LLC) to talk to Company C (destination system, e.g. NetSuite). Why should I use Fuuz instead?
   • In this example, Company B will need a platform like Fuuz to get the job done.
   • Company B is often familiar with your vendor (Workday) but not your system (NetSuite); this can lead to delays, increased costs, and unsuccessful integrations.
   • The solution is often built with a narrow focus to solve the specific need.
   • Fuuz offers a standard platform with prebuilt solutions that can be configured to support specific requirements.

Gathering Requirements

In order to have a productive discovery, the customer must provide the following pieces of information:

1. Access — often including access to the administration of the product (e.g. workday.com) or an alternate site for APIs (e.g. developers.plex.com).
2. Documentation — often including URLs, connection methods, and security protocols. (Note: access to a site may include this documentation by default.)
3. Technical Support — often a technical contact or support website (e.g. answers.sap.com) at the company we wish to connect with. (Note: this person is often a gatekeeper for documentation and technical questions in smaller companies.)
4. A list of actions — examples include pulling users from System A to create them in System B, or pushing invoices from System B into System C.

Access

In order to get a better idea of what is possible, our team and partners need access to the third party's website. In most cases the documentation is hidden. If access is not appropriate at the time of discussion, a PDF or alternate documentation should be provided. Some systems allow admin users the ability to create users, keys, and tokens to access APIs directly within their system (e.g. NetSuite), while others require ticket submissions to generate them (e.g. Plex).

Documentation

APIs can often be hidden or "private." Fuuz hides our APIs behind user security. This is a common and safe practice for many websites. Most modern products have an API, so it is no longer a benefit to advertise an API to the public. By hiding the API documentation, products limit the knowledge on a need-to-know basis, thus reducing risk.

Typical forms of documentation from a company should answer the following questions:

1. What information does the system provide?
2. What URL(s) to call to pull information out of the system? (E.g., how do I get a list of employees?)
3. What URL(s) to call to push information into the system? (E.g., how do I add invoices from another system?)
4. How does an integration authenticate?

Technical Support

Technical support can vary from a specific contact to website access about the endpoints. This often starts with the customer reaching out to their vendor asking for information on how to integrate. It is strongly recommended that a customer email their vendor asking: "I am interested in accessing information stored in your application remotely. We have a partner capable of making API calls. Do you have documentation or a technical contact that can help us get started?"

A List of Actions

Simply put, customers need to define their specific goals. Instead of "Integrate with Workday," challenge your customers and end users with "What does that mean?" Identify areas, objects, tables, or entities.

The goal is to create a list of statements similar to these:

1. I would like to add users to Plex after they are added in ADP.
2. I would like to terminate users in Plex when they are terminated in ADP.
3. I would like to use nesting data from SigmaNest and group workorders in NetSuite.
4. I would like to push pricing changes from Acumatica into my Magento website.

See Also

• How-to-create-a-simple-Integration-and-Store-data-in-Fuuz
• How-to-Integrate-with-an-HR-system-like-ADP-using-Fuuz-iPaaS
• How-to-integrate-with-Plex-Classic-using-Fuuz-iPaaS
• Fuuz-has-pre-built-integration-Connectors
• Connecting-to-Fuuz-from-a-remote-system-to-execute-a-Fuuz-API
• Integration-Nodes

---

Source: support.fuuz.com