Use OAuth or API keys to securely authorize Nearby Now to access your Blogs API data and endpoints.
Grant Nearby Now the required scopes to interact with Blogs API endpoints and retrieve blog data in real time.
Core endpoints include GET, POST, PUT, and DELETE calls for blogs and emails; below are the primary endpoints used to connect Blogs API with Nearby Now.
When a new blog post is published in Blogs API, Nearby Now can automatically create or update related content and notify your team.
Actions: create a Nearby Now entry, route a notification, and schedule a social post.
POST /blogs/posts
title, slug, content, author, categories, publishDate
Trigger fires when a blog post is updated in Blogs API.
Actions: refresh Nearby Now post data, update metadata, and trigger downstream workflows.
PUT /blogs/posts/:postId
postId, title, slug, status, updatedAt
Trigger to verify or fetch a blog post URL/slug in a reliable way.
Actions: retrieve post data by slug, sync into Nearby Now, and cache results.
GET /blogs/posts/url-slug-exists
slug, exists, postId, url
Drag-and-drop automations let you build powerful workflows without writing code.
No server changes needed—simply connect via APIs and start automating.
Real-time data syncing keeps content accurate across platforms.
Understand common terms like endpoint, trigger, action, and slug to navigate the Blogs API + Nearby Now integration.
Sends data to create a new resource on the server.
Retrieves data from the server without modifying it.
Updates an existing resource on the server.
A URL-friendly string used to identify a post in links and requests.
Automatically post new blog launches to Nearby Now channels and subscribers.
Sync blog updates to social, email, and site content from Blogs API.
Automatically adjust metadata and slugs for better search visibility.
Authorize Nearby Now to access Blogs API data securely.
Select core endpoints like GET /blogs/posts, POST /blogs/posts, and GET /blogs/posts/url-slug-exists.
Test integrations, verify data sync, and enable live mode for customers.
Blogs API supports API key and OAuth 2.0 for authentication. Nearby Now can securely store and refresh tokens, and use scoped access to protect data. If a token expires, the app will automatically request a new one or prompt you to re-authenticate.
Key endpoints include GET /blogs/posts, POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/posts/url-slug-exists, and GET /blogs/categories. These endpoints are used to read, create, update, and verify blog data as part of the Nearby Now workflow.
You can verify a slug by calling GET /blogs/posts/url-slug-exists. If the slug exists, you will get a response indicating its presence. If not, you can create a new post with a unique slug.
Yes. You can set up triggers and actions in the builder to automate responses based on blog events. No-code automation allows you to connect events to Nearby Now workflows.
The integration includes error handling with retries and status checks. You can view logs in the app to diagnose failures and retry failed tasks automatically or manually.
Rate limits apply per API key and endpoint. If you hit a limit, implement exponential backoff and queue requests to maintain smooth operations.
Docs are available within the Blogs API developer portal and in the integration section of the Nearby Now docs. You can also contact support for detailed guidance.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
