openapi: 3.0.3
info:
title: Forem API V1 agent_sessions followed_tags API
version: 1.0.0
description: "Access Forem articles, users and other resources via API.\n For a real-world example of Forem in action, check out [DEV](https://www.dev.to).\n All endpoints can be accessed with the 'api-key' header and a accept header, but\n some of them are accessible publicly without authentication.\n\n Dates and date times, unless otherwise specified, must be in\n the [RFC 3339](https://tools.ietf.org/html/rfc3339) format."
servers:
- url: https://dev.to/api
description: Production server
security:
- api-key: []
tags:
- name: followed_tags
paths:
/api/follows/tags:
get:
summary: Followed Tags
tags:
- followed_tags
description: This endpoint allows the client to retrieve a list of the tags they follow.
operationId: getFollowedTags
responses:
'401':
description: unauthorized
content:
application/json:
example:
error: unauthorized
status: 401
'200':
description: A List of followed tags
content:
application/json:
example:
- id: 2315
name: tag3
points: 1.0
- id: 2316
name: tag4
points: 1.0
schema:
type: array
items:
$ref: '#/components/schemas/FollowedTag'
/follows/tags:
get:
summary: Followed Tags
tags:
- followed_tags
description: This endpoint allows the client to retrieve a list of the tags they follow.
operationId: getFollowedTags
responses:
'200':
description: A List of followed tags
content:
application/json:
example:
- id: 701
name: tag3
points: 1
- id: 702
name: tag4
points: 1
schema:
type: array
items:
$ref: '#/components/schemas/FollowedTag'
'401':
description: unauthorized
content:
application/json:
example:
error: unauthorized
status: 401
components:
schemas:
FollowedTag:
description: Representation of a followed tag
type: object
properties:
id:
description: Tag id
type: integer
format: int64
name:
type: string
points:
type: number
format: float
required:
- id
- name
- points
securitySchemes:
api-key:
type: apiKey
name: api-key
in: header
description: "API Key authentication.\n\nAuthentication for some endpoints, like write operations on the\nArticles API require a DEV API key.\n\nAll authenticated endpoints are CORS disabled, the API key is intended for non-browser scripts.\n\n### Getting an API key\n\nTo obtain one, please follow these steps:\n\n - visit https://dev.to/settings/extensions\n - in the \"DEV API Keys\" section create a new key by adding a\n description and clicking on \"Generate API Key\"\n\n \n\n - You'll see the newly generated key in the same view\n "