|
Name |
Description |
| api_key | Required. Contact Convio to obtain the value to send. |
| v | Required. API version to invoke. Must be "1.0". |
|
method |
Required. Specifies which method to perform. |
|
response_format |
Optional. Specifies the format in which to return the response. Can be either "xml" (the default value) or "json". |
| redirect | Optional. Specifies a URL redirect to send back to the browser after processing. |
|
cons_id |
The internal constituent ID of the user. |
|
member_id |
The external member ID of the user. |
|
primary_email |
Required to create a record. The email address of the user. |
|
add_center_ids |
Comma-separated list of numeric IDs of centers to add the user to. |
|
|
|
|
add_interest_ids |
Comma-separated list of numeric IDs of email interests to add the user to. |
|
remove_center_ids |
Comma-separated list of numeric IDs of centers to remove the user from. |
|
|
|
|
remove_interest_ids |
Comma-separated list of numeric IDs of email interests to remove the user from. |
|
source |
Text to associate with the record to identify how or from where the record was added. |
|
no_welcome |
Specifies whether to send a "welcome" auto-responder email to the new user. If the value is "f" or "false" (ignoring case) and the site is configured to send welcome auto-responders to new users, then one will be sent. |
* The constituent record fields that can be set by the caller can be retrieved using the listUserFields API method.
** Changed 3/27/08. This parameter is only available when making server-side API calls for security purposes.
Code Examples
-
AJAX Two-Step Registration Form - this example provides step by step instructions to create a two-step registration form from within a Convio powered page. Cick the link to see an example and find instructions for implementing on your site.
Response
Success
The response is formatted as XML by default, but the response_format input parameter can be used to specify either XML or JSON formatting. A successful return might look like the following:
XML format:<createConsResponse
xsi:schemaLocation=http://convio.com/crm/v1.0
http://service.convio.net/xmlschema/crm.public.v1.xsd
xmlns="http://convio.com/crm/v1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><cons_id>1002001</cons_id>
<message>New user added.</message>
</createConsResponse>
JSON format:
{"createOrUpdateConsResponse ":{
"message":"New user added.","cons_id":"1002001"}}
Error
If an error occurs during processing, the structure of the response is an "errorResponse" element. It contains two other elements: a "code" element and a "message" element. The "code" element contains a number corresponding to the error conditions documented on the error list page. The "message" element contains a text message that may provide further detail about the error. For example:
XML format:<errorResponse
xsi:schemaLocation=http://convio.com/crm/v1.0
http://service.convio.net/xmlschema/crm.public.v1.xsd
xmlns="http://convio.com/crm/v1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><code>12</code>
<message>Specified user name is already in use.</message></errorResponse>
JSON format:
{"errorResponse":{"code":"12","message":
"Specified user name is already in use."}}
See the complete list of HTTP Status codes and Error codes for calling from another application.


