Authenticate requests from Lexware Office using the Blogs API credentials provided by your Blogs API account (API key or OAuth).
Lexware Office securely stores and rotates its access tokens when connecting to Blogs API, ensuring only approved requests are sent.
– GET /blogs/posts – List posts – POST /blogs/posts – Create a post – PUT /blogs/posts/:postId – Update a post – GET /blogs/categories – List categories – GET /blogs/authors – List authors – GET /blogs/posts/url-slug-exists – Check if a slug exists – POST /blogs/posts – Create a post (alternative entry point) (Note: These are the endpoints most relevant to connecting Lexware Office with the Blogs API endpoints. Other endpoints may be used as needed.)
When a new draft is saved in Lexware Office, automatically publish it to Blogs API using POST /blogs/posts.
Actions: map Lexware Office fields to blog post fields, call POST /blogs/posts, and confirm creation; store the returned postId for future updates.
POST /blogs/posts
title, content, slug, excerpt, author, categories
Daily or interval-based sync to publish queued Lexware Office posts to Blogs API.
Actions: fetch queued drafts, publish via POST /blogs/posts, then update status with PUT /blogs/posts/:postId.
POST /blogs/posts
title, content, slug, status
On-demand sync to fetch metadata such as categories and authors before posting.
Actions: GET /blogs/categories, GET /blogs/authors, and validate slug with GET /blogs/posts/url-slug-exists before publishing.
GET /blogs/categories
category_id, name, author_id, name
No-code integration lets your teams publish professional blog content without developers.
Centralized publishing controls and scheduling from Lexware Office.
Faster go-to-market with SEO-friendly slugs and rich metadata.
A quick reference to data elements and typical workflows used when connecting Blogs API with Lexware Office.
A set of endpoints that let Lexware Office talk to Blogs API to perform actions like create, update, and fetch posts.
A URL-friendly version of the post title used in the post URL.
A specific URL and HTTP method provided by an API to perform an action.
A notification mechanism that triggers actions when content changes in either system.
Automatically compile and publish a weekly digest from Lexware Office drafts to Blogs API.
Publish release notes or product updates when Lexware Office records change.
Create blog posts for upcoming events by syncing Lexware Office events to Blogs API.
Obtain Blogs API credentials and configure them in Lexware Office.
Map Lexware Office fields to Blogs API post fields and endpoints you plan to use.
Run a test post and verify it appears in Blogs API.
No code is required for this integration. The Lexware Office to Blogs API connectors handle the data flow and API calls for you. If you need a custom flow later, you can extend with additional fields or triggers as needed. If you ever need more advanced automation, you can layer in webhooks or external automation tools to expand capabilities.
Yes. You can schedule posts to publish automatically at a defined time or interval. Use Lexware Office scheduling to trigger POST /blogs/posts at the desired cadence and keep your blog current.
Key endpoints include GET /blogs/posts, POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/categories, GET /blogs/authors, and GET /blogs/posts/url-slug-exists. These cover creation, updates, and metadata management for your blog content.
To avoid duplicates, validate the slug with GET /blogs/posts/url-slug-exists before publishing. If the slug exists, modify it or append a unique suffix to ensure a unique URL.
Authentication is handled via Blogs API credentials (API key or OAuth) configured in Lexware Office. Tokens are stored securely and rotated as needed to keep connections safe.
Yes. You can fetch authors and categories using GET /blogs/authors and GET /blogs/categories to populate fields, filters, and metadata in Lexware Office.
Support is available via your Blogs API and Lexware Office integration resources, including documentation, community forums, and dedicated support channels from Rankr. If you need tailored assistance, contact our support team.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
