How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Blackbird Check-ins API

Filtered visit records.

Blackbird Check-ins API is one of 10 APIs that Blackbird publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Check-ins. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 2 operations across 2 paths, and defines 9 schemas. It is described by OpenAPI 3.0.3, at version 1.0.

Requests are made against a single base URL, https://api.staging.blackbird.xyz/flynet/v1.

2 operations 2 paths 9 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0
Base URL
https://api.blackbird.xyz/flynet/v1
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Blackbird Check-ins API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (oauthBearer). An API key is passed in the header as X-API-Key (apiKey). By default, every request must be authenticated.

  • oauthBearer — OAuth 2.0 access token. Required for the /users/me/ routes (profile, status, wallets, tags, check-ins, memberships) and all payment intent routes.
  • apiKey — Server-to-server API key prefixed flylive... (production) or flytest... (staging/dev). Required on restaurant and location Discovery routes and on the /checkin…

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Check-ins 2

Filtered visit records.

GET
/check_ins
List check-ins
listCheckIns 7 params → 200400401403
GET
/check_ins/{id}
Get a check-in
getCheckIn 1 param → 200401403404

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are Location (17 properties), Restaurant (12 properties), Address (6 properties), CheckIn (6 properties). Each schema is shown below with its type and property counts.

Location
object
17 properties 11 required
Address
object
6 properties
CheckInList
object
2 properties 2 required
CheckIn
object
6 properties 5 required
Neighborhood
object
4 properties
Coordinate
object
2 properties
Restaurant
object
12 properties 8 required
Pagination
object
5 properties 5 required
Error
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

blackbird-check-ins-api-openapi.yml Raw ↑

Other APIs Blackbird publishes across the network.

Blackbird App API
Blackbird Challenges API
Blackbird Locations API
Blackbird Memberships API
Blackbird Payments API
Blackbird Restaurants API
Blackbird Rewards API
Blackbird Specials API
Blackbird Users API
Where this information came from

This is an independent, third-party profile of Blackbird Check-ins API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.