Ah, that's a good catch. I never noticed that the request and response IDs don't match in the documentation. I'll update that document to fix the confusing example.
To be specific: When adding an event with /events/new, the response will include the new ID for the event. When modifying an event with /events/modify, the response will include the existing ID for the event. The ID does not change when the event is modified. Thanks, ~chris On Aug 18, 2010, at 10:12 AM, Bharath Alapati wrote: > Here's an example request URL: > http://api.evdb.com/rest/events/modify?...&id=E0-001-000483123-4&title=Picnic+In+The+Park > Example XML Response > <?xml version="1.0" encoding="UTF-8"?> > > <response status="ok"> > <id>E0-001-000278174-6</id> > <message>Modify event complete</message> > </response> > > Probably the response xml posted on the site is wrong. > >
