3vjia Technology OAuth Scopes
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.
OAuth endpoints
https://graph.3vjia.com/oauth/token
clientCredentials
Scopes (0)
The OAuth2 security scheme(s) in the OpenAPI declare no scopes, and no security requirement references one.
Source
OAuth Scopes
generated: '2026-10-14'
method: none
source: openapi/3vjia-technology-3d-show-api-openapi.yml, openapi/3vjia-technology-3vjia-ai-api-openapi.yml,
openapi/3vjia-technology-accounts-api-openapi.yml, openapi/3vjia-technology-aimes-api-openapi.yml,
openapi/3vjia-technology-asset-management-api-openapi.yml, openapi/3vjia-technology-authorization-api-openapi.yml,
openapi/3vjia-technology-cad-api-openapi.yml, openapi/3vjia-technology-chuangdian-api-openapi.yml,
openapi/3vjia-technology-common-services-api-openapi.yml, openapi/3vjia-technology-dedicated-services-api-openapi.yml,
openapi/3vjia-technology-design-schemes-api-openapi.yml, openapi/3vjia-technology-dms-api-openapi.yml,
openapi/3vjia-technology-dreamer-api-openapi.yml, openapi/3vjia-technology-floor-plans-api-openapi.yml,
openapi/3vjia-technology-light-design-api-openapi.yml, openapi/3vjia-technology-mos-api-openapi.yml,
openapi/3vjia-technology-products-api-openapi.yml, openapi/3vjia-technology-quotation-api-openapi.yml,
openapi/3vjia-technology-xuanchi-ai-api-openapi.yml
schemes:
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-3d-show-api-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.
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-3vjia-ai-api-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.
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-accounts-api-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.
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-aimes-api-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.
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-asset-management-api-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.
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-authorization-api-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.
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-cad-api-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.
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-chuangdian-api-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.
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-common-services-api-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.
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-dedicated-services-api-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.
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-design-schemes-api-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.
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-dms-api-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.
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-dreamer-api-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.
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-floor-plans-api-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.
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-light-design-api-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.
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-mos-api-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.
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-products-api-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.
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-quotation-api-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.
- name: oauth2ClientCredentials
source: openapi/3vjia-technology-xuanchi-ai-api-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: []
note: The OAuth2 security scheme(s) in the OpenAPI declare no scopes, and no security requirement
references one.
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/scopes/3vjia-technology-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.
A second provider on the same verified email joins the account you already have.