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

Typeface Digital Assets API

The Digital Assets API from Typeface — 7 operation(s) for digital assets.

Typeface Digital Assets API is one of 15 APIs that Typeface publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 15 operations across 7 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version v0.

Requests are made against a single base URL, https://api-us.typeface.ai.

15 operations 7 paths 14 schemas 2 DELETE6 GET2 PATCH3 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v0
Base URL
https://api-us.typeface.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Typeface Digital Assets API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

Paths & Operations 15

Across 7 paths, the API surfaces 15 operations — 2 DELETE, 6 GET, 2 PATCH, 3 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Digital Assets 15
GET
/profile-service/accounts/{accountId}/projects/{projectId}/assets
Project - List Assets
queryAssetsInProject 3 params → 200
POST
/profile-service/accounts/{accountId}/projects/{projectId}/assets
Project - Create Asset
createAssetInProject 2 params body → 200
GET
/profile-service/accounts/{accountId}/projects/{projectId}/assets/{assetId}
Project - Get Asset
getAssetInProject 3 params → 200
PUT
/profile-service/accounts/{accountId}/projects/{projectId}/assets/{assetId}
Project - Update Asset
updateAssetInProject 3 params body → 200
DELETE
/profile-service/accounts/{accountId}/projects/{projectId}/assets/{assetId}
Project - Delete Asset
deleteAssetInProject 3 params → 200
GET
/profile-service/accounts/{accountId}/projects/{projectId}/assets/{assetId}/metadata
Project - Get Metadata
getMetadataOfProjectAssets 3 params → 200
PATCH
/profile-service/accounts/{accountId}/projects/{projectId}/assets/{assetId}/metadata
Project - Patch Metadata
patchMetadataOfProjectAssets 3 params body → 204400
GET
/profile-service/accounts/{accountId}/asset-catalogs/{assetCatalogId}/assets
List Assets
queryAssetsInAssetCatalog 3 params → 200
POST
/profile-service/accounts/{accountId}/asset-catalogs/{assetCatalogId}/assets
Create Asset
createAssetInAssetCatalog 2 params body → 201
DELETE
/profile-service/accounts/{accountId}/asset-catalogs/{assetCatalogId}/assets/{assetId}
Delete Asset
deleteAssetInAssetCatalog 3 params → 204
GET
/profile-service/accounts/{accountId}/asset-catalogs/{assetCatalogId}/assets/{assetId}
Get Asset
getAssetInAssetCatalog 3 params → 200
PUT
/profile-service/accounts/{accountId}/asset-catalogs/{assetCatalogId}/assets/{assetId}
Update Asset
updateAssetInAssetCatalog 3 params body → 200
GET
/profile-service/accounts/{accountId}/asset-catalogs/{assetCatalogId}/assets/{assetId}/metadata
Get Metadata
getMetadata 3 params → 200
PATCH
/profile-service/accounts/{accountId}/asset-catalogs/{assetCatalogId}/assets/{assetId}/metadata
Patch Metadata
patchMetadata 3 params body → 204400
POST
/search-service/accounts/{accountId}/all-assets
Search Assets
searchAssets 1 param body → 200

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are SearchAssetsRequestBody (13 properties), SearchedAsset (13 properties), EntityModelAssetV2 (12 properties), Link (9 properties). Each schema is shown below with its type and property counts.

SearchedAsset
object
13 properties
SearchAssetsRequestBody
object
13 properties
Tag
object
4 properties
EntityModelAssetV2
object
12 properties
AssetV2ContentType
string
Link
object
9 properties
CreateAssetV2RequestBody
object
5 properties
JsonNode
object
SearchAssetsResponseBody
object
2 properties
QueryAssetsV2InAccountResponseBody
object
2 properties
UpdateAssetV2RequestBody
object
4 properties
MetadataPatchRequest
object
1 property 1 required
AssetMetadataResponeBody
object
2 properties
Metadata
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

typeface-digital-assets-api-openapi.yml Raw ↑

Other APIs Typeface publishes across the network.

Typeface Audiences API
Typeface Authentication API
Typeface Basic Services API
Typeface Brand Kits API
Typeface Content Generation API
Typeface Content Service API
Typeface Discovery API
Typeface Feeds API
Typeface Profile Service API
Typeface Projects API
Typeface Provisioning API
Typeface Provisioning Service API
Where this information came from

This is an independent, third-party profile of Typeface Digital Assets 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.