To use the Blogs API from Toky, set up secure access with API keys or OAuth and assign the correct scope. Store credentials securely, rotate keys regularly, and use token-based authentication in all requests.
Toky authenticates to the Blogs API using approved credentials and scopes. Keep credentials in a secure vault and ensure only required permissions are granted for each workflow.
End points covered include: GET emails/builder, POST emails/builder, GET emails/schedule, GET /blogs/posts/url-slug-exists, POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/categories, GET /blogs/authors, GET /blogs/posts, POST /blogs/posts data, DELETE /emails/builder/:locationId/:templateId, and more. Use the endpoints that match your Toky workflow to create, update, and schedule content and emails.
Trigger: when a new subscriber is added in Toky, automatically fetch or create an email template using the Emails Builder.
Actions: GET emails/builder to retrieve templates, POST emails/builder to create or update, and POST emails/builder/data to attach data.
GET emails/builder
Key fields: builderId, templateId, recipientList
Trigger: schedule a campaign at a specific time
GET emails/schedule
scheduleId, sendTime, recipientGroup
Trigger: a new post draft is ready in Toky
POST /blogs/posts
postId, slug, title, content, authorId
Create automated workflows that publish posts and send email updates without writing code.
Coordinate content, comments, and schedules across Toky and Blogs API from a single interface.
Speed up publishing with instant triggers, reliable scheduling, and centralized data mapping.
Key elements include endpoints, authentication, triggers, actions, and data mapping used to connect Toky with Blogs API.
An interface that lets Toky talk to the Blogs API to request data or perform actions.
A specific URL path in the Blogs API that performs a defined action.
A callback URL that Toky can receive when events occur in the Blogs API.
A URL friendly identifier for a blog post used in permalinks.
Pull new posts from Blogs API and send a weekly digest via Toky emails.
Create posts automatically when a trigger occurs in Toky and publish via Blogs API.
Map slug values and metadata to ensure SEO friendly posts.
Obtain Blogs API credentials and securely store them in Toky. Authorize the connection with the correct scopes.
Choose the endpoints you will use and map Toky fields to the Blogs API data fields for seamless data flow.
Run tests, verify data integrity, and deploy the integration to production with monitoring.
The Blogs API lets Toky interact with blog content and email assets without manual file transfers. It enables automated publishing, scheduling, and retrieval of templates. This makes content workflows faster and reduces repetitive tasks. You can mix blog post actions with email campaigns to create cohesive content experiences. The integration supports scalable automation for growing audiences.
Authenticate using API keys or OAuth with the appropriate scopes. Store credentials securely, rotate keys regularly, and renew tokens before they expire. In Toky, reference the credentials in a secure vault and attach them to the specific workflows that need access to the Blogs API.
The most useful endpoints for publishing are POST /blogs/posts to create posts, PUT /blogs/posts/:postId to update, and GET /blogs/posts/url-slug-exists to ensure unique slugs. For content scheduling, GET emails/schedule and POST /emails/schedule help automate timing. Combined, these endpoints let you publish, modify, and time content release.
No code is required if you use the built-in Toky workflows and the provided endpoints. You can configure triggers, actions and data mappings visually in Toky and let the integration handle the API calls. Some basic data field mapping is helpful but you don’t need custom code.
Yes. You can schedule posts and emails by using the schedule endpoints. Create a schedule resource with a send time for emails and a publish time for blog posts, then link those resources to your Toky automations.
GET retrieves information, POST creates new resources, and PUT updates existing ones. In this integration, you typically GET templates or posts for review, POST new posts or template data to create content, and PUT to modify existing posts or templates.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
