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

Otreeba Ocpc API

The Ocpc API from Otreeba — 6 operation(s) for ocpc.

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

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

This API exposes 6 operations across 6 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

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

6 operations 6 paths 6 schemas 6 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.otreeba.com/v1
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Otreeba Ocpc API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-Key (api_key). By default, every request must be authenticated.

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 6 GET. Each is listed below with its method, path, parameters, and response codes.

Ocpc 6
GET
/seed-companies/{ocpc}
Find seed company by Open Cannabis Product Code (OCPC).
getSeedCompanyByOcpc 1 param → 200400401404
GET
/seed-companies/{ocpc}/strains
Find strains for a seed company by Open Cannabis Product Code (OCPC).
getSeedCompanyStrainsByOcpc 3 params → 200400401404
GET
/edibles/{ocpc}
Find edible by Open Cannabis Product Code (OCPC).
getEdibleByOcpc 1 param → 200400401404
GET
/extracts/{ocpc}
Find extract by Open Cannabis Product Code (OCPC).
getExtractByOcpc 1 param → 200400401404
GET
/flowers/{ocpc}
Find flower by Open Cannabis Product Code (OCPC).
getFlowerByOcpc 1 param → 200400401404
GET
/strains/{ocpc}
Find strain by Open Cannabis Product Code (OCPC).
getStrainByOcpc 1 param → 200400401404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Edible (16 properties), Extract (14 properties), Flower (14 properties), Strain (11 properties). Each schema is shown below with its type and property counts.

Strain
object
11 properties 1 required
Pagination
object
6 properties
Edible
object
16 properties 1 required
Flower
object
14 properties 1 required
SeedCompany
object
10 properties 1 required
Extract
object
14 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

otreeba-ocpc-api-openapi.yml Raw ↑

Other APIs Otreeba publishes across the network.

Otreeba Brands API
Otreeba Condition API
Otreeba Conditions API
Otreeba Edibles API
Otreeba Extracts API
Otreeba Flowers API
Otreeba Identifiers API
Otreeba Products API
Otreeba Seed API
Otreeba Seed Companies API
Otreeba Slug API
Otreeba Strains API
Where this information came from

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