Glossary
JSON object
A JSON object is a set of key and value pairs in braces, and it is the only body shape OneLifeVibe accepts: arrays, strings and null get refused.
Updated November 15, 2026
- Standard
- RFC 8259 (JSON)
- Also called
object literal
At OneLifeVibe
- Send Content-Type: application/json and a JSON object, for example {"arguments":{}} for a tool call.
- Send data as a JSON object, for example {"topic":"order.placed","data":{"order":"SC-1042"}}.
What it means
A JSON object is a set of key and value pairs wrapped in braces, as defined in RFC 8259. Each key is a string, a colon follows it, and then a value. Values can be strings, numbers, true or false, null, arrays, or other objects. That nesting is what makes objects useful: you can describe a structure, not just a single value.
The keys are unordered in the spec, so do not depend on the order they come back in. Duplicate keys are a bad idea too, because behavior varies between parsers. If you want a list of things, put an array inside an object, for example {"items":[{"id":"SC-1042"}]}. The top level stays an object.
How it works
You send an object as the body of an HTTP request with the Content-Type header set to application/json. The bytes on the wire are text, usually UTF-8, and the receiving side parses that text into its own types. A parser reads the opening brace, then key and value pairs separated by commas until the closing brace.
When parsing fails, you get an error rather than a partial read, so malformed JSON fails at the boundary. Escaping matters: double quotes and backslashes inside strings need a backslash in front, and control characters have to be escaped. HTTP status codes tell you where things broke. A 400 means the request itself was bad, which includes a body that is not a JSON object or does not parse. A 401 means the credentials were missing or wrong.
How OneLifeVibe uses it
Every request body across the OneLifeVibe developer platform and the assistant connector is a JSON object. Send Content-Type: application/json, then an object. The REST API takes objects too, for example an event body like {"topic":"order.placed","data":{"order":"SC-1042"}}.
When you call a tool through the connector, the request wraps the tool arguments in an object. A call with no arguments looks like {"arguments":{}}. The inner value is still an object, which keeps the shape predictable whether or not the tool takes parameters. Signed webhooks deliver payloads the same way, so the signature covers an object rather than a bare value.
The refusal is deliberate. Arrays, strings and null are not accepted as the body, even when they are valid JSON. If your data is naturally a list, wrap it: {"items":[...]}. That gives the platform a key to read and leaves room to add fields later without breaking the contract.
Common mistakes
The most frequent failure is sending a valid JSON array at the top level, such as [{"order":"SC-1042"}], and expecting it to work. It parses fine as JSON but is not an object, so it gets rejected. Wrap it under a key instead. The same applies to sending a bare string or null.
Not setting Content-Type: application/json is the next one. Some clients default to a form encoding, and then the bytes never reach the parser as JSON. Also check that you are sending the object as the body, not as a query parameter.
Two more to watch for: leaving a trailing comma before a closing brace, which strict parsers reject, and assuming key order is preserved. If you need a canonical form for signature checks, normalize it yourself instead of trusting the order of keys.
Questions
Does OneLifeVibe accept a JSON array as a request body?
No. The body must be a JSON object. Arrays, strings and null are refused, even when they are valid JSON. If you have a list, wrap it under a key inside an object.
What does a tool call with no arguments look like?
Send Content-Type: application/json with the object {"arguments":{}}. The arguments value is an empty object, which keeps the request shape the same as calls that do pass parameters.
See it working. The OneLifeVibe connector and Platform API put these pieces together.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.