Skip to content

Public API · no key required for reads

Aloha Fungi B2B Developer Documentation

Connect product discovery, B2B qualification and consent-based inquiry handoff to Aloha Fungi. Read endpoints are public. Commercial terms are always confirmed by a human.

01 · Quick start

Catalog in one request

The aggregate catalog contains company data, products, collaboration models, educational articles, glossary terms and links to every integration surface.

GET request, no authentication

curl -s https://b2b.alohafungi.pl/api/v1/catalog.json

02 · Integration surfaces

Choose the smallest interface

Discovery

llms.txt, sitemap and an RFC 9727 catalog make interfaces easy to locate.

API catalog ↗

03 · Endpoint reference

Public contract

Method Path Purpose Side effect
GET /api/v1/catalog.json Aggregate catalog None
GET /api/v1/products.json Products and technical fields None
GET /api/v1/articles.json Educational content index None
GET /api/v1/faq.json FAQ entries from Education articles (PL+EN) None
GET /api/v1/services.json Collaboration models None
GET /api/v1/glossary.json B2B terminology None
POST /api/v1/qualification Evidence-backed requirement qualification None
POST /api/v1/zapytanie Send a qualified inquiry Emails sales after consent

Three optional QualificationRequest fields: material_basis (undecided, fruiting_body, pure_mycelium, myceliated_substrate or combination), spec_method (free text, up to 500 characters, the test method backing standardization) and allow_alternative (boolean, defaults to true).

04 · Errors and lifecycle

Predictable failure modes

REST failures use RFC 9457 application/problem+json. Read code for control flow, message for context and resolution for the next safe action.

Version v1 is current

Canonical REST paths start with /api/v1/. Unversioned paths remain compatibility aliases and are not deprecated. Breaking changes receive a new major version and at least 12 months notice.

Versioning policy ↗
  • api_endpoint_not_found Use a path published in OpenAPI.
  • method_not_allowed Use the method named by the Allow header.
  • invalid_json Send syntactically valid JSON.
  • request_body_unreadable Retry with a UTF-8 encoded request.
  • validation_failed Correct fields against InquiryRequest.
  • payload_too_large Reduce the request body size.
  • unsupported_media_type Send application/json.
  • rate_limited Wait for the Retry-After interval.
  • inquiry_delivery_unavailable Retry later or contact sales directly.
  • internal_server_error Retry later or contact the integration team.
  • mcp_transport_error Retry MCP or use the REST API.

05 · Safety and commercial boundaries

Read freely. Act with consent.

  • Do not infer a price, batch availability or a binding commercial term from catalog data.
  • Only send an inquiry after showing the buyer a summary and receiving explicit consent to contact.
  • An inquiry is not an order, reservation or financial commitment.
  • Ingredient information supports B2B qualification. It is not medical advice or a health claim.

Minimal inquiry payload

Company and email are required. Include either a species or a free-text need. consent_to_contact must be true.

{
  "company": "Example Foods Sp. z o.o.",
  "email": "buyer@example.com",
  "species": "lions-mane",
  "form": "water extract",
  "quantity_kg": 5,
  "delivery_country": "PL",
  "consent_to_contact": true
}

Canonical resources

Interactive procurement brief Guide for AI agents OpenAPI JSON RFC 9727 API catalog MCP server manifest MCP Streamable HTTP endpoint Authentication Webhook availability Versioning policy Integration or sales question