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 Audiences API

The Audiences API from Typeface — 3 operation(s) for audiences.

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

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

This API exposes 5 operations across 3 paths, and defines 15 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.

5 operations 3 paths 15 schemas 1 DELETE2 GET1 POST1 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 Audiences API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

Paths & Operations 5

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

Audiences 5
GET
/workspace-resolver-service/accounts/{accountId}/libraries/sub-types/AUDIENCE_LIBRARY
List Audience Catlogs
queryAudienceCatalogsInAccount 1 param → 200
GET
/profile-service/accounts/{accountId}/audience-catalogs/{audienceCatalogId}/audience-segments
List Audiences
queryAudiencesInAccount 2 params → 200
POST
/profile-service/accounts/{accountId}/audience-catalogs/{audienceCatalogId}/audience-segments
Create Audience
createAudienceInAccount 2 params body → 201
PUT
/profile-service/accounts/{accountId}/audience-catalogs/{audienceCatalogId}/audience-segments/{audienceId}
Manage Audience
manageAudienceInAccount 3 params body → 200
DELETE
/profile-service/accounts/{accountId}/audience-catalogs/{audienceCatalogId}/audience-segments/{audienceId}
Delete Audience
deleteAudienceInAccount 3 params → 204

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are AudienceSegment (13 properties), Image (11 properties), LibraryDetails (9 properties), AudienceSegmentProperties (6 properties). Each schema is shown below with its type and property counts.

CreateAudienceResponseBody
object
1 property 1 required
LibraryProperties
object
5 properties
EntityId
object
1 property
QueryAudienceResponseBody
object
1 property
BlobId
object
1 property
CreateAudienceRequestBody
object
6 properties
UpdateAudienceRequestBody
object
6 properties
ImageProperties
object
1 property
Image
object
11 properties
LibraryDetails
object
9 properties
AudienceSegment
object
13 properties
UpdateAudienceResponseBody
object
1 property
WorkspaceId
object
1 property
AudienceSegmentProperties
object
6 properties
GetLibrariesResponseBody
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

typeface-audiences-api-openapi.yml Raw ↑

Other APIs Typeface publishes across the network.

Typeface Authentication API
Typeface Basic Services API
Typeface Brand Kits API
Typeface Content Generation API
Typeface Content Service API
Typeface Digital Assets 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 Audiences 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.