DSYNC is a developer’s tool for connecting APIs. The platform is a live data integration service that is used to connect APIs together. The platform is used by developers to map data endpoints using our interactive advanced API endpoint. Developers can quickly create endpoints to join an unlimited amount of API services together. The advanced API endpoint is configurable and enables developers to set up customized schemas or data layouts for multiple data structures that need to be connected. DSYNC is a bidirectional IPAAS platform enabling developers to setup self-service endpoints for connecting APIs together.
- Create your own API endpoint to link/ connect your API services
- Graphical data mapping engine for connecting your API’s
- Create secure AUTH tokens to connect API
- Generate different output results in JSON / XML
- Trigger data workflows
- Set schedules based on run types
- Configurable data layout schemas for integration
- Connect different data sources, web-services, CSVs or apps to communicate with your API or endpoint
- Set custom API triggers via web-hook or CRON timer
- Batch splitter for connecting APIs
- Data transformation configuration: Object, Variables, Formulas, Date changes etc
- Self-service developer tool for connecting data types
- Live data updates between API endpoints and other apps
- Self-service – API connection - No coding only data configuration
- Granular level API mapping and data connection
- Generate output reporting and self-service error logs
- Set timers or set live updates via our CRON system
- Unlimited data types
- Generate your own schemas, structures and data layouts for API connection
- Post / Get order details between your endpoints
- Connect multiple endpoints and data types
- Build additional custom API endpoints for development
DSYNC is a developer’s data integration tool that is used to connect APIs together and provide integration. DSYNC work with platforms to expand connectivity. DSYNC is a platform for developers to trigger data flows, create source and destination endpoints for integration of multiple systems and APIs. Developers can quickly set up a unique API endpoint and control data flows between unlimited amounts of APIS. DSYNC is configurable vs the need for programming and offers a dashboard for API endpoint set up and management. The platform is highly scalable and offers enterprise performance for API connectivity. Create unique API endpoints for applications to communicate
Thinking of building a connecter into DSYNC? One of the simplest ways to connect systems is to set up a new API endpoint (create system manually) and configure your system to talk to DSYNC. For a simple connection set-up developers only need to check for two key capabilities to connect the APIs.
- Authentication methods (DSYNC can connect with multiple and generic oAuths)
- Filtering methods so you can set up polling / schedules (CRON) inside DSYNC
To check if you can build a connector into the DSYNC platform you will need to research into the system you are looking to build a connector for. Developer information is generally easy to find by searching for the developer API documentation.
Basic process steps:
- Add a blank system on the DSYNC canvas
- Configure authentication
- Adding API endpoint for each entity - example products, orders
- Configure CRON URL schedule – With no coding you can schedule a cron timer inside DSYNC
- Synchronise data - with any connectors on the platform
- Let DSYNC know if you would like to market your connector
- After you have set up the configuration DSYNC can test your working solution and put it into our Wizard for widespread use.
Systems can be connected via the below authentication methods. Basic, tokens, oAuth 1, oAuth2, and generic oAuth by passing custom headers. DSYNC have built a configurable oAuth method for passing the token in the header. Developers can use the DSYNC generic oAuth connector to pass specific information across in the header.
What can DSYNC use for Authentication when you are building a plugin?
- Basic – Username password or API key
- Token - Tokens are great because they can be passed in the headers to DSYNC.
- OAuth 1 / OAuth 2 – Custom header. DSYNC have developed a generic oAuth to be able to handle the authentication.
Filtering (Cron Job vs Webhooks)
DSYNC can connect systems with both web hooks and cron jobs. For the simple endpoint configuration, the easiest way to set up is via our cron or schedule this will require the connecting API to have filtering methods for date ranges. Developers can set up polling / cron job if the system has anything to do with dates. Key words to search for in API documents are “modified from”, “updated at”, “since” or anything to do with dates.
To check the filtering capabilities, you will need to check with the systems api documentation. Search the API documentation for terms to be able to check dates
- Check the API documentation for the system you would like to connect to DSYNC
- Check the entities you would like to synchronize example ORDERS, CUSTOMERS, PRODUCTS
- Does the system have filtering capabilities? Look for if the platform has filtering capabilities in the API documentation.
Filtering Products: Search the API documentation for terms to be able to check dates. A good example of good filtering capabilities for products are to search for terms such as “since” Here is an example of a good filter capability: Since - A date/time string in the format YYYY-MM-DD or YYYY-MM-DDTHH-MM-SS. If a date or time is provided, only products updated since the given date or time will be fetched. Default is to fetch all. This is perfect and indicates that the system can be checked for updates. This means that if DSYNC passes a date to the system it can run a cron / poll the system to check for updates and changes. DSYNC can set time schedules and run cron jobs to check if systems have made changes.
Filtering Orders. Search the API documentation for terms to be able to check dates. A good example of good filtering capabilities is “Retrieve recently changed orders”. Collect all the orders that have been updated since the time value passed into this parameter (UTC). Fetches from beginning of time if not specified. We accept 2 formats, one with precision down to day and one with precision down to seconds. Example: Jan 20th, 2014 is 2014-01-20, Jan 20th, 2014 20:10:20 is 2014-01-20T20:10:20.