Table of contents

1. The basics: auth and content negotations
   1. Authentication
   2. Content negotiation
2. The API: endpoint-by-endpoint
   1. Tables
      1. Reading a table
   2. Rows
      1. Creating a new row
      2. Reading a row
      3. Updating an existing row
      4. Deleting a row

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/Fenix/Bexar-County-Tax-Delinquency

Basic auth is widely supported and is usually accepted anywhere that accepts urls.

However, Fenix/Bexar-County-Tax-Delinquency 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/Fenix/Bexar-County-Tax-Delinquency.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:

1. users
2. tables
3. 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": "Bexar-County-Tax-Delinquency",
    "is_public": true,
    "caption": "",
    "licence": null,
    "created": "2026-02-05T19:57:39.839080+00:00",
    "last_changed": "2026-02-05T19:57:39.795246+00:00",
    "columns": [
        {
            "name": "csvbase_row_id",
            "type": "integer"
        },
        {
            "name": "2022TA101260 7080 RIMWOOD LIVE OAK 78233 2022 ",
            "type": "string"
        },
        {
            "name": "8K-",
            "type": "string"
        },
        {
            "name": "15K HIGH",
            "type": "string"
        }
    ],
    "approx_size": 4,
    "page": {
        "rows": [
            {
                "row": {
                    "2022TA101260 7080 RIMWOOD LIVE OAK 78233 2022 ": "2023TA100927 1803 TIERRA NUEVA CHINA GROVE 78263 2023 ",
                    "8K-": "3K-",
                    "15K HIGH": "8K HIGH"
                },
                "row_id": 1,
                "url": "https://csvbase.com/Fenix/Bexar-County-Tax-Delinquency/rows/1"
            }
        ],
        "previous_page_url": null,
        "next_page_url": "https://csvbase.com/Fenix/Bexar-County-Tax-Delinquency?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/Fenix/Bexar-County-Tax-Delinquency

You'll need to follow the next_page_url urls (described above) to get to the end of the table.

Rows

Rows from Fenix/Bexar-County-Tax-Delinquency look like this in JSON:

{
    "row": {
        "2022TA101260 7080 RIMWOOD LIVE OAK 78233 2022 ": "2023TA100927 1803 TIERRA NUEVA CHINA GROVE 78263 2023 ",
        "8K-": "3K-",
        "15K HIGH": "8K HIGH"
    },
    "row_id": 1,
    "url": "https://csvbase.com/Fenix/Bexar-County-Tax-Delinquency/rows/1"
}

Creating a new row

POST to https://<some_user>:<some_api_key>@csvbase.com/Fenix/Bexar-County-Tax-Delinquency/rows/

Example body

{
    "row": {
        "2022TA101260 7080 RIMWOOD LIVE OAK 78233 2022 ": "2023TA100927 1803 TIERRA NUEVA CHINA GROVE 78263 2023 ",
        "8K-": "3K-",
        "15K HIGH": "8K HIGH"
    }
}

Example response

{
    "row": {
        "2022TA101260 7080 RIMWOOD LIVE OAK 78233 2022 ": "2023TA100927 1803 TIERRA NUEVA CHINA GROVE 78263 2023 ",
        "8K-": "3K-",
        "15K HIGH": "8K HIGH"
    },
    "row_id": 1,
    "url": "https://csvbase.com/Fenix/Bexar-County-Tax-Delinquency/rows/1"
}

Status code 201 upon success.

Reading a row

GET from https://csvbase.com/Fenix/Bexar-County-Tax-Delinquency/rows/1

No body is provided with this request. Status code 200 upon success.

Example response

{
    "row": {
        "2022TA101260 7080 RIMWOOD LIVE OAK 78233 2022 ": "2023TA100927 1803 TIERRA NUEVA CHINA GROVE 78263 2023 ",
        "8K-": "3K-",
        "15K HIGH": "8K HIGH"
    },
    "row_id": 1,
    "url": "https://csvbase.com/Fenix/Bexar-County-Tax-Delinquency/rows/1"
}

Updating an existing row

PUT to https://<some_user>:<some_api_key>@csvbase.com/Fenix/Bexar-County-Tax-Delinquency/rows/1

Example body

{
    "row": {
        "2022TA101260 7080 RIMWOOD LIVE OAK 78233 2022 ": "2023TA100927 1803 TIERRA NUEVA CHINA GROVE 78263 2023 ",
        "8K-": "3K-",
        "15K HIGH": "8K HIGH"
    },
    "row_id": 1,
    "url": "https://csvbase.com/Fenix/Bexar-County-Tax-Delinquency/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/Fenix/Bexar-County-Tax-Delinquency/rows/1

No body is required. Status code 204 upon success.