3vjia Technology · OAuth Scopes

3vjia Technology OAuth Scopes

OAuth 2.0 derived

3vjia Technology uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

Tokens are issued from https://graph.3vjia.com/oauth/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

Company3D DesignHome FurnishingsInterior DesignManufacturingCustom FurnitureCADRenderingArtificial IntelligenceSoftware-as-a-ServiceChinaOpen Platform

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://graph.3vjia.com/oauth/token

Flows
clientCredentials

Scopes (0)

3vjia Technology implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

The OAuth 2.0 client_credentials grant on graph.3vjia.com defines NO scopes — the token carries the whole contracted surface and authorisation is enforced by what the enterprise's contract enables, not by scope. No type: OAuthScopes pointer is emitted in apis.yml, because there is no scope surface to point at; authentication/3vjia-technology-authentication.yml carries the auth model. This file records the verified zero.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-05'
method: derived
source: openapi/3vjia-technology-open-platform-openapi.yml
schemes:
- name: oauth2ClientCredentials
  source: openapi/3vjia-technology-open-platform-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://graph.3vjia.com/oauth/token
  description: OAuth 2.0 client credentials. appId/appKey are issued after developer + application
    approval at https://dev.3vjia.com/manage/my-app/developer. Token TTL 7200s; re-requesting
    invalidates the previous token.
scopes: []
scope_count: 0
apis_yml_pointer: none
note: >-
  The OAuth 2.0 client_credentials grant on graph.3vjia.com defines NO scopes — the token carries the
  whole contracted surface and authorisation is enforced by what the enterprise's contract enables, not
  by scope. No type: OAuthScopes pointer is emitted in apis.yml, because there is no scope surface to
  point at; authentication/3vjia-technology-authentication.yml carries the auth model. This file records
  the verified zero.

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/3vjia-technology-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.