Skip to content
Communication/messaging

ritekit.com

RiteKit sandbox and mock API

RiteKit API is based on REST principles. Authentication uses standard OAuth 2.0 process ##Getting started 1. Sign up for [RiteKit](https://ritekit.com/) 1. Go to [developer dashboard](https://ritekit.com/developer/dashboard/) 1. Click "Create a token" button to get your **Client ID** and **Client secret** 1. When you reach your free limit of calls per month, [upgrade to paid tiers](https://ritekit Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
13
Collections
-
Event types
-
Start this simulation
example request
curl https://your-ritekit.slurry.io/v1/emoji/auto-emojify \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.0.0.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 13.

  • GET/v1/emoji/auto-emojify
  • GET/v1/emoji/suggestions
  • GET/v1/images/animate
  • GET/v1/images/logo
  • GET/v1/images/quote
  • GET/v1/link/cta
  • GET/v1/link/short-link
  • GET/v1/search/trending
  • GET/v1/stats/auto-hashtag
  • GET/v1/stats/hashtag-suggestions
  • GET/v1/stats/history/{hashtag}
  • GET/v1/stats/multiple-hashtags