# Common Issues

## Connection issues

<details>

<summary>"Invalid API key" or authentication error on setup</summary>

This usually means the API key was entered incorrectly, or the Blogger API v3 hasn't been enabled in your Google Cloud project. Go to the [Google Cloud Console](https://console.cloud.google.com/), open **APIs & Services > Library**, search for "Blogger API v3", and make sure it's enabled. Then check that the API key you're using was created in the same project.

</details>

<details>

<summary>Data flow fails with a "Blog not found" error</summary>

Double-check your Blog ID. The Blog ID is a numeric string — it's not the same as your blog's URL slug or custom domain. You can find it in the Blogger dashboard under **Settings > Basic**, or in the URL of your Blogger admin panel (look for the number following `blogID=`).

</details>

## Missing data

<details>

<summary>Draft posts are not appearing in the Posts entity</summary>

The Blogger API only returns published posts via a standard API key. Draft, scheduled, and private posts are not accessible through this authentication method. If you need draft data, you would require OAuth-based access, which is not currently supported for this source.

</details>

<details>

<summary>Comments are missing or incomplete</summary>

Comments are pulled at the blog level, not per post. If you're seeing fewer comments than expected, check whether some comments have a `status` of `spam` or `pending` — these may be filtered by the API. Also confirm you're using the correct Blog ID, not a post ID.

</details>

<details>

<summary>Labels (tags) are empty for some posts</summary>

Labels are optional in Blogger — if a post was published without any labels assigned, the `labels` field will be empty. This is expected behavior and not a sync error.

</details>

## Permission errors

<details>

<summary>API key works but returns a 403 Forbidden error</summary>

Your API key may have HTTP referrer or IP restrictions applied in the Google Cloud Console. Go to **APIs & Services > Credentials**, click your API key, and check the **Application restrictions** section. For use with Coupler.io, set restrictions to "None" or add Coupler.io's IP range if you want to keep restrictions in place.

</details>

## Data discrepancies

<details>

<summary>Comment count in Posts doesn't match the Comments entity</summary>

The `replies.totalItems` field in the Posts entity is a snapshot count from the post metadata. The Comments entity pulls individual comment records and may reflect a slightly different number depending on comment status (live vs. spam vs. pending). Use the Comments entity for the most accurate and filterable count.

</details>

## Rate limits

<details>

<summary>Sync fails or returns partial data during large exports</summary>

The Blogger API has a default quota of 10,000 requests per day per project. If you're pulling data from a high-volume blog with thousands of posts and comments, you may hit this limit. You can request a quota increase in the Google Cloud Console under **APIs & Services > Quotas**. For large blogs, consider running individual entity syncs rather than all entities at once.

</details>