{"note":"OpenAPI conversion -- returning structured metadata","name":"servicenow-table","description":"ServiceNow Table API","version":"1.0.0","base_url":"","endpoints":1,"raw":"@lap v0.3\n# Machine-readable API spec. Each @endpoint block is one API call.\n@api ServiceNow Table API\n@version 1.0.0\n@auth ApiKey JSESSIONID in cookie | ApiKey X-UserToken in header\n@endpoints 1\n@toc now(1)\n\n@endpoint GET /now/table/{tableName}\n@desc Retrieves multiple records for the specified table.\n@required {tableName: str # Name of the table from which to retrieve the records., Accept: str(application/json/application/xml)=application/json # Data format of the response body.}\n@optional {sysparm_fields: str # Comma-separated list of fields to return in the response., sysparm_query: str # Encoded query used to filter the result set. You can use a UI filter to obtain a properly encoded query. Syntax: sysparm_query=. : Name of the table column to filter against. : Supports the following values: =: Exactly matches . !=: Does not match . ^: Logically AND multiple query statements. ^OR: Logically OR multiple query statements. LIKE:  contains the specified string. Only works for  fields whose data type is string. STARTSWITH:  starts with the specified string. Only works for  fields whose data type is string. ENDSWITH:  ends with the specified string. Only works for  fields whose data type is string. : Value to match against. All parameters are case-sensitive. Queries can contain more than one entry, such as sysparm_query=[].  For example:  (sysparm_query=caller_id=javascript:gs.getUserID()^active=true)  Encoded queries also support order by functionality. To sort responses based on certain fields, use the ORDERBY and ORDERBYDESC clauses in sysparm_query.  Syntax: ORDERBY ORDERBYDESC For example: sysparm_query=active=true^ORDERBYnumber^ORDERBYDESCcategory  This query filters all active records and orders the results in ascending order by number, and then in descending order by category.  If part of the query is invalid, such as by specifying an invalid field name, the instance ignores the invalid part. It then returns rows using only the valid portion of the query. You can control this behavior using the property glide.invalid_query.returns_no_rows. Set this property to true to return no rows on an invalid query. Note: The glide.invalid_query.returns_no_rows property controls the behavior of all queries across the instance, such as in lists, scripts (GlideRecord.query()), and web service APIs.}\n@returns(200) {result: [map]} # Request completed successfully. If a valid query returned no results, the response body contains only an empty result array.\n\n@end\n"}