Knowledge base
The forty endpoints behind the management consoleimportantWritten by the HubmechanismEverything the REST API cannot do is done by the console over its own HTTP interface — which our own code can use as well.200 is not success and 400 is not "no such endpoint"importantmechanismThe API's codes describe the request, not the outcome: a DELETE that matched nothing still answers 200.Open the API on a nodeimportantWritten by the HubprocedureThe only way to get a token, and the reason a fresh node's API is closed until someone opens the console.Hand a message to the engine over HTTPWritten by the HubAPI endpointThe HTTP door into the sending queue: the body is a delivery job, the same JSON that would be published to the broker.REST API tokensimportantWritten by the Hubconsole screenCreates the bearer tokens that authorise the REST API — the only way to get one.Code examplesconsole screenReady-made snippets for submitting mail from .NET, Java, PHP and Swift.Command-line submissiontoolA sending client for the shell — useful for tests, which is exactly what we used the broker and REST for instead.