You will notice that in the new API the authentication sits outside of the job_details and is handled separately.
We require all new integrations to consume the API without using passwords.
When sending us the advert content in the job details you must have Location_Id in the XML but it can be empty.
If you would like to include a location we recommend that you send us a text location into Location_Query instead of using Location_ID.
In order to get a good match the text should always include a country.
The location section of the XML will look something like this:< Location_Id/>< Location_Query>London, England</Location_Query>
Contract Type and Industry
You can use the following API call to get these lists, please note that your test account is set to use our Global system to enable you to get the relevant lists for this product. If you are likely to have clients based in France I will need to provide a separate account so that you can retrieve our French values (the Global system can also be translated to French but we have some clients using separate drop downs for France). http://api.adcourier.com/docs/show.cgi?type=show_xml&method=EnumeratedTypes
You have control over the stylesheets for both publish and dashboard. In most cases the stylesheet will be left empty so that our standard styling applies (please do not use the example provided in the XML example on the Hybrid API). By specifying a custom stylesheet, you are able to change the appearance of the AdCourier screens seen by the user to any scheme/template. The most common use for this is to configure the AdCourier screens to look like either the application generating the advert export or to add the clients own logo.
The following job description fields have a unique merging behaviour in AdCourier if the account is configured for 'Field Merging'. This is common in markets such as Holland, France and Australia (its not important for the UK or US). When the client is using AdCourier Field Merging we normally ask that the descriptive data is sent to the fields below (without field headers), for a client not opted into field merge (for example all UK and US clients) the data should be sent into the JobDescription only.
The descriptive fields we have available for clients opted into our field merge function are: