Edge Impulse · OAuth Scopes

Edge Impulse OAuth Scopes

OAuth 2.0 searched

Edge Impulse 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.

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.

Artificial IntelligenceMachine LearningEmbedded Machine LearningEdge AIMLOpsComputer VisionInternet of ThingsModel DeploymentDeveloper Tools
Scopes: 0 Flows: Method: searched

Scopes (0)

Edge Impulse 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.

📄 Provider scope reference: https://docs.edgeimpulse.com/apis/studio#api-authentication-types

Source

OAuth Scopes

Raw ↑ 
generated: '2026-09-06'
method: searched
source: https://studio.edgeimpulse.com/openapi.yml (components.securitySchemes.OAuth2)
docs: https://docs.edgeimpulse.com/apis/studio#api-authentication-types
provider: Edge Impulse
providerId: edge-impulse
description: 'OAuth 2.0 scopes declared by the Edge Impulse Studio API. There are exactly three, and all
  three are OIDC identity scopes — openid, email, profile. Edge Impulse declares NO resource or permission
  scopes: nothing in the scope set distinguishes reading a project from deleting one, or a dataset from
  an organization. Authorization is carried entirely by the credential type instead (project API key vs
  user JWT) and by per-operation checks, which is why the OAuth surface cannot be used to hand an agent
  a least-privilege token.'
authorization_url: https://studio.edgeimpulse.com/v1/oauth/authorize
token_url: https://studio.edgeimpulse.com/v1/oauth/token
flows:
- authorizationCode
- implicit
- password
- clientCredentials
scope_count: 3
scopes:
- name: openid
  description: Access to basic profile information.
  category: identity
- name: email
  description: Access to email address.
  category: identity
- name: profile
  description: Access to full profile information.
  category: identity
resource_scopes: []
findings:
- All four OAuth flows advertise the same three scopes — including implicit and password, which are discouraged
  by OAuth 2.1.
- The authorizationUrl and tokenUrl are declared as relative paths (/v1/oauth/authorize, /v1/oauth/token)
  in the spec; resolved against the declared server they are https://studio.edgeimpulse.com/v1/oauth/*.
- No /.well-known/openid-configuration or /.well-known/oauth-authorization-server document is served on
  any Edge Impulse host (probed 2026-09-06, all 404), so an OAuth client cannot discover these endpoints
  automatically.
- The OAuth2 scheme is absent from the specs harvested into this repo and present in the live published
  spec, so it is a recent addition.
related:
  authentication: authentication/edge-impulse-authentication.yml
  well_known: well-known/edge-impulse-well-known.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

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/edge-impulse-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.