2023:Web Service Lookup (Lookup Specification): Difference between revisions

Revision as of 11:18, 20 March 2023

WIP

This article is a work-in-progress or created as a placeholder for testing purposes. This article is subject to change and/or expansion. It may be incomplete, inaccurate, or stop abruptly.

This tag will be removed upon draft completion.

API refers to a Lookup Process in Grooper. It mates a URL with a Data Field in Grooper to produce extraction results with far less hassle than one would have had creating/utilizing various Lexicons, Data Types/Fields, etc.

About

API is a new Lookup Process as of v2023. It allows users to ping off of a URL outside of the Grooper database and wed it with a Data Field constructed in Grooper for easier, more accurate extraction. API Lookups can be passed into Grooper in one of two formats: JSON or XML.

Getting Started

First, you'll need to know where to go to set up your API Lookup.

Select your Project.
- For this, and further examples, we'll use a simple set-up of travelers and their destinations.
Drill down to the Data Model and select Lookups, under Behavior

@@ Line 14: / Line 14: @@
 === About ===
 API is a new Lookup Process as of '''v2023'''. It allows users to ping off of a URL outside of the Grooper database and wed it with a Data Field constructed in Grooper for easier, more accurate extraction. API Lookups can be passed into Grooper in one of two formats: JSON or XML.
+=== Getting Started ===
+First, you'll need to know where to go to set up your API Lookup.
+# Select your Project.
+#* For this, and further examples, we'll use a simple set-up of travelers and their destinations.
+# Drill down to the Data Model and select Lookups, under Behavior