Want to parse JSON from open RESTful API and save to Clipper database?
Try Withdata FileToDB, a desktop JSON to Clipper converter for Windows, MacOS, and Linux, Import JSON to Clipper, Easy and Fast.
- Can run in GUI mode, Step by Step, just a few mouse clicks.
- Can run in Command line, for Scheduled Tasks and Streams.
Download FileToDB
Windows 64 bit
Windows 32 bit
Linux .deb (For Debian, Ubuntu) 64 bit
Linux .rpm (For Red Hat, Fedora, SUSE) 64 bit
MacOS 64 bit
Import JSON from open RESTful API to Clipper database
Choose Clipper and logon.
Click “Wizard – 1 File To 1 Table” at task dialog.
Select “Source File From” with “Url”.
1. Input the RESTful API URL, and download to JSON file.
2. Open the saved JSON file.
3. Config target Clipper database.
You can create new Clipper table by JSON struct, just a few mouse clicks.
Select table and config fields.
4. Summary.
5. Import RESTful JSON to Clipper.
See importing results in Clipper table
Import API JSON_API to Clipper in command line
Save “JSON_API to Clipper” session, then you can:
- Import API JSON_API to Clipper in Windows command line.
- Import API JSON_API to Clipper in Linux command line.
- Import API JSON_API to Clipper in macOS command line.
Set scheduled tasks for importing API JSON_API to Clipper
You can schedule and automate this importing task by:
- Save session and create .bat (Windows) or .sh (Linux/macOS) file for “JSON to Clipper” conversion.
- Set scheduled task for “JSON to Clipper” conversion.
More about FileToDB – JSON to Clipper converter
Download FileToDB
Windows 64 bit
Windows 32 bit
Linux .deb (For Debian, Ubuntu) 64 bit
Linux .rpm (For Red Hat, Fedora, SUSE) 64 bit
MacOS 64 bit
JSON → Clipper reference
Type mapping
| Value kind | in JSON | in Clipper |
|---|---|---|
| Int | 1234 (number) | Numeric(10,0) |
| Bigint | 9007199254740993 | Numeric(19,0) |
| Decimal | 1234.56 (number) | Numeric(p,s) |
| Float | 1.234e10 (number) | Float |
| Text | "text" (string) | Character(n) |
| Long text | "multi-line\ntext" (escaped newline inside a string) | Memo |
| Date | "2026-09-18" (string) | Date |
| Datetime | "2026-09-18T14:30:00Z" (string) | (none) |
| Binary | "base64:..." (string) | (none) |
| Boolean | true / false (boolean) | Logical |
| JSON | nested object or array, kept as structure | (none) |
Dialect differences
JSON is a file format and Clipper is a database server, so the target has to be told the types the file never carried - the rows below are where the two sides diverge.
| Property | in JSON | in Clipper |
|---|---|---|
| port | — | (file-based) |
| identifiers | Double quotes; backslash escapes | — |
| row limit | — | (driver dependent) |
| dates | No date type: dates arrive as strings and the reader must p... | Date (D) |
| long text | — | Memo (M) |
| binary | Not supported natively - base64 inside a string | — |
| separator | Braces and commas | — |
| encoding | UTF-8 by definition | — |
| typing | string, number, boolean, null, object, array - no date type | — |
| shape | Nested objects and arrays | Tables of rows and columns |
| ceiling | Whole document is usually parsed into memory | — |
No counterpart
- JSON values of kind Date and time have nowhere to go in Clipper.
- JSON values of kind Binary have nowhere to go in Clipper.
- JSON values of kind JSON have nowhere to go in Clipper.
Convert your data online, free
Free in-browser converters for CSV, Excel, JSON, XML and SQL: Withdata Online Data Conversion. Large files, batch conversion or scheduling? See the offline desktop apps, or browse all data conversion tools.