curl --request GET \
--url https://davinci-app.com/api/v2/projects/{projectId} \
--header 'Authorization: Bearer <token>'import os
from davinci_sdk import DavinciClient
with DavinciClient(api_key=os.environ["DAVINCI_API_KEY"]) as client:
result = client.projects.get(project_id)
print(result.metadata.name, result.metadata.visibility)
import { DavinciClient } from '@celedon/davinci-sdk';
const client = new DavinciClient({
apiKey: process.env.DAVINCI_API_KEY!,
});
const { metadata } = await client.projects.get(projectId);
console.log(metadata.name, metadata.visibility);
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://davinci-app.com/api/v2/projects/{projectId}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"metadata": {
"id": "<string>",
"name": "<string>",
"slug": "<string>",
"description": "<string>",
"owner": "<string>",
"createdBy": "<string>",
"visibility": "<string>",
"version": "<string>",
"created": "2023-11-07T05:31:56Z",
"lastModified": "2023-11-07T05:31:56Z",
"storageUsedBytes": 1,
"transferState": "<string>",
"collaborators": [
"<string>"
],
"pendingCollaborators": [
"<string>"
]
}
}{
"success": false,
"error": {
"code": "<string>",
"message": "<string>",
"details": {}
}
}{
"success": false,
"error": {
"code": "<string>",
"message": "<string>",
"details": {}
}
}{
"success": false,
"error": {
"code": "<string>",
"message": "<string>",
"details": {}
}
}{
"success": false,
"error": {
"code": "<string>",
"message": "<string>",
"details": {}
}
}{
"success": false,
"error": {
"code": "<string>",
"message": "<string>",
"details": {}
}
}Get project metadata
Returns the project’s stored metadata, including its owner, visibility, version, storage footprint, and effective collaborators.
Use the permissions endpoint when you need to know what this credential may do with the project; those are reported separately because they are derived per credential rather than stored on the project.
curl --request GET \
--url https://davinci-app.com/api/v2/projects/{projectId} \
--header 'Authorization: Bearer <token>'import os
from davinci_sdk import DavinciClient
with DavinciClient(api_key=os.environ["DAVINCI_API_KEY"]) as client:
result = client.projects.get(project_id)
print(result.metadata.name, result.metadata.visibility)
import { DavinciClient } from '@celedon/davinci-sdk';
const client = new DavinciClient({
apiKey: process.env.DAVINCI_API_KEY!,
});
const { metadata } = await client.projects.get(projectId);
console.log(metadata.name, metadata.visibility);
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://davinci-app.com/api/v2/projects/{projectId}', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"metadata": {
"id": "<string>",
"name": "<string>",
"slug": "<string>",
"description": "<string>",
"owner": "<string>",
"createdBy": "<string>",
"visibility": "<string>",
"version": "<string>",
"created": "2023-11-07T05:31:56Z",
"lastModified": "2023-11-07T05:31:56Z",
"storageUsedBytes": 1,
"transferState": "<string>",
"collaborators": [
"<string>"
],
"pendingCollaborators": [
"<string>"
]
}
}{
"success": false,
"error": {
"code": "<string>",
"message": "<string>",
"details": {}
}
}{
"success": false,
"error": {
"code": "<string>",
"message": "<string>",
"details": {}
}
}{
"success": false,
"error": {
"code": "<string>",
"message": "<string>",
"details": {}
}
}{
"success": false,
"error": {
"code": "<string>",
"message": "<string>",
"details": {}
}
}{
"success": false,
"error": {
"code": "<string>",
"message": "<string>",
"details": {}
}
}Authorizations
Personal access token. The scopes granted at issuance determine both which
operations the key may call and the ceiling on the resource permissions it
can exercise. Each scope family is a ladder: projects:manage implies
projects:write and projects:read; cards:manage implies cards:write
and cards:read; and teams:manage implies teams:write and teams:read.
These are named API capability bundles, not blanket domain roles:
manage exposes only the permissions enumerated for that scope and never
bypasses the acting user's current role-based access.
Path Parameters
Project id. May be compound in the form {projectId}--{branchName}.
1Response
Project metadata.
Stored project metadata. ProjectSummary is this plus the live inUse
and activeBranch fields that only the list endpoint computes.
Hide child attributes
Hide child attributes
User id or organization id that owns the project.
x >= 0User ids with effective access, including access inherited from an organization.