Developer Reference

Blacamp Card Developer Documentation

Name: Blacamp Card Digital Pass
Brand: BLACAMP
Availability: InStock

Complete reference for integrating Blacamp Card: REST API v1, verification schemas, RateLimit headers, RFC 9457 error models, Model Context Protocol (MCP) server, and the official CLI.

1. Integration Surfaces

Blacamp Card provides multiple read-only, high-performance integration interfaces for partners, developers, and autonomous AI agents:

REST API v1

Versioned verification, perk catalog, and location search at /api/v1/.

MCP Server

Streamable HTTP MCP tools for Claude, ChatGPT, and AI agents at /mcp.

Official CLI

Terminal utility: npx @blacamp/card-cli verify <id>.

2. API Versioning & Deprecation Policy

All production REST operations follow strict URL path versioning (/api/v1/).

Backwards Compatibility: Additive changes (new optional properties, new fields) are introduced within the current major version (v1) without breaking existing consumers.
Deprecation Signaling: When an endpoint is slated for retirement, responses include standard RFC 9745 Deprecation: true and Sunset: <date> headers with a minimum 180-day grace window.
Machine Discovery: The API is cataloged via RFC 9727 at /.well-known/api-catalog and the OpenAPI 3.1 description is published at /openapi.json.

3. Rate Limit Headers

To allow AI agents and automation scripts to self-throttle in real time, all API responses return standard IETF RateLimit structured fields:

RateLimit-Limit: 120

RateLimit-Remaining: 118

RateLimit-Reset: 52

RateLimit-Policy: 120;w=60

Retry-After: 60 (only returned on HTTP 429)

4. RFC 9457 Typed Error Model

All error responses use the standard application/problem+json media type with machine-readable error codes and human-readable resolution hints:

{
  "type": "https://blacampcard.com/docs#card-not-found",
  "title": "Pass Not Found",
  "status": 404,
  "detail": "No active Blacamp Card found matching ID BC-8492-2026.",
  "code": "card_not_found",
  "resolution": "Verify the 8-digit Member ID or request a fresh QR scan from the cardholder.",
  "instance": "/api/v1/card/verify?id=BC-8492-2026"
}

5. Card Verification API

Campsites, surf schools, and outdoor partners can verify cardholder status in real time:

GET /api/v1/card/verify?id=BC-8492-2026 HTTP/1.1
Host: blacampcard.com
Accept: application/json

Sample 200 OK Response:

{
  "valid": true,
  "card_id": "BC-8492-2026",
  "member_status": "active",
  "valid_from": "2026-01-01",
  "valid_until": "2026-12-31",
  "tier": "European Explorer",
  "perks": {
    "campings_discount_percent": 25,
    "surf_discount_percent": 15,
    "van_rental_discount_percent": 10,
    "valid_all_seasons": true
  }
}

6. Model Context Protocol (MCP) Server

Blacamp Card exposes an official MCP server enabling AI agents (such as Claude, ChatGPT, and custom LangChain/AutoGen bots) to query pass privileges, verify QR cards, and compare camping benefits:

Streamable HTTP Endpoint:

https://blacampcard.com/mcp

Exposed Tools:

blacamp_card_verify: Validates a member pass ID or QR signature.
blacamp_card_search_perks: Queries partner discounts by country or activity (camping, surf, campervan).
blacamp_card_compare: Returns programmatic comparison data against ACSI and CKE.

Discover manifests: MCP Server Card • AI Catalog • Agent Skills Index.

7. Official CLI Utility

Verify passes and query perks directly from your terminal:

# Verify a member card
npx @blacamp/card-cli verify BC-8492-2026

# Output JSON for agents and automated scripts
npx @blacamp/card-cli verify BC-8492-2026 --json

# Query perks by country
npx @blacamp/card-cli perks --country=ES --type=camping