I am looking for someone to give me some training or help with some APIs, and possibly some advice on how to figure out how to plan a workflow.
I have an idea of what I need it to do but unsure if the workflow will work and don’t want to spend hours building it for it to get to the end and not work.
small budget
I really appreciate any help.
Hey @jonathan10 
Why don’t you share with us what you need?
Maybe you can solve it for free 
HI @rpetribu
I run a marketplace, where i have suppliers that singup to the platform and can,
Build a profile
Create their products
manage their products
manage bookings
and manage payment
Once approved it gets displayed on the front end home page and product page.
this all works great but I am now trying to and another way for larger suppliers that have their booking system that they would like to connect to mine.
They would not be going through,
Login Process
Uploading of trips
Creating an account
or any of the other functions that we have on the system.
All their information is held on their own system and we only GET
Product name
Price
Dates
Location
Itinuary
Brief description
IMages
Avaliblity
and then POST
Enquires
Bookings
Deposits
Full Payments
My question is can I integrate this into the extensive workflow I already have for smaller providers or will I have to create a completely new workflow and data branch?
Or does anyone have a method for planning out workflows to make sure they will work before implementing them.
If I were you, for the sake of organization, I would create two separate flows. One for the majority of your clients (the one you already have) and another for the big suppliers.
These flows can end up being quite different, so it’s better to have your actions well defined in each of the steps than to have to create several conditionals in every step. This can end up making your flow very large, complex and difficult to maintain or correct.
Thank you @rpetribu , Do you have any recomendation how to plan a workflow and best pratice.?
I think your project will be quite challenging, because these large suppliers will need to have some endpoint where you can perform your queries (GET). In addition, they will also need to have an endpoint for you to send your POST.
The first challenge is to ensure that the systems they use have this type of openness. Otherwise, there is no way for you to include them in your marketplace in the way you thought.
The second challenge is the fact that these suppliers probably work with different systems, which makes it practically impossible for you to simply create a standard GET/POST format that will adapts to all of their systems.
Have you spoken to at least two or three of these major suppliers to explore the feasibility of implementing this?
HI @rpetribu I have all the documents for the large suppliers APIs. and it very a very long document. (haha) below is only have of the end points.
I have started thinking possible building 3 doffrent levels of suppiers,
Small
Medium
Large
them build this in to the type base with a type. and each tpe can have levels of access.
Test connection and check rate limit.
List all connected channels (tour/activity/accommodation operators). This method can only be called by Marketplace Agents.
Show information on a particular channel (i.e. tour/activity/accommodation company information).
For Marketplace Agents only. List the performance (clicks, commission earnt, enquries made etc) of top 50 connected channels by clicks (or check performance for a specific channel).
Return full information about the Markup Scheme associated with a Channel. For Tour Operator Use Only.
Search Tours by keyword, distance, month, distance from a geographic point etc - or just list all. Use this call if you are building a page which lists products or if you are building a search page. Also can be used for searching (and listing) special offers.
Show information on a particular Tour.
Show all some/all dates, prices and special offers for a particular Tour.
Update details of a particular Tour. Currently supports a subset of all fields.
List primary locations (and associated countries), could be useful for building a dropdown / autocomplete search.
Product Filters are used to group related tours, this API returns a list of them and the tours they contain. For tour operator use only, not accessible by Marketplace Agents.
Special version of the “Search Tours” method, tailored specifically for searching room availability of products loaded using Hotel pricing.
For use by Tour Operators only (not Marketplace Agents), various API methods to enable managing of Tour dates & prices externally of TourCMS.
For use by Tour Operators and Marketplace Agents. Lists the field restrictions configured in specific tours.
For use by Tour Operators and Marketplace Agents. Shows the Tours Tags selected for a tours of a channel, as well as its locations
You are welcome to use these methods directly, however they are probably most useful if you are taking a regular export of TourCMS data to import into your own database. Combine with the “Show Tour” method above to get full product details.
List all Tours from a particular channel (supplier).
List image URLs for all Tours from a particular channel (supplier). Useful if you are mirroring product images to your own server.
Show all the dates and prices for a particular Tour that are generated by Departures. Shows a little more detail on each date than “Dates & Deals” but doesn’t include freesale season or hotel priced dates.
