[#RPCArg-Type]
= xref:RPCArg.adoc[RPCArg]::Type
:relfileprefix: ../
:mrdocs:

The JSON type expected for the argument&period;

== Synopsis

Declared in `&lt;rpc&sol;util&period;h&gt;`

[source,cpp,subs="verbatim,replacements,macros,-callouts"]
----
enum class Type : int;
----

== Members

[cols="1,4"]
|===
| Name| Description
| `OBJ` 
| A JSON object&period;
| `ARR` 
| A JSON array&period;
| `STR` 
| A JSON string&period;
| `NUM` 
| A JSON number&period;
| `BOOL` 
| A JSON boolean&period;
| `OBJ&lowbar;NAMED&lowbar;PARAMS` 
| Special type that behaves almost exactly like OBJ, defining an options object with a list of pre&hyphen;defined keys&period; The only difference between OBJ and OBJ&lowbar;NAMED&lowbar;PARAMS is that OBJ&lowbar;NAMED&lowbar;PARMS also allows the keys to be passed as top&hyphen;level named parameters, as a more convenient way to pass options to the RPC method without nesting them&period;
| `OBJ&lowbar;USER&lowbar;KEYS` 
| Special type where the user must set the keys e&period;g&period; to define multiple addresses&semi; as opposed to e&period;g&period; an options object where the keys are predefined
| `AMOUNT` 
| Special type representing a floating point amount (can be either NUM or STR)
| `STR&lowbar;HEX` 
| Special type that is a STR with only hex chars
| `RANGE` 
| Special type that is a NUM or &lsqb;NUM,NUM&rsqb;
|===



[.small]#Created with https://www.mrdocs.com[MrDocs]#
