Blogger is Google's free blog-publishing platform that allows users to create and manage personal or business blogs hosted on Google's infrastructure. The Blogger API v3 exposes the platform's five core resources — Blogs, Posts, Pages, Comments, and Users — over a REST interface, enabling integrations to programmatically read and write blog content, manage pages, moderate comments, retrieve page-view statistics, and look up user and blog metadata.
Power end-to-end data operations for your Blogger API with Nexla. Our bi-directional Blogger connector is purpose-built for Blogger, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Blogger or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Blogger workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
The Blogger API v3 uses Google's OAuth 2.0 implementation for authentication. To create a Blogger credential in Nexla, you must first register an OAuth 2.0 client application in the Google Cloud Console, enable the Blogger API on the same project, and configure the OAuth consent screen. The steps below walk through the full process.
Sign in to the Google Cloud Console with the Google account that will own the OAuth application.
In the project selector at the top of the console, click Select a project, then click New Project.
Enter a descriptive name in the Project name field (for example, Nexla Blogger Integration), select an organization and billing account if applicable, and click Create.
Once the project is created, ensure it is selected in the project selector before continuing.
The OAuth consent screen is what Blogger users see when authorizing your application. It must be configured before client IDs can be created.
In the Google Cloud Console, open APIs & Services > OAuth consent screen.
Select the User Type that matches your use case:
Internal: Only available for Google Workspace organizations. Restricts access to users within the same organization and skips Google's app verification process.
External: Required for any application that will be authorized by users outside your Workspace organization (or for personal Google accounts). Applications using sensitive scopes may need to complete Google's verification process before being published.
Click Create, and complete the App information fields. At minimum, enter an App name, a User support email, and a Developer contact email. Save and continue.
On the Scopes step, click Add or Remove Scopes, and add one of the following Blogger scopes:
https://www.googleapis.com/auth/blogger — Full read and write access to manage the user's Blogger account. Required for any destination flow (create, update, delete, publish, moderate comments).
https://www.googleapis.com/auth/blogger.readonly — Read-only access to the user's Blogger account. Sufficient for source-only flows that ingest blog, post, page, comment, or page-view data.
On the Test users step, add the Google accounts that will be used to authorize the application during development. While the app is in Testing mode, only listed test users can complete the consent flow.
Review the summary, and save the consent screen configuration.
In the Google Cloud Console, open APIs & Services > Credentials.
Click Create Credentials, and select OAuth client ID.
From the Application type pulldown menu, select Web application. This is the correct type for the server-side authorization-code flow that Nexla uses.
Enter a descriptive name in the Name field (for example, Nexla Blogger OAuth Client).
Under Authorized redirect URIs, click Add URI, and paste the Nexla OAuth callback URL shown in the Nexla credential overlay when you select the OAuth 2.0 authentication method. The redirect URI registered with Google must match the one used during the authorization flow exactly, including protocol and trailing slash.
Click Create. Google displays the Client ID and Client secret for the new credential.
Copy and store both the Client ID and Client secret securely. The Client secret can be retrieved again later from the Credentials page, but it should be treated as a password.
Important
The Client secret grants the ability to obtain access tokens on behalf of consenting users. Store it in a secure secret manager, never commit it to source control, and rotate it immediately if you suspect it has been exposed.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Blogger credentials use Google's three-legged OAuth 2.0 flow. The Blogger user being connected signs in to Google directly and approves access for your registered OAuth application — your Client Secret is never shared with the end user.
Enter the Client ID issued for your registered Google OAuth application in the Client ID field. This value is found on the APIs & Services > Credentials page in the Google Cloud Console.
Enter the Client Secret issued for the same OAuth application in the Client Secret field. This value is treated as a secret and is shown alongside the Client ID on the Credentials page.
Confirm that the Authorization URL field is set to https://accounts.google.com/o/oauth2/v2/auth. This is Google's standard OAuth 2.0 authorization endpoint and is shared by all Google APIs.
Confirm that the Token URL field is set to https://oauth2.googleapis.com/token. This is Google's standard OAuth 2.0 token endpoint where Nexla exchanges the authorization code for an access token and refresh token.
Confirm that the Access Scope field contains the appropriate Blogger scope for your use case:
Enter https://www.googleapis.com/auth/blogger for read and write access. Use this scope for any destination flow that creates, updates, deletes, publishes, or moderates Blogger content.
Enter https://www.googleapis.com/auth/blogger.readonly for read-only access. Use this scope for source-only flows that only ingest Blogger data.
The scopes requested here must be a subset of the scopes configured on the OAuth consent screen in the Google Cloud Console. If a scope is missing from the consent screen, Google will reject the authorization request.
Click Authorize to launch the Google consent screen. Sign in to the Google account that owns (or has access to) the Blogger blogs that will be connected, and approve the requested access.
After the consent screen is approved, Google redirects back to Nexla with an authorization code. Nexla automatically exchanges this code for an access token and refresh token using the Token URL, and stores the resulting tokens on the credential. Nexla will use the refresh token to silently obtain new access tokens as needed, so the user does not need to re-authorize unless access is revoked.
Click the Save button at the bottom of the overlay to save the configured credential. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Blogger connector tile from the list of available connectors, then select the credential that will be used to connect to the Blogger instance, and click Next; or, create a new Blogger credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Blogger endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
List User Blogs
This endpoint returns the list of blogs owned by the authenticated user (the user who authorized the OAuth credential). Use it as a discovery step to obtain blog IDs that are required by every other Blogger endpoint.
No configuration is required for this endpoint beyond selecting it. Blogger automatically returns all blogs accessible to the authenticated user via the /users/self/blogs route.
Each entry in the returned items array contains the blog's numeric id, name, description, url, post counts, and locale metadata.
Blog IDs from this endpoint are required by virtually every other Blogger endpoint — including Get Blog by ID, List Posts, List Pages, List Comments by Blog, and all destination endpoints. Run this source first when bootstrapping a new Blogger integration.
List Blogs by User
This endpoint returns the list of blogs owned by, or accessible to, a specific Blogger user. Use it when the authenticated OAuth user has access to multiple Blogger user accounts (for example, when authoring across team accounts) and you need to enumerate blogs for a user other than self.
Enter the Blogger user ID in the User Id field. Use the literal value self to refer to the authenticated user, or a numeric user ID obtained from the Get User endpoint or from the author.id attribute of a previously fetched post.
This endpoint retrieves the full metadata for a single blog by its numeric ID, including the blog name, description, URL, locale, and post and page counts. Use it to enrich a dataset of blog IDs with the latest blog-level details.
Enter the numeric blog ID in the Blog ID field. This field is required. Blog IDs can be obtained from the List User Blogs endpoint.
Leave the $.Xgafv field blank in normal usage. This is Google's standard v1/v2 error-format query parameter and is not required for typical Blogger calls.
Get Blog by URL
This endpoint retrieves a blog by its public URL rather than by numeric ID. Use it to look up the blog ID and metadata when you only have the blog's address — for example, when integrating with a marketing dataset that stores blog URLs.
Enter the full blog URL (including https://) in the Blog URL field. This field is required. Example: https://buzz.blogger.com/.
Optionally, enter a view filter in the View field to control which fields are returned: ADMIN for full admin-level detail, AUTHOR for the author's view, or READER for the public view.
Get Blog User Info
This endpoint retrieves per-user metadata for a specific blog — including the user's role on the blog and their permissions — combined with the blog's own metadata. Use it to verify access rights or to inspect role assignments programmatically.
Enter the user ID in the User Id field. Use self for the authenticated user, or a numeric user ID from the Get User endpoint.
Enter the numeric blog ID in the Blog Id field.
Optionally, enter the maximum number of recent posts to include in the response in the Max Posts field. Leaving this blank returns only blog-user metadata without inline posts.
Get Page Views
This endpoint returns page-view statistics for a blog over a specified time window. Use it to feed Blogger traffic data into a warehouse, BI tool, or marketing dashboard alongside content data from List Posts.
Enter the numeric blog ID in the Blog Id field. This field is required.
Optionally, enter a time window in the Range field. Supported values include 30DAYS, 7DAYS, and all for the lifetime total. The parameter can be repeated to fetch multiple ranges in a single call.
Page-view counts returned by this endpoint represent the total across all posts and pages on the blog for the selected range. To analyze traffic by post, pair this endpoint with List Posts in a separate flow.
List Posts
This endpoint returns a paginated list of posts from a blog. Use it as the primary content-sync endpoint for ingesting Blogger posts into a warehouse, content management system, or analytics platform. Pagination is handled automatically by Nexla using Blogger's nextPageToken.
Enter the numeric blog ID in the Blog Id field. This field is required.
Optionally, enter a maximum result count in the Max Results field. Blogger caps this at 500 per page.
Set the Fetch Bodies field to true to include the full HTML body of each post, or false to return only metadata. Omitting bodies dramatically reduces payload size for large catalogs.
Set the Fetch Images field to true to include image metadata extracted from each post's body.
To restrict the date window, enter ISO 8601 timestamps (for example, 2026-01-01T00:00:00-00:00) in the Start Date and End Date fields. The Nexla {now} and {now-1} macros can be used here for incremental ingestion.
To filter by post status, enter one of LIVE, DRAFT, SCHEDULED, or SOFT_TRASHED in the Status field. The parameter can be repeated to request multiple statuses.
To restrict results to specific labels, enter a comma-separated list of labels in the Labels field.
To sort the result set, enter published or updated in the Order By field.
To switch between admin and public views, enter ADMIN, AUTHOR, or READER in the View field. READER only returns posts visible to the public; ADMIN requires admin role on the blog.
Combine Start Date set to {now-1} (with the Time Unit for Operations set to Day) and a scheduled cron in the Nexla flow to ingest only posts published since the last run.
Get a Post
This endpoint retrieves a single post by ID, including its full body, labels, and metadata. Use it to enrich an existing dataset of post IDs with the latest content, or to drive downstream workflows that operate on individual posts.
Enter the numeric blog ID in the Blog Id field. This field is required.
Enter the numeric post ID in the Post Id field. This field is required. Post IDs can be obtained from the List Posts endpoint.
Set the Fetch Body field to true to include the full HTML body of the post, or false to omit it.
Set the Fetch Images field to true to include image metadata extracted from the post body.
Optionally, enter a value in the Max Comments field to include up to that many of the most recent comments inline with the post.
Optionally, enter ADMIN or READER in the View field. ADMIN includes draft and scheduled posts and requires admin access; READER returns the public view only.
Get Post by Path
This endpoint retrieves a post by its URL path (the portion of the post URL after the blog's domain) rather than by numeric post ID. Use it when integrating with marketing or analytics data that references posts by their slug.
Enter the numeric blog ID in the Blog Id field. This field is required.
Enter the relative URL path of the post in the Path field. The path begins with a forward slash and matches the format Blogger uses for permalinks (for example, /2026/03/my-post.html). This field is required.
Optionally, enter a value in the Max Comments field to include recent comments inline with the post.
Optionally, enter ADMIN or READER in the View field to control which fields are returned.
Search Posts
This endpoint searches for posts on a blog using a free-text query, returning posts whose title or body match the query. Use it to build content-search integrations or to surface relevant Blogger content in a downstream knowledge base.
Enter the numeric blog ID in the Blog Id field. This field is required.
Enter the search query in the Q field. This field is required. Multi-word queries are matched against the post title and body.
To control the sort order of matched posts, enter published or updated in the Order By field. The default is published (most recent first).
Optionally, enter true in the Fetch Bodies field to include full post bodies in the response.
Search uses Blogger's built-in indexing and only returns published posts visible to readers; it does not match drafts or scheduled posts.
List Post User Infos
This endpoint returns posts on a blog combined with per-user metadata (for example, the requesting user's role on each post) for a specified Blogger user. Use it to drive author-specific dashboards or to enumerate posts that a particular user has rights to edit.
Enter the user ID in the User Id field. Use self for the authenticated user.
Enter the numeric blog ID in the Blog Id field. This field is required.
Optionally, enter a maximum result count in the Max Results field. Pagination is handled automatically by Nexla.
Set the Fetch Bodies field to true to include full post bodies, or false to return only metadata.
To restrict the date window, enter ISO 8601 timestamps in the Start Date and End Date fields.
To filter by labels, enter a comma-separated list in the Labels field.
To filter by status, enter LIVE, DRAFT, SCHEDULED, or SOFT_TRASHED in the Status field. The parameter can be repeated to request multiple statuses.
To control sort order, enter published or updated in the Order By field.
To switch between admin and public views, enter ADMIN or READER in the View field.
List Pages
This endpoint returns a paginated list of static pages on a blog. Pages on Blogger are evergreen content (such as "About" or "Contact"), distinct from posts. Pagination is handled automatically by Nexla using Blogger's nextPageToken.
Enter the numeric blog ID in the Blog Id field. This field is required.
Optionally, enter a maximum result count in the Max Results field.
Set the Fetch Bodies field to true to include the full HTML body of each page.
To filter by status, enter LIVE, DRAFT, or SOFT_TRASHED in the Status field. The parameter can be repeated to request multiple statuses.
To switch between admin and public views, enter ADMIN, AUTHOR, or READER in the View field.
Get Page by ID
This endpoint retrieves a single page by blog ID and page ID, returning the page's full HTML body and metadata. Use it to fetch the latest version of a specific static page for a downstream site or CMS.
Enter the numeric blog ID in the Blog ID field. This field is required.
Enter the numeric page ID in the Page ID field. This field is required. Page IDs can be obtained from the List Pages endpoint.
List Comments by Blog
This endpoint returns a paginated list of all comments on a blog, across all posts. Use it for blog-wide comment moderation or to feed comment data into a sentiment-analysis or community-management pipeline. Pagination is handled automatically by Nexla.
Enter the numeric blog ID in the Blog Id field.
To restrict the date window, enter ISO 3339 (RFC 3339) timestamps in the Start Date and End Date fields. The Nexla {now} and {now-1} macros can be used here for incremental ingestion.
Set the Fetch Bodies field to true to include the full comment text, or false to return only metadata.
Optionally, enter a maximum result count in the Max Results field.
To filter by moderation status, enter live, pending, spam, or emptied in the Status field.
The Page Token field is managed automatically by Nexla pagination and does not normally need to be set manually.
List Comments
This endpoint returns the comments attached to a specific post. Use it when ingesting comments tied to a known set of posts — for example, syncing the discussion on a recent campaign post into a CRM or community tool.
Enter the numeric blog ID in the Blog Id field. This field is required.
Enter the numeric post ID in the Post Id field. This field is required.
To restrict the date window, enter RFC 3339 timestamps in the Start Date and End Date fields.
Set the Fetch Bodies field to true to include the full comment text.
Optionally, enter a maximum result count in the Max Results field.
To filter by moderation status, enter live, pending, spam, or emptied in the Status field.
To switch between admin and public views, enter ADMIN or READER in the View field. ADMIN returns pending and spam comments; READER returns only live comments.
Get User
This endpoint retrieves a Blogger user profile, including the user's display name, locale, and account creation timestamp. Use it to enrich a dataset of user IDs with profile metadata, or to look up the authenticated user via self.
Enter the user ID in the User ID field. Use self for the authenticated user, or a numeric user ID. This field is required.
Leave the $.Xgafv field blank in normal usage.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Blogger data sources can also be manually configured to ingest data from any valid Blogger API endpoint, including endpoints not covered by the pre-built templates or chained calls across multiple endpoints (for example, listing posts and then fetching comments for each post). Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
All Blogger v3 endpoints use the base URL https://blogger.googleapis.com/v3/ followed by the resource path — for example, https://blogger.googleapis.com/v3/users/self/blogs to list the authenticated user's blogs, or https://blogger.googleapis.com/v3/blogs/{blog_id}/posts to list posts.
Blogger list endpoints (such as /posts, /pages, /comments, and /users/self/blogs) return an items array, so the path to data is $.items[*]; endpoints that return a single object (such as /blogs/{blog_id}) use $. The kind, nextPageToken, and etag fields are returned as siblings of the items array and can be captured as record metadata. The startDate and endDate parameters expect RFC 3339 timestamps, so choose a date format that emits a full RFC 3339 timestamp when using date/time macros.
You do not need to add an authorization header — the Authorization: Bearer ... header is added automatically from your Blogger OAuth credential.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Blogger data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Blogger destination, and select the Send to Destination option from the menu. Select the Blogger connector from the list of available destination connectors, then select the credential that will be used to connect to the Blogger account, and click Next; or, create a new Blogger credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Blogger endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Create a Post
This endpoint creates a new post on a Blogger blog. Use it to programmatically publish content authored in an upstream CMS, marketing tool, or AI pipeline directly to Blogger.
Enter the numeric blog ID in the Blog Id field. This identifies which blog the post will be created on.
Each record in the upstream Nexset must include at least a title field and a content field (the HTML body). Optional fields supported by Blogger include labels (an array of tag strings), customMetaData, and location for geotagged posts.
The full record is sent as the JSON body of the POST /blogs/{blog_id}/posts call. Use the Nexla transform layer to shape upstream attributes into the field names expected by Blogger.
Set the Is Draft field to true to save the post as a draft instead of publishing immediately. Drafts can later be published via the Publish Post endpoint.
Set the Fetch Body field to true to have Blogger return the full post body in the API response, and Fetch Images to true to include image metadata.
This endpoint replaces an existing post with the full contents of the request body. Use it when the upstream system always provides a complete representation of the post — for example, when re-publishing content from a CMS that maintains canonical state.
Enter the numeric blog ID in the Blog Id field, and the numeric post ID in the Post Id field. Post IDs can be obtained from the List Posts source endpoint.
The body of each PUT call is the full post payload, including title, content, and any optional fields such as labels. Fields omitted from the body will be cleared on the post.
Optionally, set the Revert field to true to revert the post to an earlier saved version, or Publish to true to publish the updated post immediately.
Use Partially Update a Post instead when the upstream Nexset only carries the fields that should change.
Partially Update a Post
This endpoint applies a partial update to an existing post — only the fields present in the request body are modified, leaving all other fields untouched. Use it for incremental edits, such as updating only the labels or the title.
Enter the numeric blog ID in the Blog Id field, and the numeric post ID in the Post Id field.
The body of each PATCH call should contain only the attributes that should change (for example, {"title": "New title"} to rename a post). Use the Nexla transform layer to limit the outgoing record to the fields being updated.
Delete Post
This endpoint permanently deletes a post by blog ID and post ID. The deletion is irreversible from the API.
Enter the numeric blog ID in the Blog ID field. This field is required.
Enter the numeric post ID in the Post ID field. This field is required. Post IDs can be obtained from the List Posts source endpoint.
Because deletion is irreversible, validate upstream data carefully before activating this destination. Consider routing through a Nexla transform that filters to only the posts that should genuinely be deleted.
Publish Post
This endpoint publishes a draft post or schedules a post for future publication. Use it as a follow-up to Create a Post (when Is Draft was set to true) or to release content on a publication calendar.
Enter the numeric blog ID in the Blog Id field, and the numeric post ID in the Post Id field.
Optionally, enter a future timestamp in RFC 3339 format (for example, 2026-07-01T09:00:00-00:00) in the Publish Date field to schedule the post for that time. If left blank, the post is published immediately.
Revert Post to Draft
This endpoint reverts a published or scheduled post back to draft state, removing it from public view without deleting the content. Use it to unpublish content that needs to be edited before re-release.
Enter the numeric blog ID in the Blog Id field, and the numeric post ID in the Post Id field.
A reverted post can be re-published later via the Publish Post endpoint with no data loss.
Create Page
This endpoint creates a new static page on a Blogger blog. Pages are evergreen content (such as "About" or "Contact" pages), distinct from posts. Use it to provision standard pages programmatically when setting up new blogs.
Enter the numeric blog ID in the Blog Id field. This field is required.
Each record in the upstream Nexset must include a title field and a content field (the HTML body) at a minimum.
Set the Is Draft field to true to save the page as a draft, or leave it blank to publish immediately.
Update Page
This endpoint replaces an existing static page with the full contents of the request body. Use it when the upstream system maintains canonical page content and re-syncs the full page each run.
Enter the numeric blog ID in the Blog Id field, and the numeric page ID in the Page Id field. Page IDs can be obtained from the List Pages source endpoint.
The body of each PUT call should contain the full page payload — including title and content. Fields omitted from the body will be cleared.
Optionally, set the Publish field to true to ensure the updated page is published, or Revert to true to revert the page to draft.
Use Patch Page instead when the upstream Nexset only carries the fields that should change.
Patch Page
This endpoint applies a partial update to an existing page — only the fields present in the request body are modified. Use it for incremental edits to a static page (for example, updating only the body content while leaving the title intact).
Enter the numeric blog ID in the Blog Id field, and the numeric page ID in the Page Id field.
The body of each PATCH call should contain only the attributes that should change. Use the Nexla transform layer to limit the outgoing record to the fields being updated.
Delete Page
This endpoint permanently deletes a page by blog ID and page ID. The deletion is irreversible from the API.
Enter the numeric blog ID in the Blog ID field. This field is required.
Enter the numeric page ID in the Page ID field. This field is required.
Because deletion is irreversible, validate upstream data carefully before activating this destination.
Approve Comment
This endpoint approves a pending comment, making it publicly visible on the post. Use it to integrate Blogger comment moderation with an upstream review queue or automated moderation tool.
Enter the numeric blog ID in the Blogid field, the post ID in the Postid field, and the comment ID in the Commentid field. All three identify which comment to approve.
Comment IDs can be obtained from the List Comments by Blog or List Comments source endpoints, filtered to Status = pending.
This endpoint expects a POST with an empty (or empty-JSON) body. The Nexla template defaults the body to the upstream record as JSON; in most cases the request body is ignored by Blogger for this action.
Mark Comment as Spam
This endpoint marks a comment as spam, removing it from public view and adding it to the blog's spam list. Use it to integrate automated spam detection or moderator decisions back into Blogger.
Enter the numeric blog ID, post ID, and comment ID in the corresponding Blog ID, Post ID, and Comment ID fields.
Delete Comment
This endpoint permanently deletes a comment by blog ID, post ID, and comment ID. The deletion is irreversible from the API.
Enter the numeric blog ID in the Blog ID field, the post ID in the Post ID field, and the comment ID in the Comment ID field. All three are required.
Use Mark Comment as Spam instead when the comment should be hidden but not permanently destroyed — spam comments can be reviewed and restored later, while deleted comments cannot.
Once the selected endpoint template has been configured, click the Test button at the top of the Sample Payload panel, and expand a listed sample payload to verify that the destination is configured correctly before saving.
Blogger destinations can also be manually configured to send data to any valid Blogger API endpoint, including endpoints not covered by the pre-built templates, custom URL patterns, or query parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
All Blogger v3 endpoints use the base URL https://blogger.googleapis.com/v3/ followed by the resource path, and expect application/json for all write operations. For update, delete, or state-change operations, include the blog ID and resource ID at the end of the URL — Nexla macros can substitute IDs from each upstream record (for example, https://blogger.googleapis.com/v3/blogs/{blog_id}/posts/{id}). The Authorization: Bearer ... header is added automatically from your Blogger OAuth credential.
The Blogger v3 REST endpoints accept one resource per request (one post, one page, or one comment action), so record batching is typically not appropriate — leave it disabled unless you are targeting a custom proxy that accepts arrays of Blogger payloads. Optionally, enable the response webhook to capture the response from each call (for example, the newly assigned post ID returned by Create a Post) as a new Nexla webhook data source.
Important
Test payloads are sent against the real Blogger account associated with the selected credential. To avoid accidentally publishing test content to a production blog, point the destination at a sandbox blog (or use the Is Draft flag where supported) when running tests.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Blogger endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to Blogger until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
