Overview
Read and manage Jet Admin data, users, teams, and application settings.
Read and manage connected records, application users, and teams through the Jet Admin REST API. Use the JavaScript SDK from a JavaScript or TypeScript application.
Base URLs
Records, SQL, Users, Teams, and Resources
https://data.jetadmin.io
Projects, Pages, and HTTP proxy
https://api.jetadmin.io/api
Authentication
Records and SQL use the selected resource's static API token. Users and Teams use the Built-in tools static API token. Pass the token directly in the Authorization header, using the format shown in the resource's generated API.
Authorization: {{api_token}}Projects and Pages use Bearer authentication; the HTTP proxy documents JWT authentication. See Servers & Authentication for details.
URL identifiers
https://data.jetadmin.io/projects/{{project_id}}/prod/{{resource_name}}/models/{{model_id}}{{project_id}}
Project identifier in your resource API URL
{{resource_name}}
Connected resource's API name
{{model_id}}
Collection/model identifier in that resource
{{api_token}}
API token accepted by the selected resource
Copy these identifiers from Data → your resource → API. The paths shown here use prod, the published production environment. Users and Teams use the fixed Built-in tools resource __jet_app__, with users and groups as their model identifiers.
Double braces mark values to replace in examples. Interactive OpenAPI endpoints use the equivalent standard single-brace path parameters.
Make your first request
Replace the placeholders before running:
Explore the API
List, retrieve, create, update, delete, aggregate, and group records
Execute read-only SELECT queries on supported resources
List, retrieve, create, update, and delete application users
List, retrieve, and update teams
Reload resource and Built-in tools structure caches
Projects and page settings
Integrations
HTTP proxy
Pagination and errors
List endpoints document page (default 1), _per_page (default 25, maximum 10,000), and _no_pagination (up to 10,000 records). Responses contain count, next, previous, and results. Check the selected resource's generated API for supported filters and operations.
Use each endpoint's documented status codes and response schema. Error bodies vary; do not assume a universal error envelope. Rate limits are not specified in the supplied API definitions.
Download OpenAPI specifications
Was this helpful?