Khulnasoft
The Khulnasoft GraphQL API is automatically reflected from your database's schema using pg_graphql. It supports:
- Basic CRUD operations (Create/Read/Update/Delete)
- Support for Tables, Views, Materialized Views, and Foreign Tables
- Arbitrarily deep relationships among tables/views
- User defined computed fields
- Postgres' security model - including Row Level Security, Roles, and Grants
All requests resolve in a single round-trip leading to fast response times and high throughput.
If you haven't created a Khulnasoft project, do that here so you can follow along with the guide.
Quickstart
https://<PROJECT_REF>.khulnasoft.co/graphql/v1
is your project's GraphQL API endpoint. See PROJECT_REF for instructions on finding your project's reference. Note that the url does not allow a trailing /
.
To access the API you MUST provide your project's API key as a header in every request. For example see line 2 of the cURL request below.
1 2 3 4 |
|
For user authentication, pass an Authorization
header e.g.
1 |
|
The fastest way to get started with GraphQL on Khulnasoft is using the GraphQL IDE (GraphiQL) built directly into Khulnasoft Studio.
Clients
If you're new to GraphQL or Khulnasoft, we strongly recommend starting with Khulnasoft GraphQL by following the Khulnasoft Studio guide.
For more experienced users, or when you're ready to productionize your application, access the API using khulnasoft-js, GraphiQL, or any HTTP client, for example cURL.
Khulnasoft Studio
The easiest way to make a GraphQL request with Khulnasoft is to use Khulnasoft Studio's builtin GraphiQL IDE.
You can access GraphiQL here by selecting the relevant project. Alternatively, navigate there within Studio at API Docs > GraphQL > GraphiQL
.
Type queries in the central query editor and use the green icon to submit requests to the server. Results are shown in the output display to the right of the editor.
To explore the API visually, select the docs icon shown below and navigate through each type to see how they connect to the Graph.
pg_graphql mirrors the structure of the project's SQL schema in the GraphQL API. If your project is new and empty, the GraphQL API will be empty as well, with the exception of basic introspection types. For a more interesting result, go to the SQL or table editor and create a table.
Head back to GraphiQL to see the new table reflected in your GraphQL API's Query and Mutation types.
If you'd like your type and field names to match the GraphQL convention of PascalCase
for types and camelCase
for fields, check out the pg_graphql inflection guide.
HTTP Request
To access the GraphQL API over HTTP, first collect your project reference and API Key.
cURL
To hit the Khulnasoft GraphQL API using cURL, submit a POST
request to your GraphQL API's URL shown below, substituting in your PROJECT_REF and passing the project's API_KEY as the apiKey
header:
1 2 3 4 |
|
In that example, the GraphQL query
is
1 2 3 4 5 6 7 8 9 |
|
and there are no variables
1 |
|
khulnasoft-js
The JS ecosystem supports multiple prominent GraphQL frameworks. khulnasoft-js is unopinionated about your GraphQL tooling and can integrate with all of them.
For an example integration, check out the Relay guide, complete with Khulnasoft Auth support.
GraphiQL
If you'd prefer to connect to Khulnasoft GraphQL using an external IDE like GraphiQL, save the HTML snippet below as khulnasoft_graphiql.html
and open it in your browser. Be sure to substitute in your PROJECT_REF and API_KEY beneath the EDIT BELOW
comment:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 |
|
Schema & Table Visibility
pg_graphql uses Postgres' search_path
and permissions system to determine which schemas and entities are exposed in the GraphQL schema. By default on Khulnasoft, tables, views, and functions in the public
schema are visible to anonymous (anon
) and logged in (authenticated
) roles.
Remove a Table from the API
To remove a table from the GraphQL API, you can revoke permission on that table from the the relevant role. For example, to remove table foo
from the API for anonymous users you could run:
1 |
|
You can similarly revoke permissions using the more granular insert
, update
, delete
, and truncate
permissions to remove individual entrypoints in the GraphQL API. For example, revoking update
permission removes the updateFooCollection
entrypoing in the API's Mutation
type.
Add a Schema to the API
Adding a schema to the GraphQL API is a two step process.
First, we need to add the new schema to the API search path. In the example below, we add a comma separated value for the new app
schema:
Next, make sure the schema and entities (tables/views/functions) that you intend to expose are accessible by the relevant roles. For example, to match permissions from the public schema:
1 2 3 4 5 6 7 |
|
Note that in practice you likely prefer a more secure set of permissions, particularly for anonymous API users.
Version Management
To maximize stability, you are in control of when to upgrade your GraphQL API. To see which version of pg_graphql you have, and the highest upgrade version available, execute:
1 |
|
Which returns a table, for example:
name | default_version | installed_version | comment |
---|---|---|---|
pg_graphql | 1.2.0 | 1.1.0 | GraphQL support |
The default_version
is the highest version available on your database. The installed_version
is the version currently enabled in your database.
If the two differ, as in the example, you can upgrade your installed version by running:
1 2 |
|
To upgrade your GraphQL API with 0 downtime.
When making a decision to upgrade, you can review features of the upgraded version in the changelog.
Always test a new version of pg_graphql extensively on a development or staging instance before updating your production instance. pg_graphql follows SemVer, which makes API backwards compatibility relatively safe for minor and patch updates. Even so, it's critical to verify that changes do not negatively impact the specifics of your project's API in other ways, e.g. requests/sec or CPU load.
Local Development
When starting a local project through the Khulnasoft CLI, the output of khulnasoft start
provides the information needed to call the GraphQL API directly. You can also use the Khulnasoft Studio url to access the builtin GraphiQL IDE.
1 2 3 4 5 6 7 8 9 10 11 12 |
|
Term Reference
Project Reference (PROJECT_REF)
Your Khulnasoft project reference or PROJECT_REF is a 20 digit unique identifier for your project, for example bvykdyhlwawojivopztl
.
The project reference is used throughout your khulnasoft application including the project's API URL. You can find the project reference in by logging
in to Khulnasoft Studio and navigating to Settings > General > Project Settings > Reference ID
API Key (API_KEY)
Your Khulnasoft API Key is a public value that must be sent with every API request. The key is visible in Khulnasoft Studio at Settings > API > Project API keys