Checkin.no API

Name: Checkin.no API API
Brand: Checkin.no API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceOrder ManagementapiKey1 EndpointsREST

For Agents

Send GraphQL queries and mutations to Checkin.no for managing events, bookings, participants, and check-in flows.

Quickstart

Get started with Checkin.no API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"execute a GraphQL query against checkin.no"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Checkin.no API API.

Run GraphQL queries to fetch events, bookings, and participant lists

Execute GraphQL mutations to create or update bookings

Drive check-in workflows for participants on event day

Inspect ticket inventory and event schedules

Pull participant data into reporting or CRM systems

GET STARTED

Start building with Checkin.no API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Checkin.no API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Checkin.no API, keeping it validated and agent-ready. Checkin.no is a Norwegian event registration and ticketing platform widely used for sports events, conferences, and races to handle entries, payments, and on-site check-in. Its API is GraphQL-based and exposed at a single /graphql endpoint that accepts queries and mutations covering events, bookings, participants, and check-in flows. The same endpoint serves both reads and writes, with operation selection driven by the GraphQL document supplied in the request body.

Use Cases

Patterns agents use Checkin.no API API for, with concrete tasks.

★ Event Day Check-In

Run an on-site check-in app that scans participant codes and marks them as arrived. The app sends a GraphQL mutation to /graphql to update the participant's check-in status, then queries for the next list of pending arrivals. Suitable for races, conferences, and ticketed events using Checkin.no as the source of truth.

Send a GraphQL mutation to /graphql that marks participant with reference 'ABC123' as checked in and return the updated status.

Participant Reporting

Pull participant lists for an event into a CRM, finance system, or analytics dashboard. A scheduled job sends a GraphQL query to /graphql requesting events and their participants, transforms the results, and writes them downstream. Useful for organisers who run multiple events on Checkin.no and need consolidated reporting.

Send a GraphQL query asking for all events created in the last 30 days and the number of registered participants in each.

Booking Lookup Service

Build a self-service booking lookup that lets participants find their confirmation by name or reference. A small service forwards the lookup as a GraphQL query to /graphql and returns the matched booking details. Useful when participants lose their confirmation email and need to recover their entry on the day.

Send a GraphQL query searching bookings by the email 'jane@example.com' and return the matching booking's reference and event.

AI Agent for Event Operations

An autonomous agent reads natural-language requests from event staff ('how many checked in?', 'check in the next 10 runners by bib number') and translates them into GraphQL operations against /graphql via Jentic. The Authorization header is held in the Jentic MAXsystem vault, so the agent never sees the API key.

Through Jentic, search 'execute a GraphQL query', load the schema for /graphql, and submit a mutation that checks in participant reference 'ABC123'.

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for checkin.

METHOD

PATH

DESCRIPTION

POST

/graphql

Execute a GraphQL query or mutation against Checkin.no

POST

/graphql

Execute a GraphQL query or mutation against Checkin.no

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Checkin.no API keys are stored encrypted in the Jentic MAXsystem vault. Agents never hold the raw key — Jentic injects it into the Authorization header at execution time.

Intent-based discovery

Agents search Jentic by intent (e.g. 'execute a GraphQL query against checkin.no') and Jentic returns the /graphql operation with its input schema, so the agent submits the right GraphQL document without reading docs.

Time to first call

Direct Checkin.no integration: 1-2 days to learn the GraphQL schema, auth, and error handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Checkfront API

Booking management platform — REST instead of GraphQL, broader inventory and rental focus

Choose Checkfront when the use case is tour, rental, or accommodation bookings; Checkin.no is for event registration and check-in

Complementary

Cheddar Up API

Group payments and collections platform that pairs with event registrations

Choose Cheddar Up when collecting fees outside the formal event registration flow

Complementary

Checkly API

Synthetic monitoring you can use to verify the GraphQL endpoint stays available

Choose Checkly to set up uptime checks against api.checkin.no

FAQs

Specific to using Checkin.no API API through Jentic.

Why is there no official OpenAPI spec for Checkin.no API?

Checkin.no exposes a GraphQL API and does not publish an OpenAPI specification. Jentic generates and maintains this spec, wrapping the GraphQL endpoint so AI agents and developers can call Checkin.no via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Checkin.no API use?

Checkin.no uses an API key passed in the Authorization header. Through Jentic, the key is stored encrypted in the MAXsystem vault and injected at execution time, so it never appears in the agent's context.

Is the Checkin.no API REST or GraphQL?

GraphQL. There is a single POST /graphql endpoint that accepts a query or mutation in the request body. Operation type and field selection are driven by the GraphQL document, not the HTTP path. The interactive GraphiQL explorer is at https://api.checkin.no/graphiql for browsing the schema.

Can I check in participants with the Checkin.no API?

Yes. Send a GraphQL mutation to POST /graphql that updates the participant's check-in status. The response returns the updated participant and event records, which you can then display to event staff or pipe into a kiosk app.

What are the rate limits for the Checkin.no API?

The OpenAPI specification does not declare formal rate limits. Plan for retry-with-backoff on 429 responses and avoid overly broad GraphQL queries — request only the fields you need on each call.

How do I run a Checkin.no GraphQL query through Jentic?

Install the SDK with `pip install jentic`, then call Jentic.search('execute a GraphQL query'), load the schema for /graphql, and execute with your GraphQL document and variables. Jentic injects the Authorization header from the MAXsystem vault.