BYBE API
The BYBE Retail API, version 1. A REST/JSON API over BYBE's records of manufacturers, rebate offers and products, plus the write surface that clips offers for consumers, validates redemptions against purchases, and disburses consumer payouts. 16 operations across 7 tags, authenticated with HTTP Basic (API key as username, API secret as password). US only - the state filter on offers and stores is how BYBE's state-by-state alcohol compliance boundary is expressed in the contract.
BYBE API is published by BYBE on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Rebates, Promotions, Offers, Redemptions, and Disbursements. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.
This API exposes 16 operations across 14 paths, organized into 7 resource areas, and defines 1 schema. It is described by OpenAPI 3.0.1, at version v1.
Requests are made against the base URL https://api.bybe.io.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
BYBE API declares
1 security scheme
for authenticating requests.
It accepts HTTP basic authentication (basic_auth).
basic_auth— Use your API key (token) and your API secret for username and password respectively. You can get these credentials, or generate new ones, on your developer pag…
Paths & Operations 16
Across 14 paths, the API surfaces 16 operations — 13 GET, 3 POST. They span 7 resource areas: Clips, Consumers, Manufacturers, Offers, Products, Redemptions, Stores. Each is listed below with its method, path, parameters, and response codes.
A clip represents a consumer's intent to redeem an offer.
A consumer purchases products and clips/redeems offers.
A manufacturer represents a company or organization that produces alcoholic beverages.
An offer is created and funded by a manufacturer (brand).
A product is produced by a manufacturer and is featured in offers.
Redemptions are created to disburse money to a consumer for their specific purchases.
A store represents a specific retail location of a retailer.
Schemas 1
The contract defines 1 schema that model the data the API accepts and returns. Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
This is an independent, third-party profile of BYBE 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.