The inbox subject for all queries. The NATS broker automatically forwards responses to the NATS requests via this subject. It is important that the property 'custom_inbox_prefix' is set to '_INBOX.{CLIENT_NAME}' when setting up the NATS connection so that NATS can generate the subject correctly.
A client publishes the response to a query on this subject. The exact subject for the query is encoded in the request. If the client uses the NATS respond function, NATS automatically uses the correct
subscribe
replyFromProvider
A client subscribes to this subject in order to receive the response to its queries. If the client uses the NATS request function, NATS takes care of subscribing to the correct subject.
Messages
ReadProviderDefinitionQueryResponse
Content-Type:
ReadProvidersQueryResponse
Content-Type:
ReadVariablesQueryResponse
Content-Type:
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.