Want to parse JSON from open RESTful API and save to SQL Server database?
Try Withdata FileToDB, a desktop JSON to SQL Server converter for Windows, MacOS, and Linux, Import JSON to SQL Server, 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.
Import JSON from open RESTful API to SQL Server database
Choose SQL Server 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 SQL Server database.
You can create new SQL Server table by JSON struct, just a few mouse clicks.
Select table and config fields.
4. Summary.
5. Import RESTful JSON to SQL Server.
See importing results in SQL Server table
Import API JSON_API to SQL Server in command line
Save “JSON_API to SQL Server” session, then you can:
- Import API JSON_API to SQL Server in Windows command line.
- Import API JSON_API to SQL Server in Linux command line.
- Import API JSON_API to SQL Server in macOS command line.
Set scheduled tasks for importing API JSON_API to SQL Server
You can schedule and automate this importing task by:
- Save session and create .bat (Windows) or .sh (Linux/macOS) file for “JSON to SQL Server” conversion.
- Set scheduled task for “JSON to SQL Server” conversion.
More about FileToDB – JSON to SQL Server converter
Download FileToDB
JSON → SQL Server reference
Type mapping
| Value kind | in JSON | in SQL Server |
|---|---|---|
| Int | 1234 (number) | int |
| Bigint | 9007199254740993 | bigint |
| Decimal | 1234.56 (number) | decimal(p,s) |
| Float | 1.234e10 (number) | float |
| Text | "text" (string) | nvarchar(n) |
| Long text | "multi-line\ntext" (escaped newline inside a string) | nvarchar(max) |
| Date | "2026-09-18" (string) | date |
| Datetime | "2026-09-18T14:30:00Z" (string) | datetime2 |
| Binary | "base64:..." (string) | varbinary(max) |
| Boolean | true / false (boolean) | bit |
| JSON | nested object or array, kept as structure | nvarchar(max) |
Dialect differences
JSON is a file format and SQL Server 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 SQL Server |
|---|---|---|
| port | — | 1433 |
| identifiers | Double quotes; backslash escapes | [square brackets] |
| row limit | — | SELECT TOP n |
| dates | No date type: dates arrive as strings and the reader must p... | datetime, datetime2, date, time |
| long text | — | nvarchar(max) |
| binary | Not supported natively - base64 inside a string | varbinary(max) |
| 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 | — |
Command line
| Side | Command |
|---|---|
| SQL Server | bcp |
| SQL Server (load) | bcp, or BULK INSERT |
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.
