Ingresse website screenshot

Ingresse

Ingresse is a Brazilian ticketing-as-a-service (TaaS) platform that powers event ticket sales, access control, and the attendee experience for organizers and partners. Its public developer platform lets integrators build tools and services on top of Ingresse — creating events, selling and validating tickets, managing users, and handling payments — through a versioned REST API (v1 and v2) authenticated with an individually issued API key. Ingresse publishes first-party SDKs for JavaScript/Node, Android, iOS, and PHP, plus message-queue libraries, and hosts its reference documentation on a ReadMe developer portal. Ingresse is backed by 500 Global.

Ingresse publishes 1 API on the APIs.io network. Tagged areas include Company, Ticketing, Events, Ticketing as a Service, and Payments.

Ingresse’s developer surface includes documentation, API reference, support, authentication, sandbox, and 10 more developer resources.

21.2/100 emerging ▬ flat Agent 17/100 agent aware Full breakdown ↓
scored 2026-07-27 · rubric v0.5
AccessSelf serve
1 APIs
CompanyTicketingEventsTicketing as a ServicePaymentsEntertainmentEvent ManagementBrazilSDKs

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 21.2/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 10.4 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 17/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/ingresse: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

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

Ingresse API

Versioned REST API (v1 and v2) for event ticketing — events, tickets, checkout/payments, users, and access control — authenticated with an individually issued API key passed as ...

Security Posture 2

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

Ingresse Authentication

apiKey · 1 scheme

SECURITY

Ingresse Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Company 1

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: ingresse
name: Ingresse
description: Ingresse is a Brazilian ticketing-as-a-service (TaaS) platform that powers event ticket sales, access control,
  and the attendee experience for organizers and partners. Its public developer platform lets integrators build tools and
  services on top of Ingresse — creating events, selling and validating tickets, managing users, and handling payments — through
  a versioned REST API (v1 and v2) authenticated with an individually issued API key. Ingresse publishes first-party SDKs
  for JavaScript/Node, Android, iOS, and PHP, plus message-queue libraries, and hosts its reference documentation on a ReadMe
  developer portal. Ingresse is backed by 500 Global.
url: https://raw.githubusercontent.com/api-evangelist/ingresse/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
x-tier: stub
x-tier-reason: portfolio-lead
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-19'
image: https://ingresse.com/favicon.ico
tags:
- Company
- Ticketing
- Events
- Ticketing as a Service
- Payments
- Entertainment
- Event Management
- Brazil
- SDKs
apis:
- name: Ingresse API
  description: Versioned REST API (v1 and v2) for event ticketing — events, tickets, checkout/payments, users, and access
    control — authenticated with an individually issued API key passed as the `apikey` query parameter.
  humanURL: https://developer.ingresse.com
  baseURL: https://api.ingresse.com
  properties:
  - type: Documentation
    url: https://developer.ingresse.com/docs
  - type: APIReference
    url: https://developer.ingresse.com/reference
  - type: Authentication
    url: authentication/ingresse-authentication.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://ingresse.com
- type: DeveloperPortal
  url: https://developer.ingresse.com
- type: Documentation
  url: https://developer.ingresse.com/docs
- type: APIReference
  url: https://developer.ingresse.com/reference
- type: Support
  url: https://developer.ingresse.com/discuss
- type: GitHubOrganization
  url: https://github.com/ingresse
- type: LLMsTxt
  url: llms/ingresse-llms.txt
- type: Packages
  url: packages/ingresse-packages.yml
- type: SDKs
  url: packages/ingresse-packages.yml
- type: Authentication
  url: authentication/ingresse-authentication.yml
- type: Conventions
  url: conventions/ingresse-conventions.yml
- type: ErrorCatalog
  url: errors/ingresse-error-codes.yml
- type: Lifecycle
  url: lifecycle/ingresse-lifecycle.yml
- type: Sandbox
  url: sandbox/ingresse-sandbox.yml
- type: DomainSecurity
  url: security/ingresse-domain-security.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence