The Export URL

Every endpoint you create in CSV Getter produces a unique URL. This page explains the URL structure, how to use parameters, authentication, and shows complete real-world examples.

URL Anatomy

https://api.csvgetter.com/<endpoint_id>?type=json_records&sql=SELECT * FROM csvgetter WHERE status='Active'
└──────────┬──────────────┘└─────┬─────┘└────────────────────────────┬────────────────────────────────────┘
       Base URL              Endpoint ID                      URL Parameters

Base URL

All endpoint URLs use the same base:

https://api.csvgetter.com

Endpoint ID

A unique alphanumeric identifier generated when you create the endpoint. Examples:

https://api.csvgetter.com/abc123def456
https://api.csvgetter.com/0b6VSN8fXQ8U

There is also an alternate path format that works identically:

https://api.csvgetter.com/files/abc123def456

URL Parameters

Query parameters are appended after ? and separated by &. They modify the output without changing the endpoint configuration.


How Parameters Chain

You can combine any number of parameters by joining them with &:

Order doesn't matter. These are equivalent:

URL Encoding

When your parameters contain special characters (spaces, quotes, etc.), they must be URL-encoded. Most HTTP clients and browsers do this automatically, but if you're building URLs manually:

Character
Encoded

Space

%20 or +

=

%3D

&

%26

'

%27

*

%2A

>

%3E

<

%3C

Example — SQL query with spaces and comparisons:

Raw SQL:

URL-encoded:

Tip: Use the URL Wizard in the CSV Getter dashboard to build URLs with parameters automatically.

Tip: You can also use our URL encoderarrow-up-right


Authentication

Endpoints can optionally require a Bearer token. When auth is enabled:

Request with auth:

Without the header (or wrong token), you'll get:

The Bearer token is set when configuring your endpoint in the dashboard. You can change it at any time.

Auth Error Responses

Scenario
Status Code
Error Message

No Authorization header

401

Authorization header is required

Missing Bearer prefix

401

Invalid Authorization header format

Wrong token

401

Invalid Authorization header


Complete Real-World Example

Scenario

You have an Airtable base tracking job applicants. You want to:

  1. Get only applicants with status "Interview"

  2. Return only their name, email, and application date

  3. Output as JSON

  4. Get an email notification when the export runs

The URL

Broken down:

Part
Value
Purpose

Base URL

https://api.csvgetter.com/abc123def456

Your endpoint

type

json_records

Output as JSON array of objects

sql

SELECT name, email, application_date FROM csvgetter WHERE status='Interview' ORDER BY application_date DESC

Filter to interviews, select 3 columns, sort by date

email_me

true

Send you an email notification

Response (200 OK)


Previewing vs. Live Hits

When you use the URL Wizard or preview an endpoint in the dashboard, CSV Getter returns a sample (up to 10 rows) and does not deduct a credit.

When you hit the URL directly (browser, code, cURL, Excel, etc.), it returns the full dataset and deducts 1 credit.


Error Responses

All error responses are JSON objects with an error field and an HTTP status code:

See Troubleshooting for a full list of error codes and solutions.


Next Steps

  • URL Parameters — Full reference for all parameters.

  • The SQL Parameter — Master data filtering and transformation.

  • The Type Parameter — All output formats explained.

  • Combining URL Parameters — Real workflow recipes.

Last updated