Integrating Multiple Blog APIs into an Astro Site: Dev.to and Hashnode

If you're like me, you probably write on several blogging platforms. In my case, I use both Dev.to and Hashnode to reach different audiences. But what happens when you want to display all your posts on your personal site? Today I will show you how I integrated both APIs into my portfolio built with Astro.

The Challenge

The main challenge was:

1. Get messages from two different APIs
2. Unify data format
3. Order them chronologically
4. Handle errors and rate limiting
5. Secure typing with TypeScript

Initial Configuration

First, we define the interfaces to type our data:

interface BlogPost {
  title: string;
  brief: string;
  slug: string;
  dateAdded: string;
  rawDate: string;
  coverImage: string;
  url: string;
  source: string;
}

interface HashnodeEdge {
  node: {
    title: string;
    brief: string;
    slug: string;
    dateAdded: string;
    coverImage?: {
      url: string;
    };
    url: string;
  };
}

Integrating Dev.to

The Dev.to API is RESTful and fairly straightforward. Here is how I implemented it:

async function getDevToPosts() {
  try {
    const params = new URLSearchParams({
      username: 'tuUsuario',
      per_page: '20',
      state: 'all',
      sort: 'published_at',
      order: 'desc'
    });

    const headers = {
      'Accept': 'application/vnd.forem.api-v1+json'
    };

    // Agregar API key si está disponible
    if (import.meta.env.DEV_TO_API_KEY) {
      headers['api-key'] = import.meta.env.DEV_TO_API_KEY;
    }

    const response = await fetch(`https://dev.to/api/articles?${params}`, { headers });

    if (!response.ok) {
      throw new Error(`HTTP ${response.status}`);
    }

    const posts = await response.json();

    return posts.map((post: any) => ({
      title: post.title,
      brief: post.description,
      slug: post.slug,
      dateAdded: formatDate(post.published_timestamp),
      rawDate: post.published_timestamp,
      coverImage: post.cover_image || '/images/default-post.png',
      url: post.url,
      source: 'devto'
    }));
  } catch (error) {
    console.error('Error al obtener posts de Dev.to:', error);
    return [];
  }
}

Integrating Hashnode

Hashnode uses GraphQL, which requires a slightly different approach:

async function getHashnodePosts() {
  try {
    const query = `
      query {
        publication(host: "tuBlog.hashnode.dev") {
          posts(first: 20) {
            edges {
              node {
                title
                brief
                slug
                dateAdded: publishedAt
                coverImage {
                  url
                }
                url
              }
            }
          }
        }
      }
    `;

    const response = await fetch('https://gql.hashnode.com', {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify({ query })
    });

    const { data } = await response.json();

    return data.publication.posts.edges.map((edge: HashnodeEdge) => ({
      title: edge.node.title,
      brief: edge.node.brief,
      slug: edge.node.slug,
      dateAdded: formatDate(edge.node.dateAdded),
      rawDate: edge.node.dateAdded,
      coverImage: edge.node.coverImage?.url || '/images/default-post.png',
      url: edge.node.url,
      source: 'hashnode'
    }));
  } catch (error) {
    console.error('Error al obtener posts de Hashnode:', error);
    return [];
  }
}

Combining the Results

The magic happens when combining and ordering the posts:

const hashnodePosts = await getHashnodePosts();
const devtoPosts = await getDevToPosts();

const allBlogPosts = [...hashnodePosts, ...devtoPosts]
  .sort((a, b) => new Date(b.rawDate).getTime() - new Date(a.rawDate).getTime());

Error Handling and Rate Limiting

To handle rate limiting and errors, I implemented these strategies:

Client side cache:

const CACHE_DURATION = 5 * 60 * 1000; // 5 minutos
let postsCache = {
  data: null,
  timestamp: 0
};

async function getAllPosts() {
  const now = Date.now();
  if (postsCache.data && (now - postsCache.timestamp) 



<h3>
  
  
  Retries with exponential backoff:
</h3>



<pre class="brush:php;toolbar:false">async function fetchWithRetry(url: string, options: any, retries = 3) {
  for (let i = 0; i  setTimeout(resolve, parseInt(retryAfter) * 1000));
        continue;
      }
      return response;
    } catch (error) {
      if (i === retries - 1) throw error;
      await new Promise(resolve => setTimeout(resolve, Math.pow(2, i) * 1000));
    }
  }
}

Rendered in Astro

Finally, we render the posts in our Astro component:

---
const allBlogPosts = await getAllPosts();
---

<div>



<p>This integration allows us to:</p>

<ul>
<li>Maintain a single source of truth for our posts</li>
<li>Show content from multiple platforms</li>
<li>Handle errors elegantly</li>
<li>Maintain a typed and secure code</li>
</ul>

<p>The full code is available on my GitHub.</p>

<p>Have you integrated other blogging platforms into your site? Share your experiences in the comments! ?</p>

<h2>
  
  
  webdev #astro #typescript #api
</h2>


          </div>

            
        

The above is the detailed content of Integrating Multiple Blog APIs into an Astro Site: Dev.to and Hashnode. For more information, please follow other related articles on the PHP Chinese website!