API archive entry · source-reported
Bungie.Net API
These endpoints constitute the functionality exposed by Bungie.net, both for more traditional website functionality and for connectivity to Bungie video games and their related functionality.
Other Media APIs
These records share a directory category and are ordered by similarity of reported access facts. They are a shortlist, not proof of drop-in compatibility.
Aggregators API Service
Aggregators API
Unknown · HTTPS unconfirmed · CORS Unknown
API docs | logoraisr.com
Dig into our logoraisr API reference documentation. We also offer an OpenAPI specification to allow easy integration into your systems. You can download the json file by clicking on the download button. OpenAPI 2.0 Validation Status
Unknown · HTTPS unconfirmed · CORS Unknown
api.video
api.video is an API that encodes on the go to facilitate immediate playback, enhancing viewer streaming experiences across multiple devices and platforms. You can stream live or on-demand online videos within minutes.
Unknown · HTTPS unconfirmed · CORS Unknown
APOD
This endpoint structures the APOD imagery and associated metadata so that it can be repurposed for other applications. In addition, if the concept_tags parameter is set to True, then keywords derived from the image explanation are returned. These keywords could be used as auto-generated hashtags for twitter or instagram feeds; but generally help with discoverability of relevant imagery
Unknown · HTTPS unconfirmed · CORS Unknown
Archive API
The Archive API provides lists of NYT articles by month going back to 1851. You can use it to build your own local database of NYT article metadata.
Unknown · HTTPS unconfirmed · CORS Unknown
ART19 Content API Documentation
The ART19 Content API conforms to the JSON:API specification. API requests **MUST** use the HTTP Accept header: `Accept: application/vnd.api+json` API requests **MUST** be authenticated using the HTTP Authorization header: `Authorization: Token token="your-token", credential="your-credential"` ## General Notes Some query parameters use unencoded [ and ] characters simply for readability. Defaults, examples, and possible values are additionally rendered in double quotes for readability. In practice, query parameters should not have quotes around the values (e.g., `foo=bar` is valid, not `foo="bar"`), and both query parameter keys and values must be percent-encoded, per the requirements in RFC 3986 § 3.4. ## Rate Limiting In order to provide a fair distribution of available resources, all API calls are subject to rate limits. If you exceed the number of API calls per minute granted to your credential, a `429 Too Many Requests` error response will be returned. In that case, a `Retry-After` header MAY be included in the response, describing the number of seconds after which a request can be retried. If you run into a high number of 429 errors, please reach out to ART19 Support to adjus
Unknown · HTTPS unconfirmed · CORS Unknown
How to compare them
Coverage
Compare exact endpoints, fields, geography, history, and update frequency.
Operating cost
Model request volume, caching, overages, support, and migration cost.
Integration risk
Test auth, errors, pagination, latency, versioning, and outage behavior.
Data rights
Review attribution, redistribution, retention, privacy, and commercial-use terms.
Source reference
This page separates source-reported facts from questions that need live provider verification.