I’ve been authenticated with my login details, but when making calls after this I’m told I’m not authorized?

The most common reason for this is that the access token has not been URL encoded. All parameters that are passed into the API must be URL encoded before making the request.

In PHP, it is as simple as using the inbuilt function:

$accesstoken = urlencode('V9ZgDeeNgiB8JhvX24ez3dFjCdIvxgZqRCf7owGvY5dPRdo4LX7u+p5zcNNgMjQAoFhWACGNy+6BPLu16nifkw==');
echo $accesstoken; // V9ZgDeeNgiB8JhvX24ez3dFjCdIvxgZqRCf7owGvY5dPRdo4LX7u%2Bp5zcNNgMjQAoFhWACGNy%2B6BPLu16nifkw%3D%3D

Ok, I’ve URL encoded my access token but I am still not being authorized…

If you are using the XML response from the Aventri API, depending on what language you are using your responses might be getting returned as objects rather than string values. For example in PHP you could have the following response:

            SimpleXMLElement Object
            [0] => tdl60c0E+cRkGuOFhGPaIqYrOGuzNa9f5PRdJD1IfMf58eoBHJ4DA6AD6caU2MZG2pOvCRJYejxQWY8gGQ3mpg==

To resolve this situation there are three options available to you.
  • Use JSON instead of XML
  • Cast the object as a string
  • Use trim()

            $accesstoken = (string) $request['response'];
            $accesstoken = trim($request['response']);

- Also please make sure using the right Domain Hostname for the URL.
US - https://www.eiseverywhere.com
EU - https://eu.eventscloud.com
Australia - https://au.eventscloud.com
*If it changes, or you are in other environment or portal, the right Domain Hostname is always be the hostname in the URL that you log into that Aventri system back-end page.  

How do I use API Triggers?

If you would like to receive automatic notifications of registrations, registration modifications and registration cancellations you can setup API triggers for these scenarios. To setup an API trigger follow the following instructions:

  1. Within an event, navigate to the Advanced Settings > Integrations page and then scroll down to the “API Registration Trigger” section.
  2. You can create or update a trigger by filling out and submitting the form in this section:
    1. Choose the attendee scenario you want to setup a trigger for.
    2. Set the URL to send the triggered HTTP post message to.
    3. Choose the content-type of the HTTP post message.
  3. If you do not have a trigger setup for a specific scenario a new one will be created. If you already have one setup it will be updated.
  4. Once a trigger is created, whenever the respective scenario is encountered on either the front-end (by a registrant / admin) or the back-end (by an admin) an HTTP message will be posted to the configured URL containing the following parameters:
    1. AttendeeID = The numeric attendee ID which was created / modified / cancelled.
    2. EventID = The numeric event ID in which the attendee exists.
    3. Scenario = The scenario which occurred: "Registration / Modification" or "Cancellation".
  5. Once a HTTP message is received you can use the supplied information to obtain more information through other API functions, such as getAttendee.

Changes to the following types of attendee information are classified as registration modifcations:

  • Agenda selections
  • Attendee selections
  • Billing information
  • Category
  • Hotel booking
  • Lodging status
  • Options
  • Personal information
  • Registration status
  • Session selections
  • Sub category
  • Travel booking

How can I find the list of time zones codes returned in the getEvent call?

See the link to get the list of time zones.