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

Zype Content Rule Profiles API

Content rule profiles plus the country/state/city lookups they are built from — geo-blocking and availability windows. 7 operations.

Zype Content Rule Profiles API is one of 15 APIs that Zype publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Content Rules, Geo, and Rights Management. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 4 paths. It is described by OpenAPI 3.0.1, at version 1.0.0.

Requests are made against a single base URL, https://api.zype.com/.

7 operations 4 paths 0 schemas 1 DELETE4 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0.0
Base URL
https://api.zype.com/
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Zype Content Rule Profiles API declares 2 security schemes for authenticating requests. An API key is passed in the query as api_key (api_key). It accepts HTTP bearer tokens (OAuth access token) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — OAuth access token of the consumer

Paths & Operations 7

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

Content Rule Profiles 7
GET
/v3/content_rule_profiles
List Content Rule Profiles
listContentRuleProfiles → 200403
POST
/v3/content_rule_profiles
Create Content Rule Profile
createContentRuleProfile body → 201422
GET
/v3/content_rule_profiles/cities_for_state
List Cities For State
listCitiesForState 1 param → 200403
GET
/v3/content_rule_profiles/states_for_country
List States For Country
listStatesForCountry 1 param → 200403
GET
/v3/content_rule_profiles/{id}
View Content Rule Profile
getContentRuleProfile 1 param → 200404
PUT
/v3/content_rule_profiles/{id}
Update Content Rule Profile
updateContentRuleProfile 1 param body → 200404422
DELETE
/v3/content_rule_profiles/{id}
Delete Content Rule Profile
deleteContentRuleProfile 1 param → 204404422

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

zype-content-rules.json Raw ↑

Other APIs Zype publishes across the network.

Zype Platform API
Zype Playout Scheduler API
Zype Monetization API
Zype Consumers API
Zype Live API (V3)
Zype Zobjects API
Zype Analytics API (V3)
Zype Analytics API (V2)
Zype Custom Regions API
Zype Content Rule Groups API
Zype TVE API
Zype Consumer Authentication API
Where this information came from

This is an independent, third-party profile of Zype Content Rule Profiles 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.