Archive for the 'API' Category

« Previous Entries
Next Entries »
in API

Release 0.18 is out

Monday, May 22nd, 2006
By Ilya Martynov
May 22nd, 2006

New APIs:

  • New API set/getDefaultChannels() and set/getDefaultInventoryType() in Publisher service to set default channels/inventory type for publishers.

Updated documentation:

  • New page with API client examples.
  • Documentation had mistakes when describing expected time format (we use UTC timezone instead of EST, daypart time format should be in hours).

Bugfixes:

  • Invalid contact could be created when using either Publisher.add() or Contact.add() APIs.
  • Users could reset creative content hash to NULL in some cases.

API documentation: http://api.yieldmanager.com/doc/.

WSDLs for the beta production version (updated to the latest version 0.18):

WSDLs for the stable production version (runs old version 0.16):

Test version UI: http://api-test.yieldmanager.com/test-ui/.

WSDLs for the test version:

No Comments
in API

Release 0.17 is out

Wednesday, May 10th, 2006
By Ilya Martynov
May 10th, 2006

Updated APIs:

  • (INCOMPATIBLE CHANGE) All fields are declared as optional in WSDL now. The SOAP server is less strict about missing fields for add() and update() operations. In most cases it would substitute a default for a missing field when it the past the same missing field would result in a SOAP Fault.
  • (INCOMPATIBLE CHANGE) Creative service have been reworked. Particulary many new fields were added to creative soap data type, support for binary file uploads was added and complete set of validation rules have been implemented.
  • Support for super user access.
  • IO/LI services supports all cases when managing entity connects to its managed entity. Linking (i.e. connecting two self-managed entities) is not supported yet.
  • New high level API for publisher creation addEx() which allows to create a set of business objects in one step: a publisher, a default site, a default section, an insertion order connecting to this publisher and a line item on this insertion order.
  • New APIs to manage contacts.

Updated documentation:

  • Added documentation on available offer types.
  • Removed references on API addDeliveryRules() which doesn’t exist anymore.

Bugfixes:

  • insertion_order.exchange_rate is autoset by the server now.
  • Check entity settings if “Must Deliver” priority can be set

API documentation: http://api.yieldmanager.com/doc/.

Test version UI: http://api-test.yieldmanager.com/test-ui/.

WSDLs for the test version:

WSDLs for the beta production version (updated to the latest version 0.17):

WSDLs for the stable production version (runs on old version 0.16):

No Comments
in API

“Backup” of production SOAP server

Tuesday, April 4th, 2006
By Ilya Martynov
April 4th, 2006

We are trying very hard to avoid breaking existing SOAP clients when releasing a new version of SOAP server. In case if the incompatible change which is known to break an existing SOAP client had to be introduced we warn our clients in advance. Still there is a chance that new production version breaks existing SOAP clients unexpectedly. To help in this case starting from version 0.16 we provide a “backup” - an instance of production SOAP server which still runs the previous version (see the annoncement for links on WSDLs). So if you happen to run into your client application being broken after a release please report the problem immediately to rmapi-users@rt.iponweb.net and switch to “backup” version. This would allow you to keep your client application working while we are fixing the compatibility problem.

No Comments
in API

Release 0.16 is out

Tuesday, April 4th, 2006
By Ilya Martynov
April 4th, 2006

New APIs:

  • Added PixelService with add(), get(), update(), setCreatives(), getCreatives(), setPiggybackPixels(), getPiggybackPixels() operations. Added TargetProfile.set/getTargetPixels() API.

Updated APIs:

  • (INCOMPATIBLE CHANGE) The server doesn’t preset creative.advertiser_entity_id, campaign.advertiser_entity_id to currently logged in entity anymore when adding creatives or campaigns. It is also possible now to explicitly pass line_item.buyer_entity_id when adding a line item. Old behavior made sense for SMA-only case but doesn’t work well in the general case.
  • (INCOMPATIBLE CHANGE) As no external clients use Creative service yet we took an opportunity to break compatibility and rework this service to support more creative fields, add new validation rules and rework they way clients set creative content for creatives (add/delCreativeContent() APIs are gone). Most of the planned changes for this service are part of this release but some of them are not finished yet and will be a part of the next release. Particallary not all validation rules have been implemented and uploading supporting files is not ready yet (add/delSupportingFiles() API).

Updated documentation:

  • Region table lists IDs of countries regions belong to.
  • Mention in contact service documentation for how long sessions persist after login.

Bugfixes:

  • (INCOMPATIBLE CHANGE) Names of varios objects (advertisers, publishers, campaigns, line items, etc) were not checked to be non-empty strings.
  • Wrong error message was shown when accessing the API with session token set to NULL.

API documentation: http://api.yieldmanager.com/doc/.

WSDLs for the production version:

WSDLs for the previous production version:

Test version UI: http://api.yieldmanager.com/test-ui/.

WSDLs for the test version:

1 Comment
in API

Release 0.15 is out

Tuesday, March 21st, 2006
By Ilya Martynov
March 21st, 2006

Updated APIs:

  • (INCOMPATIBLE CHANGE) Both publisher and advertiser services were updated to be in sync with UI (support for finance office). One change visible to API users is that set of fields in publisher and advertisers types is different then in the previos version. Particularly billing address is gone. Another change visible to API users is that add() method in both publisher and advertiser services has a new parameter contact.
  • (INCOMPATIBLE CHANGE) Campaign data type has a new field ‘priority’.
  • (INCOMPATIBLE CHANGE) Advertiser/Publisher data types have a new readonly field ‘integration_code’. It cannot be set by add() or update(). There is a separate new API call setIntegrationCode() to set it. Please note that this call fails unless there exists at least one IO between current entity and Advertiser/Publisher you are setting the code for.
  • (INCOMPATIBLE CHANGE) Field ‘billing_name’ was removed from Advertiser/Publisher custom types.

Bugfixes:

  • When creating an advertiser or a publisher finance_office.label and finance_office.default_type were not set.
  • Publisher service didn’t validate if entity name is unique.
  • When creating a section it should have ‘Unknown’ channel by default.
  • (INCOMPATIBLE CHANGE) Java Axis SOAP clients couldn’t set neither country_id or region_id fields for publisher/advertisers. Workarounded by removing default values from WSDL which most SOAP clients do not use anyway.

API documentation: http://api.yieldmanager.com/doc/.

WSDLs for the production version:

Test version UI: http://api.yieldmanager.com/test-ui/.

WSDLs for the test version:

No Comments
« Previous Entries
Next Entries »