Skip to content
CRM

journy.io

Developer documentation sandbox and mock API

# Welcome Implementing a new tool can be daunting, but it doesn't have to. You can implement journy.io in a few different ways to ensure it fits with the rest of your tech stack seamlessly. We welcome your feedback, ideas and suggestions. We really want to make your life easier, so if we’re falling short or should be doing something different, we want to hear about it. Send us an email at [hi@jour Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
16
Collections
-
Event types
-
Start this simulation
example request
curl https://your-journy.slurry.io/events \
  -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 16.

  • DELETE/accounts
  • POST/accounts/upsert
  • POST/accounts/users/add
  • POST/accounts/users/remove
  • GET/events
  • POST/events
  • POST/link
  • GET/properties/accounts
  • GET/properties/users
  • GET/segments/accounts
  • GET/segments/users
  • POST/track