csvbase is a simple website for sharing table data. Join the discord.
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/aborruso/elenco-immobili-in-proprieta-ater-venezia-gestione-erp
Basic auth is widely supported and is usually accepted anywhere that accepts urls.
However, aborruso/elenco-immobili-in-proprieta-ater-venezia-gestione-erp is public so auth is needed only for writes.
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/aborruso/elenco-immobili-in-proprieta-ater-venezia-gestione-erp.json
This is useful when dealing with software where you aren't able to set headers.
There are three kinds of thing in csvbase:
While there's no API for users so far, there is for tables and rows.
This table looks like this in JSON:
{ "name": "elenco-immobili-in-proprieta-ater-venezia-gestione-erp", "is_public": true, "caption": "", "data_licence": "OGL", "created": "2024-06-05T08:07:25.676352+01:00", "last_changed": "2024-06-05T08:07:25.676352+01:00", "columns": [ { "name": "csvbase_row_id", "type": "integer" }, { "name": "file", "type": "string" }, { "name": "ref", "type": "string" }, { "name": "codice", "type": "string" }, { "name": "descrizione", "type": "string" }, { "name": "indirizzo", "type": "string" }, { "name": "comune", "type": "string" }, { "name": "ultimo_fitto_mensile", "type": "float" } ], "approx_size": 8894, "page": { "rows": [ { "row": { "file": "input", "ref": "01_table_01", "codice": "UI_11140002", "descrizione": "Alloggio", "indirizzo": "VIALE VENEZIA 11", "comune": "ANNONE VENETO", "ultimo_fitto_mensile": 20.73 }, "row_id": 1, "url": "https://csvbase.com/aborruso/elenco-immobili-in-proprieta-ater-venezia-gestione-erp/rows/1" } ], "previous_page_url": null, "next_page_url": "https://csvbase.com/aborruso/elenco-immobili-in-proprieta-ater-venezia-gestione-erp?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.
GET
from https://csvbase.com/aborruso/elenco-immobili-in-proprieta-ater-venezia-gestione-erp
You'll need to follow the next_page_url
urls (described
above) to get to the end of the table.
Rows from aborruso/elenco-immobili-in-proprieta-ater-venezia-gestione-erp look like this in JSON:
{ "row": { "file": "input", "ref": "01_table_01", "codice": "UI_11140002", "descrizione": "Alloggio", "indirizzo": "VIALE VENEZIA 11", "comune": "ANNONE VENETO", "ultimo_fitto_mensile": 20.73 }, "row_id": 1, "url": "https://csvbase.com/aborruso/elenco-immobili-in-proprieta-ater-venezia-gestione-erp/rows/1" }
POST
to https://<some_user>:<some_api_key>@csvbase.com/aborruso/elenco-immobili-in-proprieta-ater-venezia-gestione-erp/rows/
{ "row": { "file": "input", "ref": "01_table_01", "codice": "UI_11140002", "descrizione": "Alloggio", "indirizzo": "VIALE VENEZIA 11", "comune": "ANNONE VENETO", "ultimo_fitto_mensile": 20.73 } }
{ "row": { "file": "input", "ref": "01_table_01", "codice": "UI_11140002", "descrizione": "Alloggio", "indirizzo": "VIALE VENEZIA 11", "comune": "ANNONE VENETO", "ultimo_fitto_mensile": 20.73 }, "row_id": 1, "url": "https://csvbase.com/aborruso/elenco-immobili-in-proprieta-ater-venezia-gestione-erp/rows/1" }
Status code 201 upon success.
GET
from https://csvbase.com/aborruso/elenco-immobili-in-proprieta-ater-venezia-gestione-erp/rows/1
No body is provided with this request. Status code 200 upon success.
{ "row": { "file": "input", "ref": "01_table_01", "codice": "UI_11140002", "descrizione": "Alloggio", "indirizzo": "VIALE VENEZIA 11", "comune": "ANNONE VENETO", "ultimo_fitto_mensile": 20.73 }, "row_id": 1, "url": "https://csvbase.com/aborruso/elenco-immobili-in-proprieta-ater-venezia-gestione-erp/rows/1" }
PUT
to https://<some_user>:<some_api_key>@csvbase.com/aborruso/elenco-immobili-in-proprieta-ater-venezia-gestione-erp/rows/1
{ "row": { "file": "input", "ref": "01_table_01", "codice": "UI_11140002", "descrizione": "Alloggio", "indirizzo": "VIALE VENEZIA 11", "comune": "ANNONE VENETO", "ultimo_fitto_mensile": 20.73 }, "row_id": 1, "url": "https://csvbase.com/aborruso/elenco-immobili-in-proprieta-ater-venezia-gestione-erp/rows/1" }
Upon success the body you sent will be echoed back, with status code 200.
DELETE
from https://<some_user>:<some_api_key>@csvbase.com/aborruso/elenco-immobili-in-proprieta-ater-venezia-gestione-erp/rows/1
No body is required. Status code 204 upon success.