Archive for the 'API' Category

« Previous Entries
in API

A Change for the Better: A brief update for all of our API faithful

Thursday, January 18th, 2007
By Max Grigorev
January 18th, 2007

We have decided to change the way we handle your API questions so we can respond to you more efficiently. You should no longer directly email any of your Right Media contacts with API questions. Instead, please send them to api@rmxsupport.com. Our API team will be monitoring the queue at all times.

This change will allow us to track your requests in a consistent manner and provide you with a ticket id to follow your question or bug report to its conclusion. If you feel that your issue is extremely time sensitive, by all means CC your RM contact, but it should no longer be necessary.

Now for the the specifics:

We have set down a few ground rules.

  • Please limit the number of employees submitting tickets whenever possible. Having a single point of contact at your company will allow us to provide consistent support.
  • When opening a trouble ticket, please include as much information as you can. A few minutes of extra research and documentation put in on the front end will prevent our engineers from sending the always irritating “Have you tried this” email.
  • Always read the documentation first.
  • If your issue is extremely urgent, please make sure that you state that in the subject of the email. [URGENT] would work nicely.

Target Response Times:

We will do everything in our power to hit these metrics:

  • 24 business hour initial response time: Our agents will be checking in over the weekend and in most cases we eclipse this number.
  • 2 Day resolution time: Once we have received all of the required information, we will strive to have the issue identified and resolved within two business days. In the case where a release is required, it may take several more days until the patch can be tested and pushed into production.

Thank you for helping us to make our service better!

Max, head of API Support Team.

No Comments
in API

SOAP API version 0.22 now available

Wednesday, September 13th, 2006
By Ilya Martynov
September 13th, 2006

Release notes for new version.

API documentation.

No Comments
in API

Release 0.21 is out

Thursday, August 10th, 2006
By Ilya Martynov
August 10th, 2006

Release notes for 0.21.

API documentation.

WSDLs for the production version:

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

WSDLs for the test version:

No Comments
in API

Release 0.20 is out

Monday, July 10th, 2006
By Ilya Martynov
July 10th, 2006

New APIs:

  • ContactService.get/listAll to get all contacts available to the current user.
  • SiteService.get/listAll to get all sites available to the current user.
  • New service LinkingService.

Updated APIs:

  • (INCOMPATIBLE CHANGE) Add validation check to verify that creative content doesn’t contain any malformed macroses.
  • (INCOMPATIBLE CHANGE) Data type ‘pixel’ doesn’t have fields ‘trigger_type’ and ‘post_trigger_interval’ anymore.
  • It is allowed now to change contact.username with ContactService.update()
  • It is allowed now to change contact.role_id with update().
  • Field ‘default_site_id’ have been added to data type ‘publisher’.
  • Request rate restriction have been lifted.
  • CreativeService doesn’t wait for creative tester for 30 seconds when adding/updating creatives anymore.
  • Allow to create an insertion order between two self managed entities. Send a email notification when creating such insertion order.
  • Allow to create or modify a line item between two self managed entities. Send a email notification when creating or changing such line item.
  • Validate if a field of enum type actually has value which is defined for enum type of this field.
  • (INCOMPATIBLE CHANGE) New validation rule: campaign.learn_actions_per_creative_per_section should be < 1000000.

Bugfixes:

  • In some cases Creative service were incorrectly presetting can_track_clicks to 0 in add() and update().
  • Contact service had wrong access restriction rules.
  • SectionService.update() didn’t work if section description didn’t change.
  • PixelService.get/setPiggybackPixels() used wrong data type.
  • TargetProfile.setTargetGeography() if given all regions as a target didn’t switch geo targeting to include all regions by default. Fixed now.
  • TargetProfile.setTargetDayparts() didn’t merge overlaping dayparts correctly.
  • Publisher.update() could reset managing_entity_id to wrong value in some cases.
  • All dateTime fields specify explicitly GMT timezone now.

Updated documentation:

  • Switch to no-frames format for the documentation.
  • C++ examples were updated to follow gSOAP documentation recommendations on memory allocation strategies.
  • C# examples have have been added.
  • Added object hierarchy graphic to the documentation.

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

WSDLs for the beta production version:

WSDLs for the stable production version:

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

WSDLs for the test version:

No Comments
in API

Release 0.19 is out

Wednesday, June 7th, 2006
By Ilya Martynov
June 7th, 2006

Updated APIs:

  • (INCOMPATIBLE CHANGE) Missing validation rules for size targeting have been implemented. Now size targeting is available only for campaigns and line items.
  • (INCOMPATIBLE CHANGE) Missing validation rules for geography targeting have been implemented. Now geography targeting is available for campaigns, line items and creatives only.
  • (INCOMPATIBLE CHANGE) Missing validation rules for daypart targeting have been implemented. Now daypart targeting is available for campaigns, creatives and line items only.
  • Add back adapt_media_hex and adapt_click_hex fields to creative data type.
  • (INCOMPATIBLE CHANGE) An error is returned by CreativeService.add() or update() if a creative contains an invalid file marker.
  • (INCOMPATIBLE CHANGE) Starting from this version all versions of API will use same URL namespaces in WSDL to avoid breaking C++ and Java clients on upgrades.
  • (INCOMPATIBLE CHANGE) Missing validation rules for validated urls targeting have been implemented. Now vurl targeting is available for line items only.
  • (INCOMPATIBLE CHANGE) Missing validation rules for querystring targeting have been implemented. Now querystring targeting is available for line items only.
  • New field ‘allow_size_promotion’ in data type ‘line_item’.
  • APIs LineItemService.listBySeller(), LineItemService.listByBuyer(), LineItemService.getBySeller(), LineItemService.getByBuyer() were available to SMAs only. They are available to all entities now.

Bugfixes:

  • Campaign service didn’t check if pair of fields ‘description’ and ‘advertiser_entity_id’ in ‘campaign’ data type is unique.
  • In some cases it was not possible to set unlimited budget for pricing types with delivery caps.
  • InsertionOrderService.listBySeller returned too many IDs in some cases.
  • Users could reset creative content hash to NULL in some cases (the fix in previos release was incorrect).
  • CreativeService didn’t allow to set pop_expand_to_full_window to 0 for url creatives.
  • CreativeService didn’t allow to set click_url to NULL in some cases when it should be allowed.
  • (INCOMPATIBLE CHANGE) Data type ‘contact’ was exposing field ‘is_deleted’. It is removed from API now.
  • Creative service didn’t allow to upload creatives with repeating file markers.

Updated documentation:

  • The list of currently used SOAP toolkits and information how to build C++ examples have been added onto the example page.
  • New API lookup() in all services which support integration codes.

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

WSDLs for the beta production version:

WSDLs for the stable production version:

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

WSDLs for the test version:

No Comments
« Previous Entries