---
title: "DEV Community"
description: "List public articles and the connected author’s drafts, read an article, and create or update an article through the DEV/Forem API. Native Markdown, tags, canonical URLs and explicit publication state are preserved. Crea"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# DEV Community

<p>List public articles and the connected author’s drafts, read an article, and create or update an article through the DEV/Forem API. Native Markdown, tags, canonical URLs and explicit publication state are preserved. Creation requires an explicit published flag so examples remain drafts. This five-command REST subset excludes comments, images, organization management and other Forem hosts.</p>

<details data-command-index><summary>What you can do (5)</summary>
<h2>What you can do</h2>
<p>Available commands: 5 (3 read, 2 write). Enable only the commands your application needs.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Command</th>
<th>Effect</th>
</tr>
</thead>
<tbody><tr>
<td><a href="https://help.tooluse.net/integrations/dev-to#command-dev-to-articles-list">List one page of public DEV articles</a> — <code>dev-to.articles.list</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/dev-to#command-dev-to-articles-create">Create an explicit DEV article draft or publication</a> — <code>dev-to.articles.create</code></td>
<td>Write</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/dev-to#command-dev-to-articles-mine">List one page of the connected author’s articles and drafts</a> — <code>dev-to.articles.mine</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/dev-to#command-dev-to-articles-get">Read one public article</a> — <code>dev-to.articles.get</code></td>
<td>Read</td>
</tr>
<tr>
<td><a href="https://help.tooluse.net/integrations/dev-to#command-dev-to-articles-update">Update fields of an article owned by the connected author</a> — <code>dev-to.articles.update</code></td>
<td>Write</td>
</tr>
</tbody></table>
</div>
</details>
<h2>Connect and use</h2>

<p><a href="https://www.tooluse.net/tools/integrations/dev-to">Connect and use</a></p>
<p>Open the integration&#39;s connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.</p>
<h2>Get your provider credentials</h2>
<p>Follow these steps for DEV Community, then enter the issued values in the connection form below.</p>
<ol>
<li>On DEV Community, open Settings → Extensions → DEV Community API Keys, give a key a clear description and generate it. Paste it into this connection’s DEV Community API token field. Start with articles.mine to inspect your own drafts and publications. articles.create requires an explicit published value; keep false for drafts and review content before setting true. Article updates require ownership. Select commands and save, then create a separate scoped Tooluse.net API key for your AI client. Never expose your DEV key in the MCP URL.</li>
</ol>
<p><a href="https://developers.forem.com/api/v1#section/Authentication">Official credential setup</a></p>
<h2>Where to enter credentials</h2>
<p>In the integration page, sign in, choose your workspace and open Connect. If a <strong>Credentials</strong> choice is shown, select <strong>Use my credentials</strong>. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.</p>
<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Connection field</th>
<th>Requirement</th>
</tr>
</thead>
<tbody><tr>
<td>DEV Community API token</td>
<td>Required</td>
</tr>
</tbody></table>
</div><p>Open API keys and create a Tooluse.net key for the enabled commands.</p>
<p>Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.</p>
<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Permissions and results</h2>

<p>If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net&#39;s existing permissions. Disabling a connection or revoking a key immediately prevents new calls.</p>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<p>Your connection&#39;s daily allowance and key permissions also apply. Adding a connection does not make a provider request.</p>

<p>Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.</p>

<h2>Call from your client</h2>

<p>Use the shared MCP configuration. Refresh your client&#39;s tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.</p>

<p><a href="https://help.tooluse.net/clients">Configure Claude Code, Codex or Cursor once</a></p>

<h2>Discover your enabled tools</h2>

<p>List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.</p>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"
</code></pre>

<p>Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.</p>

<h2>HTTP call</h2>

<pre><code class="language-bash">curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {}
}'
</code></pre>

<p>Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.</p>

<h2>Commands</h2>

<details id="command-dev-to-articles-list">
<summary><span>List one page of public DEV articles — <code>dev-<wbr>to.<wbr>articles.<wbr>list</code></span></summary>
<p>Run <strong>List one page of public DEV articles</strong> with DEV Community. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/dev-to?command=dev-to.articles.list">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>minimum: 1</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>minimum: 1; maximum: 100</code></td>
</tr>
<tr>
<td><code>query.tag</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.username</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>query.top</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>minimum: 1</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/dev-to/commands/dev-to.articles.list">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-dev-to-articles-create">
<summary><span>Create an explicit DEV article draft or publication — <code>dev-<wbr>to.<wbr>articles.<wbr>create</code></span></summary>
<p>Run <strong>Create an explicit DEV article draft or publication</strong> with DEV Community. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/dev-to?command=dev-to.articles.create">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>body.article</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>body.article.title</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1</code></td>
</tr>
<tr>
<td><code>body.article.body_markdown</code></td>
<td>string</td>
<td>Required</td>
<td></td>
<td><code>minLength: 1</code></td>
</tr>
<tr>
<td><code>body.article.published</code></td>
<td>boolean</td>
<td>Required</td>
<td></td>
<td><code>default: false</code></td>
</tr>
<tr>
<td><code>body.article.description</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.article.tags</code></td>
<td>array</td>
<td>Optional</td>
<td></td>
<td><code>maxItems: 4</code></td>
</tr>
<tr>
<td><code>body.article.tags[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.article.canonical_url</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>format: &quot;uri&quot;</code></td>
</tr>
<tr>
<td><code>body.article.main_image</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>format: &quot;uri&quot;</code></td>
</tr>
<tr>
<td><code>body.article.series</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.article.organization_id</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>minimum: 1</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/dev-to/commands/dev-to.articles.create">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "body": {
    "article": {
      "title": "Example draft",
      "body_markdown": "Draft content",
      "published": false,
      "tags": [
        "testing"
      ]
    }
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-dev-to-articles-mine">
<summary><span>List one page of the connected author’s articles and drafts — <code>dev-<wbr>to.<wbr>articles.<wbr>mine</code></span></summary>
<p>Run <strong>List one page of the connected author’s articles and drafts</strong> with DEV Community. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/dev-to?command=dev-to.articles.mine">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>query</code></td>
<td>object</td>
<td>Optional</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>query.page</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>minimum: 1</code></td>
</tr>
<tr>
<td><code>query.per_page</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>minimum: 1; maximum: 100</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/dev-to/commands/dev-to.articles.mine">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-dev-to-articles-get">
<summary><span>Read one public article — <code>dev-<wbr>to.<wbr>articles.<wbr>get</code></span></summary>
<p>Run <strong>Read one public article</strong> with DEV Community. This is a read command; it does not grant access beyond the connected account&#39;s permissions.</p>

<p>This is a read operation. Provider rate limits and data access rules still apply.</p>

<p><a href="https://www.tooluse.net/tools/integrations/dev-to?command=dev-to.articles.get">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.articleId</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td><code>minimum: 1</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/dev-to/commands/dev-to.articles.get">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "articleId": 1
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<details id="command-dev-to-articles-update">
<summary><span>Update fields of an article owned by the connected author — <code>dev-<wbr>to.<wbr>articles.<wbr>update</code></span></summary>
<p>Run <strong>Update fields of an article owned by the connected author</strong> with DEV Community. This command can change provider data. Review the target and input before invoking it.</p>

<p>This operation can change provider data. Review the input before allowing an agent to call it.</p>

<p><a href="https://www.tooluse.net/tools/integrations/dev-to?command=dev-to.articles.update">Connect and use</a></p>

<p><strong>Parameters</strong></p>

<p>Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.</p>

<div class="nb-table-scroll"><table>
<thead>
<tr>
<th>Parameter</th>
<th>Type</th>
<th>Required in parent</th>
<th>Description</th>
<th>Constraints</th>
</tr>
</thead>
<tbody><tr>
<td><code>path</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>path.articleId</code></td>
<td>integer</td>
<td>Required</td>
<td></td>
<td><code>minimum: 1</code></td>
</tr>
<tr>
<td><code>body</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>body.article</code></td>
<td>object</td>
<td>Required</td>
<td></td>
<td><code>additionalProperties: false</code></td>
</tr>
<tr>
<td><code>body.article.title</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1</code></td>
</tr>
<tr>
<td><code>body.article.body_markdown</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>minLength: 1</code></td>
</tr>
<tr>
<td><code>body.article.published</code></td>
<td>boolean</td>
<td>Optional</td>
<td></td>
<td><code>default: false</code></td>
</tr>
<tr>
<td><code>body.article.description</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.article.tags</code></td>
<td>array</td>
<td>Optional</td>
<td></td>
<td><code>maxItems: 4</code></td>
</tr>
<tr>
<td><code>body.article.tags[]</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.article.canonical_url</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>format: &quot;uri&quot;</code></td>
</tr>
<tr>
<td><code>body.article.main_image</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td><code>format: &quot;uri&quot;</code></td>
</tr>
<tr>
<td><code>body.article.series</code></td>
<td>string</td>
<td>Optional</td>
<td></td>
<td></td>
</tr>
<tr>
<td><code>body.article.organization_id</code></td>
<td>integer</td>
<td>Optional</td>
<td></td>
<td><code>minimum: 1</code></td>
</tr>
</tbody></table>
</div>
<p><strong>Full JSON Schema</strong></p>

<p><a href="https://api.tooluse.net/v1/integrations/dev-to/commands/dev-to.articles.update">Full JSON Schema</a></p>

<p><strong>Example input</strong></p>

<pre><code class="language-json">{
  "path": {
    "articleId": 1
  },
  "body": {
    "article": {
      "title": "Updated draft",
      "published": false
    }
  }
}
</code></pre>

<p>At most 1 provider requests per invocation; timeout: 30 seconds.</p>

</details>
<h2>Errors</h2>

<p>Check the key&#39;s expiry, revocation, workspace and allowed operations.</p>

<p>Reuse the same idempotency key only for the same request.</p>

<p>The connection or provider limit has been reached. Check the receipt before retrying.</p>

<h2>Test the connection</h2>

<p>Open the integration&#39;s commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client&#39;s tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.</p>

<p><a href="https://developers.forem.com/api/v1">Official provider documentation</a></p>

Source: https://help.tooluse.net/integrations/dev-to/index.mdx