canonical: https://jentic.com/apis/checkin.no/checkin-no # Checkin.no API 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. ## For AI agents Send GraphQL queries and mutations to Checkin.no for managing events, bookings, participants, and check-in flows. ## Scope Does not handle payment processing, marketing campaigns, or hotel bookings - use for event registration, participant lookup, and on-site check-in only. ## Capabilities - 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 ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 your Jentic One instance, so the agent never sees the API key. Example prompt: Through Jentic, search 'execute a GraphQL query', load the schema for /graphql, and submit a mutation that checks in participant reference 'ABC123'. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/graphql` | Execute a GraphQL query or mutation against Checkin.no | ## Key resources - **GraphQL Endpoint** — Single /graphql endpoint that handles all queries and mutations - **Events** — GraphQL types representing event metadata, dates, and capacity - **Bookings** — GraphQL types for participant registrations and confirmations - **Check-in** — GraphQL mutations that update a participant's arrival status ## Why Jentic - **Setup:** Wiring Checkin.no by hand means handling its Authorization header key and composing valid GraphQL documents against its single endpoint yourself. Through Jentic you install once, import the Checkin.no API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Checkin.no exposes a single /graphql operation, so scope the agent to that operation and the registration and check-in queries it needs. You choose that set, so the agent runs only the queries and mutations you allow. - **Credential handling:** Your Checkin.no API key is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'register an event participant' or 'check in an attendee', and Jentic returns the /graphql operation with its input schema so the agent submits the right GraphQL document without browsing the reference docs. ## Related APIs - **Checkfront API** — Booking management platform - REST instead of GraphQL, broader inventory and rental focus - **Cheddar Up API** — Group payments and collections platform that pairs with event registrations - **Checkly API** — Synthetic monitoring you can use to verify the GraphQL endpoint stays available ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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 your Jentic One instance 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 your Jentic One instance. ### Can I limit what my agent is allowed to do with the Checkin.no API? Yes. Checkin.no exposes a single POST /graphql operation, and because Jentic One is self-hosted by you, your own rules decide which GraphQL queries and mutations the agent may send through it. You can allow only the registration, participant-lookup, and check-in operations you need and withhold the rest, so the agent runs no operation you have not permitted. The Checkin.no API key stays in your Jentic One instance and is injected into the Authorization header at execution time, so the agent never sees it.