How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Grist orgs API

Team sites and personal spaces are called 'orgs' in the API.

Grist orgs API is one of 17 APIs that Grist publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Organization. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 7 operations across 5 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 1.0.1.

Requests are made against a single base URL, https://{gristhost}/api.

7 operations 5 paths 7 schemas 1 DELETE4 GET2 PATCH

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.1
Base URL
https://docs.getgrist.com/api
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Grist orgs API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (Authorization: Bearer XXXXXXXXXXX) (ApiKey). By default, every request must be authenticated.

  • ApiKey — Access to the Grist API is controlled by an Authorization header, which should contain the word 'Bearer', followed by a space, followed by your API key.

Paths & Operations 7

Across 5 paths, the API surfaces 7 operations — 1 DELETE, 4 GET, 2 PATCH. Each is listed below with its method, path, parameters, and response codes.

orgs 7

Team sites and personal spaces are called 'orgs' in the API.

GET
/orgs
List the orgs you have access to
listOrgs → 200
GET
/orgs/{orgId}
Describe an org
describeOrg 1 param → 200
PATCH
/orgs/{orgId}
Modify an org
modifyOrg 1 param body → 200
DELETE
/orgs/{orgId}/{name}
Delete an org
deleteOrg 2 params → 200403404
GET
/orgs/{orgId}/access
List users with access to org
listOrgAccess 1 param → 200
PATCH
/orgs/{orgId}/access
Change who has access to org
modifyOrgAccess 1 param body → 200
GET
/orgs/{orgId}/usage
Get organization usage summary
getOrgUsage 1 param → 200

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Org (7 properties), User (3 properties), OrgAccessRead (1 property), OrgParameters (1 property). Each schema is shown below with its type and property counts.

OrgAccessWrite
object
1 property 1 required
User
object
3 properties 3 required
OrgParameters
object
1 property
Org
object
7 properties 7 required
OrgAccessRead
object
1 property 1 required
Orgs
array
Access
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

grist-orgs-api-openapi.yml Raw ↑

Other APIs Grist publishes across the network.

Grist attachments API
Grist columns API
Grist data API
Grist docs API
Grist forms API
Grist profile API
Grist records API
Grist service accounts API
Grist session API
Grist sql API
Grist tables API
Grist templates API
Where this information came from

This is an independent, third-party profile of Grist orgs API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.