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

Trend Creator API

The Creator API from Trend — 22 operation(s) for creator.

Trend Creator API is one of 20 APIs that Trend publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Creator. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, authentication docs, and rate-limit docs.

This API exposes 23 operations across 22 paths, and defines 20 schemas. It is described by OpenAPI 3.2.0, at version 1.28.31.

Requests are made against a single base URL, https://api.trend.io.

23 operations 22 paths 20 schemas 2 DELETE13 GET5 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.28.31
Base URL
https://api.trend.io
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Trend Creator API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (access-token). An API key is passed in the header as trend-api-key (admin-api-key). By default, every request must be authenticated.

Paths & Operations 23

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

Creator 23
GET
/creator/profile
ProfileController_findOnePersonalProfile → 200
GET
/creator/profile/settings
ProfileController_findPersonalProfileSettings → 200
GET
/creator/profile/public/{id}
ProfileController_findOnePublicProfile 1 param → 200
GET
/creator/profile/iframe/{firebaseUserId}
ProfileController_findOneIframeProfile 1 param → 200
GET
/creator/profile/id-list
ProfileController_getActiveCreatorsList → 200
PATCH
/creator/profile/{creatorId}
ProfileController_updateProfile 1 param body → 200
GET
/creator/portfolio/{username}
PortfolioController_getCreatorPortfolio 1 param → 200
POST
/creator/portfolio/add
PortfolioController_create body → 201
DELETE
/creator/portfolio/remove
PortfolioController_remove body → 200
DELETE
/creator/portfolio/influencer/remove/{userId}
PortfolioController_removeInfluencerPortfolioItem 1 param body → 200
GET
/creator/level
CreatorLevelController_getLevel → 200
GET
/creator/level/bonus-table
CreatorLevelController_getBonusLevels → 200
GET
/creator
CreatorController_findAll 38 params → 200
GET
/creator/findByUserEmail
CreatorController_findByUserEmail 1 param → 200
GET
/creator/demographic-data
CreatorController_getCreatorDemographicData → 200
GET
/creator/admin/level/{creatorId}
CreatorController_getAdminLevel 1 param → 200
GET
/creator/{id}
CreatorController_findOne 1 param → 200
PATCH
/creator/{id}
CreatorController_update 1 param body → 200
PATCH
/creator/admin/approve
CreatorController_approveCreator body → 200
PATCH
/creator/admin/reject
CreatorController_rejectCreator → 200
PATCH
/creator/influencer/{uid}
CreatorController_updateCreatorByInfluencerUid 1 param body → 200
POST
/creator/registration
CreatorController_postRegistration body → 201
POST
/creator/hubspot/identification
CreatorController_createIdentification → 201

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are UpdateCreatorDto (27 properties), CreatorUserDto (24 properties), Creator (23 properties), PublicProfileResponse (23 properties). Each schema is shown below with its type and property counts.

UpdateProfileDto
object
15 properties
Creator
object
23 properties 15 required
JobTypeDto
object
2 properties 2 required
User
object
12 properties 12 required
SocialProviderDto
object
4 properties 4 required
PublicProfileResponse
object
23 properties 17 required
UpdateCreatorDto
object
27 properties
ProfileDto
object
18 properties 14 required
AddressDto
object
6 properties 6 required
FindAllResponse
object
8 properties 3 required
UserIdEmailDto
object
2 properties 2 required
Address
object
6 properties 6 required
ApproveCreatorDto
object
2 properties 2 required
PortfolioDto
object
2 properties 2 required
UpdateAddressDto
object
6 properties
UserCreatorDto
object
13 properties 13 required
UpdateCreatorResponse
object
1 property 1 required
CreatorRegistrationDto
object
14 properties 13 required
SettingsDto
object
18 properties 14 required
CreatorUserDto
object
24 properties 16 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

trend-creator-api-openapi.yml Raw ↑

Other APIs Trend publishes across the network.

Trend AI API
Trend Auth API
Trend Basic Authentication (AI) API
Trend Brand Admin API
Trend Brand API
Trend Brand Authentication API
Trend Campaign API
Trend Content API
Trend Creator Authentication API
Trend Creator Portfolio API
Trend Creator Profiles API
Trend Health Check API
Where this information came from

This is an independent, third-party profile of Trend Creator 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.