JavaScript and Node.js SDK for OpenFGA


This is an autogenerated JavaScript SDK for OpenFGA. It provides a wrapper around the OpenFGA API definition, and includes TS typings.
Table of Contents
About
OpenFGA is an open source Fine-Grained Authorization solution inspired by Google’s Zanzibar paper. It was created by the FGA team at Auth0 based on Auth0 Fine-Grained Authorization (FGA), available under a permissive license (Apache-2) and welcomes community contributions.
OpenFGA is designed to make it easy for application builders to model their permission layer, and to add and integrate fine-grained authorization into their applications. OpenFGA’s design is optimized for reliability and low latency at a high scale.
Resources
Installation
Using npm:
npm install @openfga/sdk
Using yarn:
yarn add @openfga/sdk
Supported Node.js Versions
For details on the supported Node.js versions and our support policy, see SUPPORTED_RUNTIMES.md.
Getting Started
Initializing the API Client
Learn how to initialize your SDK
We strongly recommend you initialize the OpenFgaClient only once and then re-use it throughout your app, otherwise you will incur the cost of having to re-initialize multiple times or at every request, the cost of reduced connection pooling and re-use, and would be particularly costly in the client credentials flow, as that flow will be performed on every request.
The OpenFgaClient will by default retry API requests up to 3 times on 429 and 5xx errors.
No Credentials
const { OpenFgaClient } = require('@openfga/sdk');
const fgaClient = new OpenFgaClient({
apiUrl: process.env.FGA_API_URL,
storeId: process.env.FGA_STORE_ID,
authorizationModelId: process.env.FGA_MODEL_ID,
});
API Token
const { OpenFgaClient, CredentialsMethod } = require('@openfga/sdk');
const fgaClient = new OpenFgaClient({
apiUrl: process.env.FGA_API_URL,
storeId: process.env.FGA_STORE_ID,
authorizationModelId: process.env.FGA_MODEL_ID,
credentials: {
method: CredentialsMethod.ApiToken,
config: {
token: process.env.FGA_API_TOKEN,
}
}
});
Client Credentials
const { OpenFgaClient, CredentialsMethod } = require('@openfga/sdk');
const fgaClient = new OpenFgaClient({
apiUrl: process.env.FGA_API_URL,
storeId: process.env.FGA_STORE_ID,
authorizationModelId: process.env.FGA_MODEL_ID,
credentials: {
method: CredentialsMethod.ClientCredentials,
config: {
apiTokenIssuer: process.env.FGA_API_TOKEN_ISSUER,
apiAudience: process.env.FGA_API_AUDIENCE,
clientId: process.env.FGA_CLIENT_ID,
clientSecret: process.env.FGA_CLIENT_SECRET,
}
}
});
You can set default headers that will be sent with every request during client initialization:
const { OpenFgaClient } = require('@openfga/sdk');
const fgaClient = new OpenFgaClient({
apiUrl: process.env.FGA_API_URL,
storeId: process.env.FGA_STORE_ID,
authorizationModelId: process.env.FGA_MODEL_ID,
baseOptions: {
headers: {
"X-Custom-Header": "default-value",
"X-Request-Source": "my-app",
}
}
});
You can also send custom headers on a per-request basis by using the options parameter. Custom headers will override any default headers set in the client configuration.
const result = await fgaClient.check({
user: "user:anne",
relation: "viewer",
object: "document:roadmap",
}, {
headers: {
"X-Request-ID": "123e4567-e89b-12d3-a456-426614174000",
"X-Custom-Header": "custom-value",
}
});
Get your Store ID
You need your store id to call the OpenFGA API (unless it is to call the CreateStore or ListStores methods).
If your server is configured with authentication enabled, you also need to have your credentials ready.
Calling the API
Note regarding casing in the OpenFgaClient:
All input parameters are in camelCase, all response parameters will match the API and are in snake_case.
Note: The Client interface might see several changes over the next few months as we get more feedback before it stabilizes.
Stores
List Stores
Get a paginated list of stores.
API Documentation
const options = { pageSize: 10, continuationToken: "..." };
const { stores } = await fgaClient.listStores(options);
Create Store
Initialize a store.
API Documentation
const { id: storeId } = await fgaClient.createStore({
name: "FGA Demo Store",
});
Get Store
Get information about the current store.
API Documentation
const store = await fgaClient.getStore();
Delete Store
Delete a store.
API Documentation
await fgaClient.deleteStore();
Authorization Models
Read Authorization Models
Read all authorization models in the store.
API Documentation
Requires a client initialized with a storeId
const options = { pageSize: 10, continuationToken: "..." };
const { authorization_models: authorizationModels } = await fgaClient.readAuthorizationModels(options);
Write Authorization Model
Create a new authorization model.
API Documentation
Note: To learn how to build your authorization model, check the Docs at https://openfga.dev/docs.
Learn more about the OpenFGA configuration language.
You can use the OpenFGA Syntax Transformer to convert between the friendly DSL and the JSON authorization model.
const { authorization_model_id: id } = await fgaClient.writeAuthorizationModel({
schema_version: "1.1",
type_definitions: [{
type: "user",
}, {
type: "document",
relations: {
"writer": { "this": {} },
"viewer": {
"union": {
"child": [
{ "this": {} },
{ "computedUserset": {
"object": "",
"relation": "writer" }
}
]
}
}
} }],
});
Read a Single Authorization Model
Read a particular authorization model.
const options = {};
options.authorizationModelId = "01GXSA8YR785C4FYS3C0RTG7B1";
const { authorization_model: authorizationModel } = await fgaClient.readAuthorizationModel(options);
Read the Latest Authorization Model
Reads the latest authorization model (note: this ignores the model id in configuration).
API Documentation
const { authorization_model: authorizationModel } = await fgaClient.readLatestAuthorizationModel();
Relationship Tuples
Read Relationship Tuple Changes (Watch)
Reads the list of historical relationship tuple writes and deletes.
API Documentation
const type = 'document';
const startTime = "2022-01-01T00:00:00Z"
const options = {
pageSize: 25,
continuationToken: 'eyJwayI6IkxBVEVTVF9OU0NPTkZJR19hdXRoMHN0b3JlIiwic2siOiIxem1qbXF3MWZLZExTcUoyN01MdTdqTjh0cWgifQ==',
};
const response = await fgaClient.readChanges({ type, startTime }, options);
Read Relationship Tuples
Reads the relationship tuples stored in the database. It does not evaluate nor exclude invalid tuples according to the authorization model.
API Documentation
const body = {
user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b",
relation: "viewer",
object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a",
};
const body = {
user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b",
object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a",
};
const body = {
user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b",
relation: "viewer",
object: "document:",
};
const body = {
user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b",
object: "document:",
};
const body = {
object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a",
};
const body = {};
const { tuples } = await fgaClient.read(body);
Write (Create and Delete) Relationship Tuples
Create and/or delete relationship tuples to update the system state.
API Documentation
Transaction mode (default)
By default, write runs in a transaction mode where any invalid operation (deleting a non-existing tuple, creating an existing tuple, one of the tuples was invalid) or a server error will fail the entire operation.
const options = {};
options.authorizationModelId = "01GXSA8YR785C4FYS3C0RTG7B1";
await fgaClient.write({
writes: [{ user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b", relation: "viewer", object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a" }],
deletes: [{ user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b", relation: "editor", object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a" }],
}, options);
await fgaClient.writeTuples([{ user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b", relation: "viewer", object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a" }], options);
await fgaClient.deleteTuples([{ user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b", relation: "editor", object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a" }], options);
Non-transaction mode
The SDK will split the writes into separate requests and send them in parallel chunks (default = 1 item per chunk, each chunk is a transaction).
// if you'd like to disable the transaction mode for writes (requests will be sent in parallel writes)
options.transaction = {
disable: true,
maxPerChunk: 1, // defaults to 1 - each chunk is a transaction (even in non-transaction mode)
maxParallelRequests: 10, // max requests to issue in parallel
};
const response = await fgaClient.write({
writes: [{ user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b", relation: "viewer", object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a" }],
deletes: [{ user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b", relation: "editor", object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a" }],
}, options);
/*
response = {
writes: [{ tuple_key: { user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b", relation: "viewer", object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a", status: "success" } }],
deletes: [{ tuple_key: { user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b", relation: "editor", object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a", status: "failure", err: <FgaError ...> } }],
};
*/
Conflict Options for Write Operations
The SDK supports conflict options for write operations, allowing you to control how the API handles duplicate writes and missing deletes.
Note: This requires OpenFGA v1.10.0 or later.
Using Conflict Options with Write
const options = {
conflict: {
onDuplicateWrites: ClientWriteRequestOnDuplicateWrites.Ignore,
onMissingDeletes: ClientWriteRequestOnMissingDeletes.Ignore,
}
};
const body = {
writes: [{
user: 'user:anne',
relation: 'writer',
object: 'document:2021-budget',
}],
deletes: [{
user: 'user:bob',
relation: 'reader',
object: 'document:2021-budget',
}],
};
const response = await fgaClient.write(body, options);
Using Conflict Options with WriteTuples
const tuples = [{
user: 'user:anne',
relation: 'writer',
object: 'document:2021-budget',
}];
const options = {
conflict: {
onDuplicateWrites: ClientWriteRequestOnDuplicateWrites.Ignore,
}
};
const response = await fgaClient.writeTuples(tuples, options);
Using Conflict Options with DeleteTuples
const tuples = [{
user: 'user:bob',
relation: 'reader',
object: 'document:2021-budget',
}];
const options = {
conflict: {
onMissingDeletes: OnMissingDelete.Ignore,
}
};
const response = await fgaClient.deleteTuples(tuples, options);
Conflict Options Behavior
-
onDuplicateWrites:
ClientWriteRequestOnDuplicateWrites.Error (default): Returns an error if an identical tuple already exists (matching on user, relation, object, and condition)
ClientWriteRequestOnDuplicateWrites.Ignore: Treats duplicate writes as no-ops, allowing idempotent write operations
-
onMissingDeletes:
ClientWriteRequestOnMissingDeletes.Error (default): Returns an error when attempting to delete a tuple that doesn’t exist
ClientWriteRequestOnMissingDeletes.Ignore: Treats deletes of non-existent tuples as no-ops, allowing idempotent delete operations
Important: If a Write request contains both idempotent (ignore) and non-idempotent (error) operations, the most restrictive action (error) will take precedence. If a condition fails for a sub-request with an error flag, the entire transaction will be rolled back.
Relationship Queries
Check
Check if a user has a particular relation with an object.
API Documentation
const options = {
authorizationModelId: "01GXSA8YR785C4FYS3C0RTG7B1",
};
const result = await fgaClient.check({
user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b",
relation: "viewer",
object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a",
}, options);
Batch Check
Similar to check, but instead of checking a single user-object relationship, accepts a list of relationships to check. Requires OpenFGA version 1.8.0 or greater.
API Documentation
Note: The order of batchCheck results is not guaranteed to match the order of the checks provided. Use correlationId to pair responses with requests.
const options = {
authorizationModelId: "01GXSA8YR785C4FYS3C0RTG7B1",
}
const corrId = randomUUID();
const { result } = await fgaClient.batchCheck({
checks: [
{
user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b",
relation: "viewer",
object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a",
context: {
ViewCount: 100
},
correlationId: corrId,
},
{
user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b",
relation: "viewer",
object: "document:7772ab2a-d83f-756d-9397-c5ed9f3cb888",
}
]
}, options);
const userAllowed = result.filter(r => r.correlationId === corrId);
console.log(`User is allowed access to ${userAllowed.length} documents`);
userAllowed.forEach(item => {
console.log(`User is allowed access to ${item.request.object}`);
});
If you are using an OpenFGA version less than 1.8.0, you can use the clientBatchCheck function,
which calls check in parallel. It will return allowed: false if it encounters an error, and will return the error in the body.
If 429s or 5xxs are encountered, the underlying check will retry up to 3 times before giving up.
const { responses } = await fgaClient.clientBatchCheck([{
user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b",
relation: "viewer",
object: "document:0192ab2d-d36e-7cb3-a4a8-5d1d67a300c5",
}, {
user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b",
relation: "member",
object: "document:0192ab2d-d36e-7cb3-a4a8-5d1d67a300c5",
}, {
user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b",
relation: "viewer",
object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a",
contextualTuples: [{
user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b",
relation: "writer",
object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a"
}],
}], options);
Expand
Expands the relationships in userset tree format.
API Documentation
const options = {};
options.authorizationModelId = "01GXSA8YR785C4FYS3C0RTG7B1";
const { tree } = await fgaClient.expand({
relation: "viewer",
object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a",
}, options);
List Objects
List the objects of a particular type that the user has a certain relation to.
API Documentation
const options = {};
options.authorizationModelId = "01GXSA8YR785C4FYS3C0RTG7B1";
const response = await fgaClient.listObjects({
user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b",
relation: "viewer",
type: "document",
contextualTuples: [{
user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b",
relation: "writer",
object: "document:0192ab2d-d36e-7cb3-a4a8-5d1d67a300c5"
}],
}, options);
Streamed List Objects
List objects of a particular type that the user has access to, using the streaming API.
The Streamed ListObjects API is very similar to the ListObjects API, with two key differences:
- Streaming Results: Instead of collecting all objects before returning a response, it streams them to the client as they are collected.
- No Pagination Limit: Returns all results without the 1000-object limit of the standard ListObjects API.
This is particularly useful when querying computed relations that may return large result sets.
API Documentation
const options = {};
options.authorizationModelId = "01GXSA8YR785C4FYS3C0RTG7B1";
const objects = [];
for await (const response of fgaClient.streamedListObjects(
{ user: "user:anne", relation: "can_read", type: "document" },
{ consistency: ConsistencyPreference.HigherConsistency }
)) {
objects.push(response.object);
}
List Relations
List the relations a user has with an object. This wraps around BatchCheck to allow checking multiple relationships at once.
Note: Any error encountered when checking any relation will be treated as allowed: false;
const options = {};
options.authorization_model_id = "1uHxCSuTP0VKPYSnkq1pbb1jeZw";
const response = await fgaClient.listRelations({
user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b",
object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a",
relations: ["can_view", "can_edit", "can_delete"],
contextualTuples: [{
user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b",
relation: "writer",
object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a"
}],
}, options);
List Users
List the users who have a certain relation to a particular type.
API Documentation
const options = {};
options.authorization_model_id = "1uHxCSuTP0VKPYSnkq1pbb1jeZw";
const userFilters = [{type: "user"}];
const response = await fgaClient.listUsers({
object: {
type: "document",
id: "roadmap"
},
relation: "can_read",
user_filters: userFilters,
context: {
"view_count": 100
},
contextualTuples:
[{
user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b",
relation: "editor",
object: "folder:product"
}, {
user: "folder:product",
relation: "parent",
object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a"
}]
}, options);
Assertions
Read Assertions
Read assertions for a particular authorization model.
API Documentation
const options = {};
options.authorizationModelId = "01GXSA8YR785C4FYS3C0RTG7B1";
const response = await fgaClient.readAssertions(options);
Write Assertions
Update the assertions for a particular authorization model.
API Documentation
const options = {};
options.authorizationModelId = "01GXSA8YR785C4FYS3C0RTG7B1";
const response = await fgaClient.writeAssertions([{
user: "user:81684243-9356-4421-8fbf-a4f8d36aa31b",
relation: "viewer",
object: "document:0192ab2a-d83f-756d-9397-c5ed9f3cb69a",
expectation: true,
}], options);
Calling Other Endpoints
In certain cases you may want to call other APIs not yet wrapped by the SDK. You can do so by using the executeApiRequest method available on the OpenFgaClient. It allows you to make raw HTTP calls to any OpenFGA endpoint by specifying the HTTP method, path, body, query parameters, and path parameters, while still honoring the client configuration (authentication, telemetry, retries, and error handling).
For streaming endpoints, use executeStreamedApiRequest instead.
This is useful when:
- You want to call a new endpoint that is not yet supported by the SDK
- You are using an earlier version of the SDK that doesn’t yet support a particular endpoint
- You have a custom endpoint deployed that extends the OpenFGA API
Example: Calling a Custom Endpoint with POST
const { OpenFgaClient } = require('@openfga/sdk');
const fgaClient = new OpenFgaClient({
apiUrl: process.env.FGA_API_URL,
storeId: process.env.FGA_STORE_ID,
});
const response = await fgaClient.executeApiRequest({
operationName: 'CustomEndpoint',
method: 'POST',
path: '/stores/{store_id}/custom-endpoint',
pathParams: { store_id: process.env.FGA_STORE_ID },
body: {
user: 'user:bob',
action: 'custom_action',
resource: 'resource:123',
},
queryParams: {
page_size: 20,
},
});
console.log('Response:', response);
Example: Calling an Existing Endpoint with GET
const stores = await fgaClient.executeApiRequest({
operationName: 'ListStores',
method: 'GET',
path: '/stores',
queryParams: {
page_size: 10,
continuation_token: 'eyJwayI6...',
},
});
console.log('Stores:', stores);
Example: Using Path Parameters
Path parameters are specified in the path using {param_name} syntax and are replaced with URL-encoded values from the pathParams object:
const response = await fgaClient.executeApiRequest({
operationName: 'GetAuthorizationModel',
method: 'GET',
path: '/stores/{store_id}/authorization-models/{model_id}',
pathParams: {
store_id: 'your-store-id',
model_id: 'your-model-id',
},
});
Example: Calling a Streaming Endpoint
For streaming endpoints (e.g. streamed-list-objects), use executeStreamedApiRequest instead of executeApiRequest. This returns a raw Node.js readable stream. To parse the newline-delimited JSON (NDJSON) response into individual objects, use the parseNDJSONStream helper exported by the SDK:
const { OpenFgaClient, parseNDJSONStream } = require('@openfga/sdk');
const fgaClient = new OpenFgaClient({
apiUrl: process.env.FGA_API_URL,
storeId: process.env.FGA_STORE_ID,
});
const streamResponse = await fgaClient.executeStreamedApiRequest({
operationName: 'StreamedListObjects',
method: 'POST',
path: '/stores/{store_id}/streamed-list-objects',
pathParams: { store_id: process.env.FGA_STORE_ID },
body: {
authorization_model_id: process.env.FGA_MODEL_ID,
user: 'user:alice',
relation: 'reader',
type: 'document',
},
});
for await (const item of parseNDJSONStream(streamResponse)) {
console.log('Object:', item.object);
}
Note: Unlike executeApiRequest (which wraps the response in a CallResult with a $response property), executeStreamedApiRequest returns the raw stream directly. parseNDJSONStream handles chunked data, partial lines, and buffer flushing automatically. It accepts Node.js Readable streams, AsyncIterables, or even plain strings and Buffers.
Retries
If a network request fails with a 429 or 5xx error from the server, the SDK will automatically retry the request up to 3 times with a minimum wait time of 100 milliseconds between each attempt.
To customize this behavior, create an object with maxRetry and minWaitInMs properties. maxRetry determines the maximum number of retries (up to 15), while minWaitInMs sets the minimum wait time between retries in milliseconds.
Apply your custom retry values by setting to retryParams on the configuration object passed to the OpenFgaClient call.
const { OpenFgaClient } = require('@openfga/sdk');
const fgaClient = new OpenFgaClient({
apiUrl: process.env.FGA_API_URL,
storeId: process.env.FGA_STORE_ID,
authorizationModelId: process.env.FGA_MODEL_ID,
retryParams: {
maxRetry: 3,
minWaitInMs: 250
}
});
API Endpoints
| Method |
HTTP request |
Description |
| ListStores |
GET /stores |
List all stores |
| CreateStore |
POST /stores |
Create a store |
| GetStore |
GET /stores/{store_id} |
Get a store |
| DeleteStore |
DELETE /stores/{store_id} |
Delete a store |
| ReadAuthorizationModels |
GET /stores/{store_id}/authorization-models |
Return all the authorization models for a particular store |
| WriteAuthorizationModel |
POST /stores/{store_id}/authorization-models |
Create a new authorization model |
| ReadAuthorizationModel |
GET /stores/{store_id}/authorization-models/{id} |
Return a particular version of an authorization model |
| ReadChanges |
GET /stores/{store_id}/changes |
Return a list of all the tuple changes |
| Read |
POST /stores/{store_id}/read |
Get tuples from the store that matches a query, without following userset rewrite rules |
| Write |
POST /stores/{store_id}/write |
Add or delete tuples from the store |
| Check |
POST /stores/{store_id}/check |
Check whether a user is authorized to access an object |
| BatchCheck |
POST /stores/{store_id}/batch-check |
Similar to check, but accepts a list of relations to check |
| Expand |
POST /stores/{store_id}/expand |
Expand all relationships in userset tree format, and following userset rewrite rules. Useful to reason about and debug a certain relationship |
| ListObjects |
POST /stores/{store_id}/list-objects |
[EXPERIMENTAL] Get all objects of the given type that the user has a relation with |
| ReadAssertions |
GET /stores/{store_id}/assertions/{authorization_model_id} |
Read assertions for an authorization model ID |
| WriteAssertions |
PUT /stores/{store_id}/assertions/{authorization_model_id} |
Upsert assertions for an authorization model ID |
Models
Models
OpenTelemetry
This SDK supports producing metrics that can be consumed as part of an OpenTelemetry setup. For more information, please see the documentation
Contributing
See CONTRIBUTING for details.
Author
OpenFGA
License
This project is licensed under the Apache-2.0 license. See the LICENSE file for more info.
The code in this repo was auto generated by OpenAPI Generator from a template based on the typescript-axios template and go template, licensed under the Apache License 2.0.
评论