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

Emotive Brands API

The Brands API from Emotive — 9 operation(s) for brands.

Emotive Brands API is one of 36 APIs that Emotive publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Brands. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and a getting-started guide.

This API exposes 17 operations across 9 paths, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against a single base URL, https://api-gw.emotiveapp.co/auth.

17 operations 9 paths 16 schemas 3 DELETE8 GET1 PATCH3 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.emotiveapp.co
Authentication
API Key
License
Private
Resource Areas
1

Authentication & Security 1

Emotive Brands API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-Key (ApiKeyAuth).

Paths & Operations 17

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

Brands 17
GET
/v1/brands
Returns paginated list of Brand names and ids.
controllers.resource.list_brands 3 params → 200401
GET
/v1/brands/{brand_id}/invitations
Returns a list of invitations for a brand.
controllers.resource.list_brand_invitations 1 param → 200401404
POST
/v1/brands/{brand_id}/invitations
Create an invitation for a brand.
controllers.resource.create_brand_invitation 1 param body → 201401404
DELETE
/v1/brands/{brand_id}/invitations/{invitation_id}
Delete an invitation for a brand.
controllers.resource.delete_brand_invitation 2 params → 204401404
GET
/v1/brands/{brand_id}/invitations/{invitation_id}
Returns an invitation for a brand.
controllers.resource.get_brand_invitation 2 params → 200401404
GET
/v1/brands/{brand_id}/products
Returns a list of products for a brand.
controllers.brands.list_brand_products 1 param → 200401404
PUT
/v1/brands/{brand_id}/products
Update products for a brand.
controllers.brands.update_brand_products 1 param body → 200401
GET
/v1/brands/{brand_id}/users
Returns paginated list of users
controllers.users.list_users 3 params → 200401404
GET
/v1/brands/{brand_id}/users/{user_id}/roles
Returns paginated list of roles for a user in a brand.
controllers.resource.list_roles 2 params → 200401403404
POST
/v1/brands/{brand_id}/users/{user_id}/roles
Assign a role to a user in a brand.
controllers.resource.assign_role 2 params body → 201400401403404409
PUT
/v1/brands/{brand_id}/users/{user_id}/roles
Update a role for a user in a brand.
controllers.resource.update_user_roles 2 params body → 200401403
DELETE
/v1/brands/{brand_id}/users/{user_id}/roles/{role_id}
Delete a role for a user in a brand.
controllers.resource.delete_role 3 params → 204401403404
GET
/v2/brands
Get all Brands.
controllers.brands.list_brands 3 params → 200401
POST
/v2/brands
Create a new Brand.
controllers.brands.create_brand body → 201400401
DELETE
/v2/brands/{brand_id}
Delete a Brand.
controllers.brands.delete_brand 1 param → 204401404
GET
/v2/brands/{brand_id}
Get Brand information for an id.
controllers.brands.get_brand 1 param → 200401404
PATCH
/v2/brands/{brand_id}
Update Brand.
controllers.brands.update_brand 1 param body → 200401404

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are UserSchema (9 properties), InvitationSchema (7 properties), ProductSchema (4 properties), CreateBrandSchema (3 properties). Each schema is shown below with its type and property counts.

InvitationListSchema
object
1 property
BrandSchema
object
3 properties
UserListSchema
object
2 properties
InvitationSchema
object
7 properties
ProductListSchema
object
1 property
UserAccessRoles
array
CreateBrandSchema
object
3 properties
JsonResponse
object
1 property
GroupAccessRoles
array
BrandAPIResponse
object
2 properties
ProductSchema
object
4 properties
BrandProducts
object
3 properties
BrandListSchema
object
2 properties
RoleSchema
object
3 properties
UserSchema
object
9 properties
UserAccessSchema
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

emotive-brands-api-openapi.yml Raw ↑

Other APIs Emotive publishes across the network.

Emotive Knowledge Base MCP Server
Emotive Admin API
Emotive Auth0 API
Emotive Authentication Source API
Emotive Brand API
Emotive Bulk Subscriber API
Emotive Connections API
Emotive Custom Events API
Emotive Experience API
Emotive Google API
Emotive Impersonate API
Emotive JWT API
Where this information came from

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