For your AI assistant

bipbip-context — llm

bipbip context --for llm

Build with AI

Paste the full BipBip Merchant API context into your AI assistant — Claude, Cursor, or Copilot — so it integrates faster and stops hallucinating endpoints. Everything follows the llms.txt convention, an open standard that packages docs as plain text ready for an LLM.

curl -s https://developer-portal.bipbip.dev/llms-full.txt

Two files that cover the whole integration in one shot. The curated index to browse, or the full bundle to paste straight into a prompt.

# first lines of the output

# BipBip Merchant API

> Integration API for merchants: an inbound REST API to manage orders and
> outbound HMAC-signed webhooks that deliver order and menu events to your POS.

Base URLs: https://merchant-api.bipbip.hn (production)
Payload schema version: 1.0
Open

curl -s https://developer-portal.bipbip.dev/llms.txt

The llms.txt index: a curated list of every topic with links to each file. Ideal as an entry point.

Open

ls llms/

# pick a file or copy its link

  • quickstart.txt

    Quickstart — Overview of both API surfaces, base URLs, required REST headers, and the end-to-end happy path.

    Open

  • rest-api.txt

    REST API — Inbound REST endpoints (Orders + menu), idempotency, rate limits, and the RFC 7807 error envelope.

    Open

  • webhooks.txt

    Webhooks — Transport contract, HMAC verification, signed headers, auth strategies, retries, and every event type.

    Open

  • schemas.txt

    Schemas — Field-by-field JSON payload schemas for orders, status updates, and menu-change results.

    Open

  • changelog.txt

    Changelog — Dated contract changes classified as breaking, behavior, or additive, each with the action it requires. Read this before assuming a field, status, or filter still behaves the way an older integration expects.

    Open

cat prompts/*

Copy one of these prompts, replace the context placeholder with the matching file, and hand it to your assistant.

Webhook receiver with HMAC verification

Here is the BipBip Merchant API context: <paste llms-full.txt here>. Write a Node.js webhook receiver with Express that captures the raw body, verifies the HMAC-SHA256 signature from the X-Bipbip-Signature-256 header in constant time, and handles the order.created event by responding 200 with the remoteOrderId.

REST client to accept orders

Using this BipBip REST API context: <paste rest-api.txt here>. Generate a Python function that accepts an order by calling POST /api/v1/Orders/{orderKey}/accept with the X-Bipbip-Api-Key and Idempotency-Key headers, retrying with exponential backoff on a 429.

Types from the schemas

With these BipBip payload schemas: <paste schemas.txt here>. Generate TypeScript interfaces for the order.created payload and the OrderUpdateEvent envelope, marking optional fields correctly.