Today's episode of Byte Sized is about Leonhard Euler and the creation of Graph Theory.
For more about how Graph Theory works, check out this video from BaseCS!
... body_markdown: "---\r\ntitle: Byte Sized Episode 2: The Creation of Graph Theory \r\npublished: true\r\ndescription: The full story of Leonhard Euler and the creation of this fundamental computer science principle, delivered in a few minutes.\r\ntags: computerscience, graphtheory, bytesized, history\r\ncover_image: https://thepracticaldev.s3.amazonaws.com/i/88e62fzblbluz1dm7xjf.png\r\nseries: Byte Sized Season 1\r\n---\r\n\r\nToday's episode of Byte Sized is about Leonhard Euler and the creation of [Graph Theory](https://en.wikipedia.org/wiki/Graph_theory).\r\n\r\nFor more about how Graph Theory works, check out this video from BaseCS!..." user: name: Vaidehi Joshi username: vaidehijoshi twitter_username: vaidehijoshi github_username: vaidehijoshi website_url: http://www.vaidehi.com profile_image: https://res.cloudinary.com/practicaldev/image/fetch/s--eDGAYAoK--/c_fill,f_auto,fl_progressive,h_640,q_auto,w_640/https://thepracticaldev.s3.amazonaws.com/uploads/user/profile_image/2882/K2evUksb.jpg profile_image_90: https://res.cloudinary.com/practicaldev/image/fetch/s--htZnqMn3--/c_fill,f_auto,fl_progressive,h_90,q_auto,w_90/https://thepracticaldev.s3.amazonaws.com/uploads/user/profile_image/2882/K2evUksb.jpg organization: name: Byte Sized username: bytesized slug: bytesized profile_image: https://res.cloudinary.com/practicaldev/image/fetch/s--sq0DrZfn--/c_fill,f_auto,fl_progressive,h_640,q_auto,w_640/https://thepracticaldev.s3.amazonaws.com/uploads/organization/profile_image/865/652f7998-32a8-4fd9-85ca-dd697d2a9ee9.png profile_image_90: https://res.cloudinary.com/practicaldev/image/fetch/s--1Pt_ICL---/c_fill,f_auto,fl_progressive,h_90,q_auto,w_90/https://thepracticaldev.s3.amazonaws.com/uploads/organization/profile_image/865/652f7998-32a8-4fd9-85ca-dd697d2a9ee9.png ArticleCreateTitleBody: value: article: title: Hello, World! published: true body_markdown: Hello DEV, this is my first post tags: ["discuss", "help"] series: Hello series canonical_url: https://example.com/blog/hello ArticleCreateFrontMatter: value: article: body_markdown: | --- title: Hello, World! published: true tags: discuss, help date: 20190701T10:00Z series: Hello series canonical_url: https://example.com/blog/hello --- Hello DEV, this is my first post ArticleCreateOrganization: value: article: title: Hello, World! published: true body_markdown: Hello DEV, this is my first post tags: ["discuss", "help"] series: Hello series canonical_url: https://example.com/blog/hello organization_id: 1234 Listings: value: - type_of: classified_listing id: 1157 title: TestBash Detroit slug: testbash-detroit-50gb body_markdown: "Do you want to learn about automation? Maybe you're interested in AI-driven testing? Security testing? We have a selection of talks, workshops and training courses to help you in a wide variety of areas in software testing. Join us for our very first trip to Detroit MI! \n\nhttps://bit.ly/TBDetroit" tag_list: events tags: - events category: cfp processed_html: |Do you want to learn about automation? Maybe you're interested in AI-driven testing? Security testing? We have a selection of talks, workshops and training courses to help you in a wide variety of areas in software testing. Join us for our very first trip to Detroit MI!
published: true user: name: Heather username: heatherr twitter_username: github_username: Heather-R website_url: profile_image: https://res.cloudinary.com/practicaldev/image/fetch/s--ggU5WPaT--/c_fill,f_auto,fl_progressive,h_640,q_auto,w_640/https://dev-to-uploads.s3.amazonaws.com/uploads/user/profile_image/136256/11cced64-afd2-4421-91e1-c5f7b216d49b.jpeg profile_image_90: https://res.cloudinary.com/practicaldev/image/fetch/s--CjladMBD--/c_fill,f_auto,fl_progressive,h_90,q_auto,w_90/https://dev-to-uploads.s3.amazonaws.com/uploads/user/profile_image/136256/11cced64-afd2-4421-91e1-c5f7b216d49b.jpeg Listing: value: type_of: classified_listing id: 1157 title: TestBash Detroit slug: testbash-detroit-50gb body_markdown: "Do you want to learn about automation? Maybe you're interested in AI-driven testing? Security testing? We have a selection of talks, workshops and training courses to help you in a wide variety of areas in software testing. Join us for our very first trip to Detroit MI! \n\nhttps://bit.ly/TBDetroit" tag_list: events tags: - events category: cfp processed_html: |Do you want to learn about automation? Maybe you're interested in AI-driven testing? Security testing? We have a selection of talks, workshops and training courses to help you in a wide variety of areas in software testing. Join us for our very first trip to Detroit MI!
published: true user: name: Heather username: heatherr twitter_username: github_username: Heather-R website_url: profile_image: https://res.cloudinary.com/practicaldev/image/fetch/s--ggU5WPaT--/c_fill,f_auto,fl_progressive,h_640,q_auto,w_640/https://dev-to-uploads.s3.amazonaws.com/uploads/user/profile_image/136256/11cced64-afd2-4421-91e1-c5f7b216d49b.jpeg profile_image_90: https://res.cloudinary.com/practicaldev/image/fetch/s--CjladMBD--/c_fill,f_auto,fl_progressive,h_90,q_auto,w_90/https://dev-to-uploads.s3.amazonaws.com/uploads/user/profile_image/136256/11cced64-afd2-4421-91e1-c5f7b216d49b.jpeg ListingCreate: value: classified_listing: title: ACME Conference body_markdown: Awesome conference category: cfp tags: - events ListingCreateOrganization: value: classified_listing: title: ACME Conference body_markdown: Awesome conference category: cfp tags: - events organization_id: 1 ListingUpdate: value: classified_listing: title: ACME New Conference body_markdown: Awesome new conference ListingUpdateActionBump: value: classified_listing: action: bump ListingUpdateActionPublish: value: classified_listing: action: publish ListingUpdateActionUnpublish: value: classified_listing: action: unpublish WebhookCreate: value: webhook_endpoint: target_url: https://example.com/webhooks/webhook1 source: DEV events: - article_created WebhookShow: value: type_of: webhook_endpoint id: 1 source: DEV target_url: https://example.com/webhooks/webhook1 events: - article_created created_at: "2019-09-02T09:47:39.230Z" user: name: bob username: bob twitter_username: github_username: bob website_url: profile_image: "..." profile_image_90: "..." tags: - name: articles description: Articles are all the posts users create on DEV - name: listings description: Listings are classified ads - name: users description: Users own resources that require authentication - name: webhooks description: Webhooks are HTTP endpoints registered to receive events paths: /articles: get: operationId: getArticles summary: Published articles description: | This endpoint allows the client to retrieve a list of articles. "Articles" are all the posts that users create on DEV that typically show up in the feed. They can be a blog post, a discussion question, a help thread etc. but is referred to as article within the code. By default it will return featured, published articles ordered by descending popularity. It supports pagination, each page will contain `30` articles by default. tags: - articles parameters: - name: page in: query description: Pagination page. schema: type: integer format: int32 example: 1 - name: per_page in: query description: Page size (defaults to 30 with a maximum of 1000). schema: type: integer format: int32 example: 30 - name: tag in: query description: | Using this parameter will retrieve articles that contain the requested tag. Articles will be ordered by descending popularity. This parameter can be used in conjuction with `top`. schema: type: string example: discuss - name: username in: query description: | Using this parameter will retrieve articles belonging to a User or Organization ordered by descending publication date. If `state=all` the number of items returned will be `1000` instead of the default `30`. This parameter can be used in conjuction with `state`. schema: type: string example: ben - name: state in: query description: | Using this parameter will allow the client to check which articles are fresh or rising. If `state=fresh` the server will return fresh articles. If `state=rising` the server will return rising articles. This param can be used in conjuction with `username`, only if set to `all`. schema: type: string enum: [fresh, rising, all] example: fresh - name: top in: query description: | Using this parameter will allow the client to return the most popular articles in the last `N` days. `top` indicates the number of days since publication of the articles returned. This param can be used in conjuction with `tag`. schema: type: integer format: int32 example: 2 - name: collection_id in: query description: | Adding this will allow the client to return the list of articles belonging to the requested collection, ordered by ascending publication date. schema: type: integer format: int32 example: 99 responses: 200: description: A list of articles content: application/json: schema: type: array items: $ref: "#/components/schemas/ArticleIndex" examples: articles-success: $ref: "#/components/examples/ArticlesIndex" x-code-samples: # https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-code-samples - lang: Shell label: curl (all articles) source: | curl https://dev.to/api/articles - lang: Shell label: curl (user's articles) source: | curl https://dev.to/api/articles?username=ben post: operationId: createArticle summary: Create a new article description: | This endpoint allows the client to create a new article. "Articles" are all the posts that users create on DEV that typically show up in the feed. They can be a blog post, a discussion question, a help thread etc. but is referred to as article within the code. ### Rate limiting There is a limit of 10 articles created each 30 seconds by the same user. ### Additional resources - [Rails tests for Articles API](https://github.com/thepracticaldev/dev.to/blob/master/spec/requests/api/v0/articles_spec.rb) tags: - articles requestBody: description: Article to create content: application/json: schema: $ref: "#/components/schemas/ArticleCreate" examples: article-create-title-body: $ref: "#/components/examples/ArticleCreateTitleBody" article-create-front-matter: $ref: "#/components/examples/ArticleCreateFrontMatter" article-create-organization: $ref: "#/components/examples/ArticleCreateOrganization" responses: 201: description: A newly created article content: application/json: schema: $ref: "#/components/schemas/ArticleShow" examples: article-success: $ref: "#/components/examples/ArticleShow" headers: Location: description: The URL of the new article schema: type: string format: url 400: description: BadRequest content: application/json: schema: $ref: "#/components/schemas/APIError" examples: error-bad-request: $ref: "#/components/examples/ErrorBadRequest" 401: description: Unauthorized content: application/json: schema: $ref: "#/components/schemas/APIError" examples: error-unauthorized: $ref: "#/components/examples/ErrorUnauthorized" 422: description: Unprocessable Entity content: application/json: schema: $ref: "#/components/schemas/APIError" examples: error-unprocessable-entity: $ref: "#/components/examples/ErrorUnprocessableEntity" security: - api_key: [] - oauth2: [] x-code-samples: # https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-code-samples - lang: Shell label: curl source: | curl -X POST -H "Content-Type: application/json" \ -H "api-key: API_KEY" \ -d '{"article":{"title":"Title","body_markdown":"Body","published":false,"tags":["discuss", "javascript"]}}' \ https://dev.to/api/articles - lang: Shell label: curl (with front matter) source: | curl -X POST -H "Content-Type: application/json" \ -H "api-key: API_KEY" \ -d '{"article":{"body_markdown":"---\ntitle:A sample article about...\npublished:false\n---\n..."}}' \ https://dev.to/api/articles /articles/{id}: get: operationId: getArticleById summary: A published article description: | This endpoint allows the client to retrieve a single published article given its `id`. tags: - articles parameters: - name: id in: path required: true description: Id of the article schema: type: integer format: int32 example: 150589 responses: 200: description: An article content: application/json: schema: $ref: "#/components/schemas/ArticleShow" examples: article-success: $ref: "#/components/examples/ArticleShow" 404: description: Resource not found content: application/json: schema: $ref: "#/components/schemas/APIError" examples: article-not-found: $ref: "#/components/examples/ErrorNotFound" x-code-samples: # https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-code-samples - lang: Shell label: curl source: | curl https://dev.to/api/articles/150589 put: operationId: updateArticle summary: Update an article description: | This endpoint allows the client to update an existing article. "Articles" are all the posts that users create on DEV that typically show up in the feed. They can be a blog post, a discussion question, a help thread etc. but is referred to as article within the code. ### Rate limiting There are no limits on the amount of updates. ### Additional resources - [Rails tests for Articles API](https://github.com/thepracticaldev/dev.to/blob/master/spec/requests/api/v0/articles_spec.rb) tags: - articles parameters: - name: id in: path required: true description: Id of the article schema: type: integer format: int32 example: 150589 requestBody: description: | Article params for the update. *Note: if the article contains a front matter in its body, its front matter properties will still take precedence over any JSON equivalent params, which means that the full body_markdown with the modified front matter params needs to be provided for an update to be successful* content: application/json: schema: $ref: "#/components/schemas/ArticleUpdate" examples: article-update-title-body: $ref: "#/components/examples/ArticleCreateTitleBody" article-update-front-matter: $ref: "#/components/examples/ArticleCreateFrontMatter" article-update-organization: $ref: "#/components/examples/ArticleCreateOrganization" responses: 200: description: The updated article content: application/json: schema: type: object $ref: "#/components/schemas/ArticleShow" examples: article-success: $ref: "#/components/examples/ArticleShow" 400: description: BadRequest content: application/json: schema: type: object $ref: "#/components/schemas/APIError" examples: error-bad-request: $ref: "#/components/examples/ErrorBadRequest" 401: description: Unauthorized content: application/json: schema: type: object $ref: "#/components/schemas/APIError" examples: error-unauthorized: $ref: "#/components/examples/ErrorUnauthorized" 422: description: Unprocessable Entity content: application/json: schema: type: object $ref: "#/components/schemas/APIError" examples: error-unprocessable-entity: $ref: "#/components/examples/ErrorUnprocessableEntity" security: - api_key: [] - oauth2: [] x-code-samples: # https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-code-samples - lang: Shell label: curl source: | curl -X PUT -H "Content-Type: application/json" \ -H "api-key: API_KEY" \ -d '{"article":{"title":"Title"}' \ https://dev.to/api/articles/{id} /articles/me: get: operationId: getUserArticles summary: User's articles description: | This endpoint allows the client to retrieve a list of published articles on behalf of an authenticated user. "Articles" are all the posts that users create on DEV that typically show up in the feed. They can be a blog post, a discussion question, a help thread etc. but is referred to as article within the code. Published articles will be in reverse chronological publication order. It will return published articles with pagination. By default a page will contain `30` articles. tags: - articles - users parameters: - name: page in: query description: Pagination page. schema: type: integer format: int32 example: 1 - name: per_page in: query description: Page size (defaults to 30 with a maximum of 1000). schema: type: integer format: int32 example: 30 responses: 200: description: A list of published articles content: application/json: schema: type: array items: $ref: "#/components/schemas/ArticleMe" security: - api_key: [] - oauth2: [] x-code-samples: # https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-code-samples - lang: Shell label: curl source: | curl -H "api-key: API_KEY" https://dev.to/api/articles/me /articles/me/published: get: operationId: getUserPublishedArticles summary: User's published articles description: | This endpoint allows the client to retrieve a list of published articles on behalf of an authenticated user. "Articles" are all the posts that users create on DEV that typically show up in the feed. They can be a blog post, a discussion question, a help thread etc. but is referred to as article within the code. Published articles will be in reverse chronological publication order. It will return published articles with pagination. By default a page will contain `30` articles. tags: - articles - users parameters: - name: page in: query description: Pagination page. schema: type: integer format: int32 example: 1 - name: per_page in: query description: Page size (defaults to 30 with a maximum of 1000). schema: type: integer format: int32 example: 30 responses: 200: description: A list of published articles content: application/json: schema: type: array items: $ref: "#/components/schemas/ArticleMe" security: - api_key: [] - oauth2: [] x-code-samples: # https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-code-samples - lang: Shell label: curl source: | curl -H "api-key: API_KEY" https://dev.to/api/articles/me/published /articles/me/unpublished: get: operationId: getUserUnpublishedArticles summary: User's unpublished articles description: | This endpoint allows the client to retrieve a list of unpublished articles on behalf of an authenticated user. "Articles" are all the posts that users create on DEV that typically show up in the feed. They can be a blog post, a discussion question, a help thread etc. but is referred to as article within the code. Unpublished articles will be in reverse chronological creation order. It will return unpublished articles with pagination. By default a page will contain `30` articles. tags: - articles - users parameters: - name: page in: query description: Pagination page. schema: type: integer format: int32 example: 1 - name: per_page in: query description: Page size (defaults to 30 with a maximum of 1000). schema: type: integer format: int32 example: 30 responses: 200: description: A list of articles content: application/json: schema: type: array items: $ref: "#/components/schemas/ArticleMe" security: - api_key: [] - oauth2: [] x-code-samples: # https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-code-samples - lang: Shell label: curl source: | curl -H "api-key: API_KEY" https://dev.to/api/articles/me/unpublished /articles/me/all: get: operationId: getUserAllArticles summary: User's all articles description: | This endpoint allows the client to retrieve a list of all articles on behalf of an authenticated user. "Articles" are all the posts that users create on DEV that typically show up in the feed. They can be a blog post, a discussion question, a help thread etc. but is referred to as article within the code. It will return both published and unpublished articles with pagination. Unpublished articles will be at the top of the list in reverse chronological creation order. Published articles will follow in reverse chronological publication order. By default a page will contain `30` articles. tags: - articles - users parameters: - name: page in: query description: Pagination page. schema: type: integer format: int32 example: 1 - name: per_page in: query description: Page size (defaults to 30 with a maximum of 1000). schema: type: integer format: int32 example: 30 responses: 200: description: A list of articles content: application/json: schema: type: array items: $ref: "#/components/schemas/ArticleMe" security: - api_key: [] - oauth2: [] x-code-samples: # https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-code-samples - lang: Shell label: curl source: | curl -H "api-key: API_KEY" https://dev.to/api/articles/me/all /listings: get: operationId: getListings summary: Published listings description: | This endpoint allows the client to retrieve a list of listings. "Listings" are classified ads that users create on DEV. They can be related to conference announcements, job offers, mentorships, upcoming events and more. By default it will return published listings ordered by descending freshness. It supports pagination, each page will contain `30` articles by default. tags: - listings parameters: - name: page in: query description: Pagination page. schema: type: integer format: int32 example: 1 - name: per_page in: query description: Page size (defaults to 30 with a maximum of 100). schema: type: integer format: int32 example: 30 - name: category in: query description: | Using this parameter will return listings belonging to the requested category. schema: type: string example: cfp responses: 200: description: A list of listings content: application/json: schema: type: array items: $ref: "#/components/schemas/Listing" examples: listings-success: $ref: "#/components/examples/Listings" x-code-samples: # https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-code-samples - lang: Shell label: curl (all listings) source: | curl https://dev.to/api/listings post: operationId: createListing summary: Create a new listing description: | This endpoint allows the client to create a new listing. "Listings" are classified ads that users create on DEV. They can be related to conference announcements, job offers, mentorships, upcoming events and more. The user creating the listing or the organization on which behalf the user is creating for need to have enough creadits for this operation to be successful. The server will prioritize the organization's credits over the user's credits. ### Additional resources - [Rails tests for Listings API](https://github.com/thepracticaldev/dev.to/blob/master/spec/requests/api/v0/classified_listings_spec.rb) tags: - listings requestBody: description: Listing to create content: application/json: schema: $ref: "#/components/schemas/ListingCreate" examples: listing-create: $ref: "#/components/examples/ListingCreate" listing-create-organization: $ref: "#/components/examples/ListingCreateOrganization" responses: 201: description: A newly created Listing content: application/json: schema: $ref: "#/components/schemas/Listing" examples: article-success: $ref: "#/components/examples/Listing" 400: description: BadRequest content: application/json: schema: $ref: "#/components/schemas/APIError" examples: error-bad-request: $ref: "#/components/examples/ErrorBadRequest" 401: description: Unauthorized content: application/json: schema: $ref: "#/components/schemas/APIError" examples: error-unauthorized: $ref: "#/components/examples/ErrorUnauthorized" 402: description: PaymentRequired content: application/json: schema: $ref: "#/components/schemas/APIError" examples: error-unauthorized: $ref: "#/components/examples/ErrorPaymentRequired" 422: description: Unprocessable Entity content: application/json: schema: $ref: "#/components/schemas/APIError" examples: error-unprocessable-entity: $ref: "#/components/examples/ErrorUnprocessableEntity" security: - api_key: [] x-code-samples: # https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-code-samples - lang: Shell label: curl source: | curl -X POST -H "Content-Type: application/json" \ -H "api-key: API_KEY" \ -d '{"classified_listing":{"title":"Title","body_markdown":"Body","category":"cfp"}}' \ https://dev.to/api/listings - lang: Shell label: curl (with tags) source: | curl -X POST -H "Content-Type: application/json" \ -H "api-key: API_KEY" \ -d '{"classified_listing":{"title":"Title","body_markdown":"Body","category":"cfp","tags":["python"]}}' \ https://dev.to/api/listings - lang: Shell label: curl (draft) source: | curl -X POST -H "Content-Type: application/json" \ -H "api-key: API_KEY" \ -d '{"classified_listing":{"title":"Title","body_markdown":"Body","category":"cfp","action":"draft"}}' \ https://dev.to/api/listings /listings/category/{category}: get: operationId: getListingsByCategory summary: Published listings by category description: | This endpoint allows the client to retrieve a list of listings belonging to the specified category. "Listings" are classified ads that users create on DEV. They can be related to conference announcements, job offers, mentorships, upcoming events and more. By default it will return published listings ordered by descending freshness. It supports pagination, each page will contain `30` articles by default. tags: - listings parameters: - name: category in: path required: true description: The category of the listing schema: $ref: "#/components/schemas/ListingCategory" - name: page in: query description: Pagination page. schema: type: integer format: int32 example: 1 - name: per_page in: query description: Page size (defaults to 30 with a maximum of 100). schema: type: integer format: int32 example: 30 responses: 200: description: A list of listings content: application/json: schema: type: array items: $ref: "#/components/schemas/Listing" examples: listings-success: $ref: "#/components/examples/Listings" x-code-samples: # https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-code-samples - lang: Shell label: curl (call for papers listings) source: | curl https://dev.to/api/listings/category/cfp /listings/{id}: get: operationId: getListingById summary: A listing description: | This endpoint allows the client to retrieve a single listing given its `id`. An unpublished listing is only accessible if authentication is supplied and it belongs to the authenticated user. tags: - listings parameters: - name: id in: path required: true description: Id of the listing schema: type: integer format: int32 example: 1 responses: 200: description: A listing content: application/json: schema: $ref: "#/components/schemas/Listing" examples: article-success: $ref: "#/components/examples/Listing" 404: description: Resource not found content: application/json: schema: $ref: "#/components/schemas/APIError" examples: article-not-found: $ref: "#/components/examples/ErrorNotFound" security: - {} # this indicates that authentication is optional - api_key: [] x-code-samples: # https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-code-samples - lang: Shell label: curl source: | curl https://dev.to/api/listings/1184 - lang: Shell label: curl (with authentication) source: | curl -H "api-key: API_KEY" https://dev.to/api/listings/1185 put: operationId: updateListing summary: Update a listing description: | This endpoint allows the client to update an existing listing. tags: - listings parameters: - name: id in: path required: true description: Id of the listing schema: type: integer format: int32 example: 1184 requestBody: description: | Listing params for the update. **Note**: except for bumping, publishing and unpublishing there are the following restrictions on the ability to update listings: - the payload has to contain at least one param among `title`, `body_markdown` or `tags`/`tag_list` - the listing can't be updated if it has not been bumped in the last 24 hours - the listing can't be updated if it has been published but not recently bumped content: application/json: schema: $ref: "#/components/schemas/ListingUpdate" examples: listing-update-action-bump: $ref: "#/components/examples/ListingUpdateActionBump" listing-update-action-publish: $ref: "#/components/examples/ListingUpdateActionPublish" listing-update-action-unpublish: $ref: "#/components/examples/ListingUpdateActionUnpublish" listing-update: $ref: "#/components/examples/ListingUpdate" responses: 200: description: The updated article content: application/json: schema: type: object $ref: "#/components/schemas/ArticleShow" examples: article-success: $ref: "#/components/examples/ArticleShow" 400: description: BadRequest content: application/json: schema: type: object $ref: "#/components/schemas/APIError" examples: error-bad-request: $ref: "#/components/examples/ErrorBadRequest" 401: description: Unauthorized content: application/json: schema: type: object $ref: "#/components/schemas/APIError" examples: error-unauthorized: $ref: "#/components/examples/ErrorUnauthorized" 402: description: PaymentRequired content: application/json: schema: type: object $ref: "#/components/schemas/APIError" examples: error-unauthorized: $ref: "#/components/examples/ErrorPaymentRequired" 422: description: Unprocessable Entity content: application/json: schema: type: object $ref: "#/components/schemas/APIError" examples: error-unprocessable-entity: $ref: "#/components/examples/ErrorUnprocessableEntity" security: - api_key: [] x-code-samples: # https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-code-samples - lang: Shell label: curl (bump) source: | curl -X PUT -H "Content-Type: application/json" \ -H "api-key: API_KEY" \ -d '{"classified_listing":{"action":"bump"}' \ https://dev.to/api/listings/{id} - lang: Shell label: curl (update) source: | curl -X PUT -H "Content-Type: application/json" \ -H "api-key: API_KEY" \ -d '{"classified_listing":{"title":"Title"}' \ https://dev.to/api/listings/{id} /webhooks: get: operationId: getWebhooks summary: Webhooks description: | This endpoint allows the client to retrieve a list of webhooks they have previously registered. "Webhooks" are used to register HTTP endpoints that will be called once a relevant event is triggered inside the web application, events like `article_created`, `article_updated`. It will return all webhooks, without pagination. tags: - webhooks responses: 200: description: A list of webhooks content: application/json: schema: type: array items: $ref: "#/components/schemas/WebhookIndex" examples: webhooks-success: summary: Successful response value: - type_of: webhook_endpoint id: 1 source: DEV target_url: https://example.com/webhooks/webhook1 events: - article_created created_at: "2019-09-02T09:47:39.230Z" security: - api_key: [] - oauth2: [] x-code-samples: # https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-code-samples - lang: Shell label: curl source: | curl -H "api-key: API_KEY" https://dev.to/api/webhooks post: operationId: createWebhook summary: Create a new webhook description: | This endpoint allows the client to create a new webhook. "Webhooks" are used to register HTTP endpoints that will be called once a relevant event is triggered inside the web application, events like `article_created`, `article_updated`. tags: - webhooks requestBody: description: Webhook to create content: application/json: schema: $ref: "#/components/schemas/WebhookCreate" examples: webhook-create: $ref: "#/components/examples/WebhookCreate" responses: 201: description: A newly created webhook content: application/json: schema: type: object $ref: "#/components/schemas/WebhookShow" examples: webhook-success: $ref: "#/components/examples/WebhookShow" 400: description: BadRequest content: application/json: schema: type: object $ref: "#/components/schemas/APIError" examples: error-bad-request: $ref: "#/components/examples/ErrorBadRequest" 401: description: Unauthorized content: application/json: schema: type: object $ref: "#/components/schemas/APIError" examples: error-unauthorized: $ref: "#/components/examples/ErrorUnauthorized" 422: description: Unprocessable Entity content: application/json: schema: type: object $ref: "#/components/schemas/APIError" examples: error-unprocessable-entity: $ref: "#/components/examples/ErrorUnprocessableEntity" security: - api_key: [] - oauth2: [] x-code-samples: # https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-code-samples - lang: Shell label: curl source: | curl -X POST -H "Content-Type: application/json" \ -H "api-key: API_KEY" \ -d '{"webhook_endpoint":{"target_url":"https://example.org/webhooks/webhook1","source":"DEV","events":["article_created"]}}' \ https://dev.to/api/webhooks /webhooks/{id}: get: operationId: getWebhookById summary: A webhook endpoint description: | This endpoint allows the client to retrieve a single webhook given its `id`. tags: - webhooks parameters: - name: id in: path required: true description: Id of the webhook schema: type: integer format: int32 example: 123 responses: 200: description: A webhook endpoint content: application/json: schema: type: object $ref: "#/components/schemas/WebhookShow" examples: webhook-success: $ref: "#/components/examples/WebhookShow" 401: description: Unauthorized content: application/json: schema: type: object $ref: "#/components/schemas/APIError" examples: article-unauthorized: $ref: "#/components/examples/ErrorUnauthorized" 404: description: Resource not found content: application/json: schema: type: object $ref: "#/components/schemas/APIError" examples: article-not-found: $ref: "#/components/examples/ErrorNotFound" security: - api_key: [] - oauth2: [] x-code-samples: # https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-code-samples - lang: Shell label: curl source: | curl https://dev.to/api/webhooks/123 delete: operationId: deleteWebhook summary: A webhook endpoint description: | This endpoint allows the client to delete a single webhook given its `id`. tags: - webhooks parameters: - name: id in: path required: true description: Id of the webhook schema: type: integer format: int32 example: 123 responses: 204: description: A successful deletion 401: description: Unauthorized content: application/json: schema: $ref: "#/components/schemas/APIError" examples: article-unauthorized: $ref: "#/components/examples/ErrorUnauthorized" 404: description: Resource not found content: application/json: schema: $ref: "#/components/schemas/APIError" examples: article-not-found: $ref: "#/components/examples/ErrorNotFound" security: - api_key: [] - oauth2: [] x-code-samples: # https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-code-samples - lang: Shell label: curl source: | curl -X DELETE \ -H "api-key: API_KEY" \ https://dev.to/api/webhooks/1