Use an API token to authorize requests to the Blogs API endpoints such as GET emails/builder and POST blogs/posts. Keep tokens secure and rotate them every 90 days.
Referral Rock connections use an API token for server-to-server calls. Store the token in a secure vault and attach it to requests that create or update referrals, campaigns, and blog-related data.
Key endpoints include: GET emails/builder, GET /blogs/posts, POST /blogs/posts, GET /blogs/posts/url-slug-exists, PUT /blogs/posts/:postId, GET /blogs/categories, GET /blogs/authors, and more to support content-to-referral workflows.
Trigger: A new blog post is published in Blogs API.
Actions: Create or update a referral campaign in Referral Rock and tag posts for tracking.
POST /blogs/posts
postId, title, slug, author, publishDate, referralCampaignId
Trigger: A scheduled job runs to fetch recent blogs from Blogs API.
Actions: Sync posts into Referral Rock campaigns and update campaign content.
GET /blogs/posts
postId, title, summary, publishDate, campaignId
Trigger: An existing blog post is updated in Blogs API.
Actions: Update Referral Rock items, refresh slug mappings, and notify teams.
PUT /blogs/posts/:postId
postId, slug, title, updatedAt
No custom development is required: both systems expose endpoints you can connect through a visual automation builder.
Consistent data across platforms reduces manual data entry and errors.
Scales with your content strategy as you publish more posts and run more campaigns.
Understand the core terms used in this integration, including endpoints, triggers, actions, and data fields, so you can map data accurately between Blogs API and Referral Rock.
Application Programming Interface: a defined set of rules that lets different software systems talk to each other.
An event that starts an automation or workflow in your integration, such as a new blog post published.
A specific URL path on an API that performs a function, like POST /blogs/posts or GET /blogs/posts.
A URL-friendly version of a post title used for routing and sharing links, e.g., my-post-title
Automatically start a referral campaign whenever a new post is published in Blogs API, increasing reach and engagement.
Push a weekly or monthly blog digest into Referral Rock to nurture leads without manual newsletters.
Segment campaigns by author or category and tailor referrals to reader interests.
Obtain API tokens for Blogs API and Referral Rock, and secure storage.
Choose endpoints such as POST /blogs/posts and GET /blogs/posts to sync content.
Set up triggers, actions, and data mappings to automate post and referral data flow.
Yes, the integration uses standard HTTPS with token-based authentication and least-privilege scopes. Use API tokens from both services and rotate them regularly. Enable monitoring and alerts for failures to keep data secure. In practice, this means all requests are signed and transmitted over TLS, minimizing risk.
Absolutely. You can map fields like title, slug, publishDate, author, and category to corresponding Referral Rock fields. If a field isn’t present by default, you can skip it or use a custom field in Referral Rock. This keeps data clean and aligned.
The essential endpoints depend on your use case, but a typical starter set includes POST /blogs/posts to push new content, GET /blogs/posts to pull posts, GET /blogs/posts/url-slug-exists to validate slugs, and PUT /blogs/posts/:postId to update. Also consider GET /blogs/categories and GET /blogs/authors for richer mappings.
No coding is required if you’re using a no-code automation builder or integration platform that supports REST. You will configure triggers, actions, and mappings visually. Some basic JSON field mapping is helpful but not necessary for most setups.
Sync frequency is configurable. You can run real-time webhooks where supported or schedule periodic pulls every few hours. Plan around your content cadence to avoid rate limits and ensure timely updates.
Yes. Use a sandbox or test environment to simulate posts and referrals. Verify mappings, test end-to-end flows, and check error handling before going live. Most platforms offer a test trigger or a mock post.
When an error occurs, check the API response for status codes and error messages. Implement retries with exponential backoff and notify your team. Most integrations log failures and provide a retry dashboard.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
