csvbase is a simple website for sharing table data. Join the discord.
Table of contents
The basics: auth and content negotiation
Authentication
With CSVBase, you authenticate using by putting your username and API key straight in the url (known as "HTTP "basic" auth").
Here's an example:
https://<some_user>:<some_api_key>@csvbase.com/timw/logic
Basic auth is widely supported and is usually accepted anywhere that accepts urls.
However, timw/logic is public so auth is needed only for writes.
Content negotiation
CSVBase APIs use content negotiation to decide what formats are in use. This means it consults HTTP headers to decide what format to send back in response to a request.
It important that you set the Content-Type
and Accept headers to be the mimetype you want:
typically that is application/json for both. If you fail to
include these headers in your requests, the API will still work but
CSVBase will pick a sensible default: CSV for tables, JSON for rows.
You can bypass content negotiation for read-only requests by appending a
file extension to the url, eg .json. Here's an example
of that (same resource as above):
https://<some_user>:<some_api_key>@csvbase.com/timw/logic.json
This is useful when dealing with software where you aren't able to set headers.
The API: endpoint-by-endpoint
There are three kinds of thing in csvbase:
- users
- tables
- rows
While there's no API for users so far, there is for tables and rows.
Tables
This table looks like this in JSON:
{
"name": "logic",
"is_public": true,
"caption": "",
"licence": null,
"created": "2024-04-30T06:40:06.942477+01:00",
"last_changed": "2024-04-30T06:40:06.942477+01:00",
"columns": [
{
"name": "csvbase_row_id",
"type": "integer"
},
{
"name": "$SYMBOL",
"type": "string"
},
{
"name": "$NOT_PLACED",
"type": "string"
},
{
"name": "$GEOMETRY",
"type": "string"
},
{
"name": "$NO_GEOMETRY",
"type": "string"
},
{
"name": "$PROPERTY=MFR",
"type": "string"
},
{
"name": "$VALUE",
"type": "string"
},
{
"name": "$DESCRIPTION",
"type": "string"
},
{
"name": "$FILE1",
"type": "string"
},
{
"name": "$ITEM_ID",
"type": "integer"
},
{
"name": "$FILE2",
"type": "string"
},
{
"name": "col11",
"type": "string"
}
],
"approx_size": 799,
"page": {
"rows": [
{
"row": {
"$SYMBOL": "74ABT125",
"$NOT_PLACED": null,
"$GEOMETRY": "DIP14",
"$NO_GEOMETRY": null,
"$PROPERTY=MFR": null,
"$VALUE": null,
"$DESCRIPTION": "QUAD BUS BUFFER GATE (OE)",
"$FILE1": null,
"$ITEM_ID": 1,
"$FILE2": null,
"col11": null
},
"row_id": 1,
"url": "https://csvbase.com/timw/logic/rows/1"
}
],
"previous_page_url": null,
"next_page_url": "https://csvbase.com/timw/logic?op=gt&n=1"
}
}
Note that there is the top-level metadata, plus a "page" of rows. Tables
are often (usually) too big to be put into a single JSON object so they
are "paginated". To follow the table, page by page, you can use
the next_page_url and previous_page_url
dictionary keys. They will be null if you've reached
the end or are at the beginning, respectively.
Reading a table
GET from https://csvbase.com/timw/logic
You'll need to follow the next_page_url urls (described
above) to get to the end of the table.
Rows
Rows from timw/logic look like this in JSON:
{
"row": {
"$SYMBOL": "74ABT125",
"$NOT_PLACED": null,
"$GEOMETRY": "DIP14",
"$NO_GEOMETRY": null,
"$PROPERTY=MFR": null,
"$VALUE": null,
"$DESCRIPTION": "QUAD BUS BUFFER GATE (OE)",
"$FILE1": null,
"$ITEM_ID": 1,
"$FILE2": null,
"col11": null
},
"row_id": 1,
"url": "https://csvbase.com/timw/logic/rows/1"
}
Creating a new row
POST to https://<some_user>:<some_api_key>@csvbase.com/timw/logic/rows/
Example body
{
"row": {
"$SYMBOL": "74ABT125",
"$NOT_PLACED": null,
"$GEOMETRY": "DIP14",
"$NO_GEOMETRY": null,
"$PROPERTY=MFR": null,
"$VALUE": null,
"$DESCRIPTION": "QUAD BUS BUFFER GATE (OE)",
"$FILE1": null,
"$ITEM_ID": 1,
"$FILE2": null,
"col11": null
}
}
Example response
{
"row": {
"$SYMBOL": "74ABT125",
"$NOT_PLACED": null,
"$GEOMETRY": "DIP14",
"$NO_GEOMETRY": null,
"$PROPERTY=MFR": null,
"$VALUE": null,
"$DESCRIPTION": "QUAD BUS BUFFER GATE (OE)",
"$FILE1": null,
"$ITEM_ID": 1,
"$FILE2": null,
"col11": null
},
"row_id": 1,
"url": "https://csvbase.com/timw/logic/rows/1"
}
Status code 201 upon success.
Reading a row
GET from https://csvbase.com/timw/logic/rows/1
No body is provided with this request. Status code 200 upon success.
Example response
{
"row": {
"$SYMBOL": "74ABT125",
"$NOT_PLACED": null,
"$GEOMETRY": "DIP14",
"$NO_GEOMETRY": null,
"$PROPERTY=MFR": null,
"$VALUE": null,
"$DESCRIPTION": "QUAD BUS BUFFER GATE (OE)",
"$FILE1": null,
"$ITEM_ID": 1,
"$FILE2": null,
"col11": null
},
"row_id": 1,
"url": "https://csvbase.com/timw/logic/rows/1"
}
Updating an existing row
PUT to https://<some_user>:<some_api_key>@csvbase.com/timw/logic/rows/1
Example body
{
"row": {
"$SYMBOL": "74ABT125",
"$NOT_PLACED": null,
"$GEOMETRY": "DIP14",
"$NO_GEOMETRY": null,
"$PROPERTY=MFR": null,
"$VALUE": null,
"$DESCRIPTION": "QUAD BUS BUFFER GATE (OE)",
"$FILE1": null,
"$ITEM_ID": 1,
"$FILE2": null,
"col11": null
},
"row_id": 1,
"url": "https://csvbase.com/timw/logic/rows/1"
}
Response
Upon success the body you sent will be echoed back, with status code 200.
Deleting a row
DELETE from https://<some_user>:<some_api_key>@csvbase.com/timw/logic/rows/1
No body is required. Status code 204 upon success.