--- swagger: "2.0" info: description: "
\n\t\t\t\t\t\t\t\t\t\t\t\tThe AE REST\ \ API provides an interface for 3rd party\n\t\t\t\t\t\t\t\t\t\t\t\t\ applications to interact with the Automation Engine. It allows you to target\n\ \t\t\t\t\t\t\t\t\t\t\t\tthe AE from many programming languages, not only from\ \ Java. The AE REST API\n\t\t\t\t\t\t\t\t\t\t\t\twill eventually expose the most\ \ important AE API features for 3rd\n\t\t\t\t\t\t\t\t\t\t\t\tparty\ \ developers.\n\t\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\ \t\t\t\t\t\t\t\tPlease see the AE Java API if you are looking for a more comprehensive\n\ \t\t\t\t\t\t\t\t\t\t\t\tAPI.\n\t\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\ \tThe URI for each request has the form http[s]://{host}:{port}/ae/api/{version}.
\n\ \t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\tResponses which contain HTTP Status Codes 4xx\ \ through 5xx signal client / server\n\t\t\t\t\t\t\t\t\t\t\t\t\ errors. Details are delivered in the response body, formatted as application/json.\n\ \t\t\t\t\t\t\t\t\t\t\t\tDepending on the number of errors, the top level element\ \ of responses will\n\t\t\t\t\t\t\t\t\t\t\t\teither be an array of or\ \ a single object of type OutError or OutValidationError.\n\ \t\t\t\t\t\t\t\t\t\t\t\tPlease see POST /{client_id}/executions [400] and\ \ [401] for an example.\n\t\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\ \t\n\t\t\t\t\t\t\t\t\t\t\t\tA health check is available under\ \ GET /{client_id}/system/health. Be aware that solely the HTTP status\ \ code should\n\t\t\t\t\t\t\t\t\t\t\t\tbe used to determine the health ([200]\ \ signals healthy, [503] not healthy). A response body is optionally\ \ delivered,\n\t\t\t\t\t\t\t\t\t\t\t\tdepending on whether a PWP is currently\ \ present or not. If no PWP is present, a body of type OutError is returned,\n\ \t\t\t\t\t\t\t\t\t\t\t\totherwise it will be of type OutHealthCheck.\n\ \t\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\ Basic Authentication is used to authenticate users in the system,\ \ so make sure the Authorization header\n\t\t\t\t\t\t\t\t\t\t\t\tis present\ \ for each request. The user-pass section can be entered in the following 3 formats\ \ USERNAME:PASSWORD,\n\t\t\t\t\t\t\t\t\t\t\t\tUSERNAME/DEPARTMENT:PASSWORD\ \ and CLIENT/USERNAME/DEPARTMENT:PASSWORD. The character\ \ encoding scheme\n\t\t\t\t\t\t\t\t\t\t\t\tused to convert this section\ \ into an octet sequence is expected to be ISO-8859-1.\n\t\t\t\ \t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\tThe internal\ \ authorization system is used to authorize inbound requests. Depending\ \ on the endpoint, different\n\t\t\t\t\t\t\t\t\t\t\t\tprivileges and authorizations\ \ are needed. If missing, a [403] with details will be returned.\n\t\t\ \t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\tSome\ \ resources may be disabled till a given precondition\ \ is met eg. a mandatory configuration\n\t\t\t\t\t\t\t\t\t\t\t\tparameter is set.\ \ A call to a disabled resource yields a [404] with a custom error code and\ \ message.\n\t\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\tfilter identifier | \t\t\tfilter model | \t\ \t\tdescription | \t\t\texample | \t\t
---|---|---|---|
object_name | \t\t\tObjectNameFilter | \t\ \t\tSearches for object names, also supports placeholder signs. | \t\ \t\tExample | \t\t
calendar_event | \t\t\ \tCalendarEventFilter | \t\t\ \tSearches for calendar events with the given event name that are valid\ \ on the given time frame. | \t\t\tExample | \t\t
granularity | \t\t\t\GranularityFilter | \t\t\tBy\ \ default, a search query returns UC4 objects. To return calendar-events,\ \ use this \t\t\tfilter with the value CALENDAR_EVENT in field granularity. | \t\ \t\tExample | \t\t
location | \t\t\tLocationFilter | \t\t\tFinds objects\ \ by their folder location. | \t\t\tExample | \t\t
time_frame | \t\t\tTimeFrameFilter | \t\t\tSearches\ \ for objects that were created create/modified/used within the given \t\t\ \ttimeframe (unix epoch dates). Note: queries for object usage only return\ \ results if the LAST_USE property \t\t\thas been enabled in UC_SYSTEM_SETTINGS. | \t\ \t\tExample | \t\t
client | \t\t\tClientFilter | \t\t\tExtend the search\ \ to objects on client 0. | \t\t\tExample | \t\t
object_id | \t\t\tObjectIdFilter | \t\t\tSearches for\ \ an object with the given id. | \t\t\tExample | \t\t
variable_key | \t\t\t\VaraKeyFilter | \t\t\tSearches\ \ for variable keys inside of STATIC VARA objects. | \t\t\tExample | \t\ \t
agent | \t\t\tAgentFilter | \t\ \t\tSearches content of the agent field in JOBS objects. | \t\ \t\tExample | \t\ \t
login | \t\t\tLoginFilter | \t\ \t\tSearches content of the login field in JOBS objects. | \t\ \t\tExample | \t\ \t
archive_key | \t\t\tArchiveKeysFilter | \t\ \t\tSearch within the archive keys of an object. Please note that an archive\ \ key can \t\t\tonly have 32 characters, searching for longer keys will yield\ \ empty results. | \t\t\tExample | \t\t
variable_value | \t\t\ \tVaraValueFilter | \t\t\tSearches\ \ for variable keys inside of STATIC VARA objects. | \t\t\tExample | \t\ \t
title | \t\t\tObjectTitleFilter | \t\ \t\tSearch in object titles. | \t\t\tExample | \t\t
process | \t\t\tProcessSheetFilter | \t\t\tSearch\ \ in scripts of the process sheet (full-text). | \t\t\tExample | \t\t
documentation | \t\t\t\DocumentationFilter | \t\t\t\Search in object's documentation (full-text). Performs a full-text search\ \ in the \t\t\tdocumentation of an object (structured and unstructured). For\ \ structured documentation, \t\t\tthe search term will be matched against\ \ keys and values of the documentation. | \t\t\tExample | \t\t
object_type | \t\t\t\ObjectTypeFilter | \t\t\tFinds\ \ objects by the attribute object type. | \t\t\tExample | \t\t
platform | \t\t\tObjectPlatformFilter | \t\t\tFind\ \ objects by the attribute platform. | \t\t\tExample | \t\t
object_sub_type | \t\t\ \tObjectSubTypeFilter | \t\t\ \tFind objects by the attribute subtype. | \t\t\tExample | \t\ \t