The following API calls have been made available for your convenience. Enjoy!

Agent.Run - You can now have an agent running multiple times in the system. This can be accomplished by calling the Agent.Run command successively using the API; you do not have to wait for a previous job from an agent to finish before initializing a new job for the agent.

In the past, you could only perform the following four actions through the web console. Now you can perform them through the API as well:

Collection.Add - With this new call, users can add entirely new collections to their account. This is really useful now that you can tell an agent which collection to use for inputs when it runs.

Collection.AddField - Allows users to add fields to existing user-created collections.

Collection.DeleteField - Allows users to delete fields from existing user-created collections. 

Collection.SetUniqueFields - Allows users to programmatically set the unique fields for the Collection. 

Collection.Publish - Users can now initiate FTP publishing for an agent at any time. This will be very useful for users that are getting large amounts of data back via the View.GetItems call. Downloading millions of records will take hours using the API. With the Collection.Publish call, it can publish a file in minutes. Then, you can load the file on the user side and process it.

View.SetFields - Allows users to select the included fields and their order in the specified view. Now you can include system fields in your views without having to go into the agent and manually editing the view in the Web Console.

Job.GetList - This call will allow you to find out all the jobs on your account. You can filter this list by supplying the Job.State parameter to specify Active, Archived, or All jobs. This is useful for knowing when agents are running, so you can determine whether or not you can run an agent.

Collection.GetFields - There is a new parameter called "Include" that can be supplied to determine which fields to get back—either all fields or the unique fields. It defaults to "All". In the past, you had to filter the list afterwards to determine the Unique fields for a collection.

Agent.GetJobs - This call now has a Job.State parameter that can be passed in to determine whether to only get Active, Archived, or All jobs for an agent.

You can learn more about these and other API calls on the API documentation page: http://www.mozenda.com/api.