Hi Steven,
The URL API is a browser based api, so if you plan on coding in a language such as java or C# there could be some unexpected results This is because these languages usually do not follow URL redirects, which occur on our servers with the URL API. I'm not too famillar with C# so you may have to correct me, but it looks like this is using server to server communication and not being populated in a browser like you would see with classic asp. I think that is what may be causing the error in this case. I would suggest using the XML API to do the attendee registration for server to server communication. An example is below.
1
2
3<?xml version="1.0" encoding="UTF-8"?>
4<serv:message xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
5 xmlns:serv="http://www.webex.com/schemas/2002/06/service"
6 xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service
7 http://www.webex.com/schemas/2002/06/service/service.xsd">
8
9 <header>
10 <securityContext>
11 <webExID>{username}</webExID>
12 <password>{password}</password>
13 <siteID>243585</siteID>
14 <partnerID>g0webx!</partnerID>
15 </securityContext>
16 </header>
17
18 <body>
19 <bodyContent xsi:type="java:com.webex.service.binding.attendee.CreateMeetingAttendee">
20 <person>
21 <name>{full name}</name>
22 <email>{email}</email>
23 <title>{title}</title>
24 <company>{co}</company>
25 <address>
26 <address1>{a1}</address1>
27 <address2>{a2}</address2>
28 <city>{City}</city>
29 <state>{state}</state>
30 <zipCode>{Zip}</zipCode>
31 <country>{Co}.</country>
32 </address>
33 <phones>
34 <phone>1,123,1234567</phone>
35 </phones>
36 </person>
37 <joinStatus>ACCEPT</joinStatus>
38 <sessionKey>{session key}</sessionKey>
39</bodyContent>
40</body>
41</serv:message>
