Feedly · OpenAPI Overlay 1.0.0

API Evangelist enhancements for Feedly Trends API

3 actions 3 updates update extends openapi/feedly-trends-openapi.yml
Authorship not recorded No authorship marker is recorded for this file. It is not presented as the provider's.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-providerx-apievangelist-sourcex-apievangelist-harvestedx-apievangelist-conventionsx-apievangelist-errorsx-apievangelist-rate-limitsx-apievangelist-authenticationx-apievangelist-notes

Targets 2

$.info
$

OpenAPI Overlay

Raw ↑
overlay: 1.0.0
info:
  title: API Evangelist enhancements for Feedly Trends API
  version: 1.0.0
extends: openapi/feedly-trends-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-provider: feedly
    x-apievangelist-source: https://developers.feedly.com/.well-known/api-catalog
    x-apievangelist-harvested: '2026-08-12'
    x-apievangelist-conventions: conventions/feedly-conventions.yml
    x-apievangelist-errors: errors/feedly-problem-types.yml
    x-apievangelist-rate-limits: rate-limits/feedly-rate-limits.yml
    x-apievangelist-authentication: authentication/feedly-authentication.yml
- target: $
  update:
    x-apievangelist-notes:
      idempotency: Not supported. No Idempotency-Key header or parameter is published on any Feedly operation;
        retried writes are not server-deduplicated.
      pagination: Cursor pagination via a continuation token. Stop when `continuation` is absent from
        the response. newerThan cannot be older than 31 days.
      rate_limits: 100,000 requests per month per token. X-RateLimit-Count / X-RateLimit-Limit / X-RateLimit-Reset
        on every response; X-RateLimit-Reset is SECONDS remaining, not a timestamp. 429 on exhaustion,
        no Retry-After.
      error_envelope: 'Not RFC 9457. Two proprietary shapes: {errorMessage, errorId} and {errorCode, requestId,
        errorMessage}.'
      response_schemas: The published 200 response schemas are empty objects. Real object shapes are documented
        only in prose at https://developers.feedly.com/reference/ — see data-model/feedly-data-model.yml.
      access: API access requires the Threat Intelligence Advanced plan and an admin-generated token from
        https://feedly.com/i/team/api.
- target: $.info
  update:
    x-apievangelist-empty-response-schemas:
    - list-ttps
    - collect-procedures
    - trending-articles
    - trending-new-malware
    - trending-attackers