Generic REST / JSON connector
Pull records from any REST endpoint, map the fields and check them against a sample.
Who can do thisWorkspace Administrator
The Generic REST / JSON connector pulls records from any REST endpoint that returns JSON and writes them into a Juvaro app: assets in AMS or items in WMS. You map each target field yourself, and you can check the mapping against a live or pasted sample before you save. Use it for a system that has no dedicated connector.
The Integration Hub is in English only. Its buttons, fields and messages are quoted in English in these articles, in the Danish articles too, exactly as you see them in the app.
Create the connection
- Open Marketplace, find Generic REST / JSON (category Generic, works with Any app) and click Add. The mapping builder opens.
- Under Basics, enter a Name.
- Under Source, set the endpoint (see below) and click Fetch live sample.
- Under Target, choose the Module and, for assets, the Asset model.
- Under Field mappings, map each target field.
- Check the result under Sample & preview.
- Under Schedule & status, set the trigger and switch Enabled on.
- Click Save.
Source
- Type: REST / JSON endpoint.
- URL: the address the Hub calls, for example https://api.example.com/assets.
- Auth secret name (optional): the name of a secret held in Juvaro's vault for this endpoint, for example my-api-key. You type the name here, not the secret itself. Leave it empty for a public endpoint. The names of secrets Juvaro created for other connections are refused.
Fetch live sample calls the URL once and reads the reply. It shows "Live sample fetched", with " - showing the first 64 KB" if the reply was longer. The field names it finds become choices in the mapping. If it fails, you see "could not fetch the sample" or "timed out waiting for the sample".
Target
Module is AMS · Asset or WMS · Item. For AMS · Asset you must also choose an Asset model; every record becomes an asset of that model. Without it, saving fails with "choose an asset model for the AMS · Asset target".
Field mappings
Each row is one target field, with its mapping. A red asterisk marks a required field.
| Module | Target fields |
|---|---|
| AMS · Asset | Asset tag (required), Serial number, Purchase cost, Status |
| WMS · Item | SKU (required), Name (required), Quantity |
For each field choose a Mapping:
- Copy from field: take the value from a field in the source. After a live sample you pick the field from a list; otherwise you type the field name.
- Constant value: use the same value for every record, for example a fixed status.
Sample and preview
Under Sample & preview, paste a sample in Paste a sample (JSON object or array), for example one or two records from the system's documentation. The Hub runs your mapping over it and shows the result as a table, five rows per page. Problems, such as "sample is not valid JSON", are listed above the table. Nothing is written to AMS or WMS by the preview.
Check the preview with a sample that has an empty or odd record in it. It is cheaper to find a mapping problem here than after a run has written a hundred assets.
Schedule, webhook and cost
- A new connection starts with Trigger on Manual (Run now only) and Enabled off. Switch to On a schedule and it starts as daily at 02:00 UTC; the fastest choice is every 15 minutes. All times are UTC. See Schedules and Run now.
- The Webhook trigger section lets an outside system start a run. Before the first save it says "Save the connection first, then a webhook URL + secret appear here." See Webhook triggers.
- There is no Test connection; use Fetch live sample and a first Run now instead.
- Every run costs 1 credit plus 5 per MB, even when it finds no records; records themselves are free. A fetch is capped at 5 MB, and a connection that hits the cap shows Truncated on the Usage page. See Usage and credits.
- After 3 scheduled failures in a row the connection pauses itself. See A connection's page: figures, Pause and Resume.