Skip to content
Other

geneea.com

Geneea Natural Language Processing sandbox and mock API

<div class="api-description"> <h2>Authentication</h2> <p>For all calls, supply your API key. <a href="https://www.geneea.com/pricing">Sign up to <em>obtain the key</em></a>.</p> <p> Our API supports both <em>unencrypted (HTTP)</em> and <em>encrypted (HTTPS)</em> protocols. However, for security reasons, we strongly encourage using only the encrypted version. </p> <p>The API key should be supplied Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
12
Collections
-
Event types
-
example request
curl https://your-geneea.slurry.io/account \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.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

All 12.

  • GET/account
  • GET/s1/correction
  • POST/s1/correction
  • GET/s1/entities
  • POST/s1/entities
  • GET/s1/lemmatize
  • POST/s1/lemmatize
  • GET/s1/sentiment
  • POST/s1/sentiment
  • GET/s1/topic
  • POST/s1/topic
  • GET/status