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

Edge Impulse ThirdPartyAuth API

The ThirdPartyAuth API from Edge Impulse — 4 operation(s) for thirdpartyauth.

Edge Impulse ThirdPartyAuth API is one of 36 APIs that Edge Impulse publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against a single base URL, https://studio.edgeimpulse.com/v1.

7 operations 4 paths 10 schemas 1 DELETE2 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://studio.edgeimpulse.com/v1
Authentication
API Key, API Key, API Key
Resource Areas
1

Authentication & Security 3

Edge Impulse ThirdPartyAuth API declares 3 security schemes for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuthentication). An API key is passed in the cookie as jwt (JWTAuthentication). An API key is passed in the header as x-jwt-token (JWTHttpHeaderAuthentication). By default, every request must be authenticated.

Paths & Operations 7

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

ThirdPartyAuth 7
GET
/api/third-party-auth
Get all third party auth
getAllThirdPartyAuth → 200
POST
/api/third-party-auth
Create third party auth
createThirdPartyAuth body → 200
GET
/api/third-party-auth/{authId}
Get third party auth
getThirdPartyAuth 1 param → 200
POST
/api/third-party-auth/{authId}
Update third party auth
updateThirdPartyAuth 1 param body → 200
DELETE
/api/third-party-auth/{authId}
Delete third party auth
deleteThirdPartyAuth 1 param → 200
POST
/api/{projectId}/third-party-auth/{authId}/authorize
Give access to project
authorizeThirdParty 2 params body → 302
POST
/api/third-party-auth/{authId}/login
Create or login a user
createUserThirdParty 1 param body → 200

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are ThirdPartyAuth (6 properties), CreateThirdPartyAuthRequest (6 properties), CreateUserThirdPartyRequest (5 properties), UpdateThirdPartyAuthRequest (4 properties). Each schema is shown below with its type and property counts.

GenericApiResponse
object
2 properties 1 required
CreateThirdPartyAuthResponse
UpdateThirdPartyAuthRequest
object
4 properties
ThirdPartyAuth
object
6 properties 6 required
GetThirdPartyAuthResponse
CreateThirdPartyAuthRequest
object
6 properties 4 required
CreateUserThirdPartyResponse
AuthorizeThirdPartyRequest
object
1 property 1 required
CreateUserThirdPartyRequest
object
5 properties 4 required
GetAllThirdPartyAuthResponse

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

edge-impulse-thirdpartyauth-api-openapi.yml Raw ↑

Other APIs Edge Impulse publishes across the network.

Edge Impulse Admin API
Edge Impulse Auth API
Edge Impulse Canary API
Edge Impulse CDN API
Edge Impulse Classify API
Edge Impulse Deployment API
Edge Impulse Devices API
Edge Impulse DSP API
Edge Impulse EmailVerification API
Edge Impulse Export API
Edge Impulse FeatureFlags API
Edge Impulse Health API
Where this information came from

This is an independent, third-party profile of Edge Impulse ThirdPartyAuth 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.