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

Relevance AI Projects API

The projects API from Relevance AI — 30 operation(s) for projects.

Relevance AI Projects API is one of 32 APIs that Relevance AI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Project. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 33 operations across 30 paths, and defines 51 schemas. It is described by OpenAPI 3.2.0, at version latest.

Requests are made against a single base URL, /latest.

33 operations 30 paths 51 schemas 15 GET17 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
latest
Base URL
https://api-{region}.stack.tryrelevance.com/latest
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Relevance AI Projects API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (AuthorizationHeader). By default, every request must be authenticated.

  • AuthorizationHeader — Authorization credentials. Header authorization should be in the form of: project:apikey

Paths & Operations 33

Across 30 paths, the API surfaces 33 operations — 15 GET, 17 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Projects 33
POST
/projects/create
CreateProject
CreateProject body → 200
POST
/projects/update
UpdateProject
UpdateProject body → 200
GET
/projects/list
ListProjects
ListProjects 2 params → 200
GET
/projects/organization_info
GetProjectsOrgInfo
GetProjectsOrgInfo → 200
GET
/projects/keys/list
ListProjectKeys
ListProjectKeys → 200
GET
/projects/keys/availability
ListProjectNativeApiKeysAvailability
ListProjectNativeApiKeysAvailability → 200
GET
/projects/keys/types/list
ListProjectKeyTypes
ListProjectKeyTypes 2 params → 200
POST
/projects/keys/set
SetProjectKey
SetProjectKey body → 200
POST
/projects/keys/delete
DeleteProjectKey
DeleteProjectKey body → 200
POST
/projects/snippets/upsert
UpsertProjectSnippet
UpsertProjectSnippet body → 200
GET
/projects/snippets/list
ListProjectSnippets
ListProjectSnippets 3 params → 200
POST
/projects/snippets/delete
DeleteProjectSnippet
DeleteProjectSnippet body → 200
POST
/projects/{project_id}/delete_job
CreateProjectDeleteJob
CreateProjectDeleteJob 1 param body → 200
GET
/projects/{project_id}/delete_job
GetProjectDeletionMetadata
GetProjectDeletionMetadata 1 param → 200
GET
/projects/delete_job/{project_deletion_job_id}
GetProjectDeleteJob
GetProjectDeleteJob 1 param → 200
GET
/projects/{project_id}/usage-alarms/list
ListProjectUsageAlarms
ListProjectUsageAlarms 1 param → 200
POST
/projects/{project_id}/usage-alarms/upsert
UpsertProjectUsageAlarm
UpsertProjectUsageAlarm 1 param body → 200
POST
/projects/{project_id}/usage-alarms/delete
DeleteProjectUsageAlarm
DeleteProjectUsageAlarm 1 param body → 200
GET
/projects/{project_id}/usage-alarms/is-blocking
GetIsProjectBlockingOnUsageAlarms
GetIsProjectBlockingOnUsageAlarms 1 param → 200
GET
/projects/{project_id}/feature_gates
GetProjectFeatureGates
GetProjectFeatureGates 1 param → 200
GET
/projects/streaming-token
GetProjectStreamingToken
GetProjectStreamingToken → 200
PUT
/projects/{project_id}/settings/{setting_id}
UpdateProjectSetting
UpdateProjectSetting 2 params body → 200
GET
/projects/{project_id}/settings/{setting_id}
GetProjectSetting
GetProjectSetting 2 params → 200
POST
/projects/{project_id}/settings
ListProjectSettings
ListProjectSettings 1 param body → 200
POST
/projects/mcp/upsert
UpsertProjectMCPServer
UpsertProjectMCPServer body → 200
POST
/projects/mcp/list
ListProjectMCPServers
ListProjectMCPServers body → 200
POST
/projects/mcp/delete
DeleteProjectMCPServer
DeleteProjectMCPServer body → 200
POST
/projects/mcp/get
GetProjectMCPServer
GetProjectMCPServer body → 200
GET
/assets/{asset_type}/{asset_id}/access_configuration
GetAssetAccessConfiguration
GetAssetAccessConfiguration 2 params → 200
POST
/assets/{asset_type}/{asset_id}/access_configuration
SetAssetAccessConfiguration
SetAssetAccessConfiguration 2 params body → 200
GET
/job-priorities/list
ListEntityJobPriorities
ListEntityJobPriorities → 200
POST
/job-priorities/set
SetEntityJobPriority
SetEntityJobPriority body → 200
POST
/job-priorities/unset
UnsetEntityJobPriority
UnsetEntityJobPriority body → 200

Schemas 51

The contract defines 51 schemas that model the data the API accepts and returns. The most detailed are CreateProjectDeleteJobOutput (8 properties), ListProjectSettingsOutput (7 properties), UpsertProjectMCPServerOutput (6 properties), GetProjectMCPServerOutput (6 properties). Each schema is shown below with its type and property counts.

UpsertProjectSnippetInput
object
6 properties 3 required
CreateProjectOutput
object
1 property 1 required
ListProjectSettingsInput
object
1 property 1 required
ListProjectKeysOutput
object
1 property 1 required
GetProjectFeatureGatesOutput
object
2 properties 2 required
ListProjectNativeApiKeysAvailabilityOutput
object
1 property 1 required
GetProjectMCPServerOutput
object
6 properties 3 required
DeleteProjectKeyInput
object
1 property 1 required
UnsetEntityJobPriorityOutput
object
1 property 1 required
DeleteProjectUsageAlarmInput
object
2 properties 2 required
UpsertProjectMCPServerOutput
object
6 properties 3 required
GetProjectSettingOutput
GetProjectStreamingTokenOutput
object
1 property 1 required
CreateProjectInput
object
5 properties 1 required
UpsertProjectMCPServerInput
object
5 properties
DeleteProjectSnippetInput
object
1 property 1 required
SetProjectKeyOutput
object
2 properties 2 required
UnsetEntityJobPriorityInput
object
2 properties 2 required
UpsertProjectSnippetOutput
boolean
ListProjectsOutput
object
2 properties 2 required
CreateProjectDeleteJobInput
DeleteProjectMCPServerInput
object
1 property 1 required
DeleteProjectMCPServerOutput
object
1 property 1 required
ListProjectSettingsOutput
object
7 properties
SetAssetAccessConfigurationOutput
object
1 property 1 required
ListProjectKeyTypesOutput
object
1 property 1 required
SetEntityJobPriorityInput
object
3 properties 3 required
UpdateProjectSettingInput
object
1 property 1 required
UpsertProjectUsageAlarmOutput
object
2 properties 2 required
DeleteProjectSnippetOutput
boolean
SetEntityJobPriorityOutput
object
1 property 1 required
SetProjectKeyInput
object
2 properties 2 required
UpdateProjectSettingOutput
ListProjectMCPServersInput
ListEntityJobPrioritiesOutput
object
1 property 1 required
DeleteProjectKeyOutput
object
2 properties 2 required
UpdateProjectInput
object
4 properties
GetIsProjectBlockingOnUsageAlarmsOutput
object
4 properties 4 required
UpdateProjectOutput
object
2 properties 2 required
DeleteProjectUsageAlarmOutput
object
GetProjectDeletionMetadataOutput
object
2 properties 2 required
GetProjectsOrgInfoOutput
object
5 properties 3 required
SetAssetAccessConfigurationInput
CreateProjectDeleteJobOutput
object
8 properties 7 required
GetAssetAccessConfigurationOutput
UpsertProjectUsageAlarmInput
object
4 properties 3 required
ListProjectUsageAlarmsOutput
object
1 property 1 required
GetProjectDeleteJobOutput
object
2 properties 2 required
GetProjectMCPServerInput
object
1 property 1 required
ListProjectSnippetsOutput
array
ListProjectMCPServersOutput
array
List of MCP servers for the project

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

relevance-ai-projects-api-openapi.yml Raw ↑

Other APIs Relevance AI publishes across the network.

Relevance AI MCP Server
Relevance AI Agent Debug Configs API
Relevance AI Agent Runtime Events API
Relevance AI Agents API
Relevance AI Alarms API
Relevance AI Analytics API
Relevance AI Apify API
Relevance AI Auth API
Relevance AI Billing API
Relevance AI Branding Kit API
Relevance AI Branding Kits API
Relevance AI Chat API
Where this information came from

This is an independent, third-party profile of Relevance AI Projects 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.