Contact us to let us know the URL, e.g. http://www.placeford.org/cycling/journeyplanner/ and the header/footer URLs

(Note that we also can support wildcard proxied domains, e.g. http://customer1.placeford.org/cycling/journeyplanner/, http://customer2.placeford.org/cycling/journeyplanner/, etc.)

We will then add the site to our settings and sort out any customisations and layout fixes

We will confirm when ready to go-live

Method 3 (Avoid if possible)

iframe method

We can set up a site which can be loaded in an iFrame. This is reasonably simple at both ends, but has the downside of being unable to have a unique URL for each journey that people can e-mail to others.

This involves the webteam simply creating an iFrame in the relevant part of your site, with the target being a URL that we will set up and confirm.

Steps:

Contact us to let us know the URL of the page and the size of the iframe

We will then add the site to our settings and sort out any customisations

We will then confirm our URL to use within the iframe

Method 4 (Advanced)

API calls into your own interface

This is by far the most advanced option and requires programming and much testing from your webteam, and so is not really recommended unless you are prepared to put in ongoing resources.

We have an API which provides a journey solution when provided with the details (start and end points etc.) of a requested journey. This data would need to be captured and then inserted into an interface which you run.

This requires an ongoing commitment to resourcing at your end so that the system keeps pace with any changes to the API we implement.