Fevo website screenshot

Fevo

FEVO is a New York social-commerce and group-ticketing platform, launched in 2016, that lets fans buy, split and share orders for live events together. Its Social Checkout drawer and Distributed Commerce Button embed into a client's own site, sitting in front of existing ticketing and inventory systems, while the FEVO Enterprise console at gofevo.com handles offer creation, gating, discounting, payouts and reporting. The developer surface is deliberately narrow: a client-side JavaScript widget (GMWidget) any partner can embed, and an Order API data feed that pushes FEVO Sales Report fields into a customer data warehouse using a User ID and Access Key issued by a FEVO representative. FEVO reports 800+ brands in sports, music and entertainment and more than 24 million tickets sold.

Fevo publishes 2 APIs on the APIs.io network. Tagged areas include Company, Ticketing, Event, Group Sales, and Social Commerce.

Fevo’s developer surface includes documentation, support, engineering blog, signup flow, changelog, authentication, and 21 more developer resources.

34.7/100 thin ▬ flat Agent 8/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
2 APIs
CompanyTicketingEventGroup SalesSocial CommerceE-CommerceCheckoutSportsLive EntertainmentEmbedded Commerce

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/fevo: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

FEVO Order API

A data-feed API that returns every field in the FEVO Sales Report — orders and order adjustments — so a customer can pull FEVO transaction data directly into their own data ware...

FEVO Embedded Checkout (Distributed Commerce Button)

The client-side embed surface. A single script tag loads GMWidget from gofevo.com (or gofevo.uk for the UK), and GMWidget.open('offerSlug') opens the FEVO Social Checkout drawer...

Pricing Plans 1

Published pricing tiers and plan structures.

Fevo Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Fevo Rate Limits

0 limits

RATE LIMITS

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Fevo Authentication

3 schemes

SECURITY

Fevo Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Fevo Vulnerability Disclosure

Hackerone · contact published

SECURITY

Fevo Trust Center

SOC 2

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 6

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: fevo
name: Fevo
description: 'FEVO is a New York social-commerce and group-ticketing platform, launched in 2016, that lets fans buy, split
  and share orders for live events together. Its Social Checkout drawer and Distributed Commerce Button embed into a client''s
  own site, sitting in front of existing ticketing and inventory systems, while the FEVO Enterprise console at gofevo.com
  handles offer creation, gating, discounting, payouts and reporting. The developer surface is deliberately narrow: a client-side
  JavaScript widget (GMWidget) any partner can embed, and an Order API data feed that pushes FEVO Sales Report fields into
  a customer data warehouse using a User ID and Access Key issued by a FEVO representative. FEVO reports 800+ brands in sports,
  music and entertainment and more than 24 million tickets sold.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - rate-limits
  - security
  generated: '2026-09-03'
  method: derived
image: https://cdn.prod.website-files.com/63c2beaea55341844ce65d4e/682d14798ca7154c6364947c_FEVO%20Logomark.png
url: https://raw.githubusercontent.com/api-evangelist/fevo/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: stub
x-tier-reason: harvest
specificationVersion: '0.23'
created: '2026-08-12'
modified: '2026-08-12'
tags:
- Company
- Ticketing
- Event
- Group Sales
- Social Commerce
- E-Commerce
- Checkout
- Sports
- Live Entertainment
- Embedded Commerce
tags_raw:
- Company
- Ticketing
- Events
- Group Sales
- Social Commerce
- E-Commerce
- Checkout
- Sports
- Live Entertainment
- Embedded Commerce
apis:
- aid: fevo:order-api
  name: FEVO Order API
  description: A data-feed API that returns every field in the FEVO Sales Report — orders and order adjustments — so a customer
    can pull FEVO transaction data directly into their own data warehouse. Queries run by Order Date or Event Date. Access
    requires a User ID and Access Key issued per team by a FEVO representative; the endpoint definitions document is distributed
    as a Salesforce content-delivery page linked from the Help Center. No public reference, no machine-readable spec.
  humanURL: https://intercom.help/fevoenterprise/en/articles/8912590-api-faqs
  x-base-url: unpublished
  x-base-url-note: 'FEVO names no host for the Order API on any public page. The endpoint definitions are linked only to a
    Salesforce content-delivery URL that requires JavaScript to view (probed 2026-08-12: HTTP 200, 1,359-byte contentDistribution
    shell, x-robots-tag noindex). api.fevo.com and api.gofevo.com do not resolve. Recorded as missing rather than guessed
    from the domain.'
  tags:
  - Order
  - Reporting
  - Data Feed
  tags_raw:
  - Orders
  - Reporting
  - Data Feed
  properties:
  - type: Documentation
    url: https://intercom.help/fevoenterprise/en/articles/8912590-api-faqs
  - type: Authentication
    url: authentication/fevo-authentication.yml
  - type: ErrorCatalog
    url: errors/fevo-problem-types.yml
- aid: fevo:embedded-checkout
  name: FEVO Embedded Checkout (Distributed Commerce Button)
  description: The client-side embed surface. A single script tag loads GMWidget from gofevo.com (or gofevo.uk for the UK),
    and GMWidget.open('offerSlug') opens the FEVO Social Checkout drawer over the partner's own page for the named offer.
    The embedding domain must be allow-listed by FEVO before the drawer will render.
  humanURL: https://intercom.help/fevoenterprise/en/articles/8986183-distributed-commerce-button
  baseURL: https://www.gofevo.com
  tags:
  - Checkout
  - Widget
  - Embedded Commerce
  properties:
  - type: Documentation
    url: https://intercom.help/fevoenterprise/en/collections/9890359-embedded-checkout
  - type: Components
    url: components/fevo-components.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/fevo-domain-security.yml
- type: Website
  url: https://www.fevo.com
- type: SecondaryMarketListing
  url: https://forgeglobal.com/fevo_stock/
- type: Documentation
  url: https://intercom.help/fevoenterprise/en/
- type: Support
  url: https://www.fevo.com/ticket-help
- type: Blog
  url: https://www.fevo.com/blog
- type: SignUp
  url: https://www.fevo.com/demo-request
- type: Login
  url: https://www.gofevo.com/manage/
- type: TermsOfService
  url: https://wf.fevo.com/terms-of-use
- type: PrivacyPolicy
  url: https://wf.fevo.com/privacy-policy
- type: GitHubOrganization
  url: https://github.com/fevo-tech
- type: ChangeLog
  url: changelog/fevo-changelog.yml
- type: Packages
  url: packages/fevo-packages.yml
- type: SDKs
  url: packages/fevo-packages.yml
- type: Components
  url: components/fevo-components.yml
- type: Conventions
  url: conventions/fevo-conventions.yml
- type: Lifecycle
  url: lifecycle/fevo-lifecycle.yml
- type: Authentication
  url: authentication/fevo-authentication.yml
- type: ErrorCatalog
  url: errors/fevo-problem-types.yml
- type: Conformance
  url: conformance/fevo-conformance.yml
- type: Compliance
  url: security/fevo-trust-center.yml
- type: TrustCenter
  url: security/fevo-trust-center.yml
- type: Security
  url: security/fevo-vulnerability-disclosure.yml
- type: VulnerabilityDisclosure
  url: security/fevo-vulnerability-disclosure.yml
- type: Plans
  url: plans/fevo-plans-pricing.yml
- type: RateLimits
  url: rate-limits/fevo-rate-limits.yml
- type: LLMsTxt
  url: llms/fevo-llms.txt
x-contract-note: 'FEVO publishes no machine-readable contract. Full STEP 0b discovery was run on 2026-08-12 against every
  host: /openapi.json, /openapi.yaml, /swagger.json, /api-docs, /docs and /redoc on www.fevo.com, www.gofevo.com, report.gofevo.com
  and fevo-enterprise.com (all 404); /graphql (404); /.well-known/{security.txt,openid-configuration,oauth-authorization-server,api-catalog,ai-plugin.json,agent-card.json,agent.json}
  on every host (all 404); /llms.txt (404). api.fevo.com and api.gofevo.com do not resolve. No MCP server, no A2A agent card,
  no AsyncAPI, no webhook catalog, no Postman collection. The GitHub org github.com/fevo-tech holds 11 repos, every one a
  fork. The Order API''s own definitions document is a Salesforce content-delivery page that requires JavaScript, and access
  requires credentials issued by a FEVO representative. Separately, the entire legacy Fevo.js stack — https://www.fevo.com/docs/v1,
  https://www.fevo.com/api/v1 and https://sdk.fevo.com/v1/fevo.js — returned HTTP 502 with CloudFront reporting it could not
  resolve the origin domain name, with no deprecation notice ever published.'
x-enrichment:
  date: '2026-08-12'
  status: enriched
  artifacts_added: 15
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/fevo"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/fevo/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/fevo/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.