Plain definitions of the handful of technical words you might run into while setting up, each one line, no assumed background.
The basic way one piece of software asks another to do something over the internet. Every page load, every app action, and every ping FlowProofs receives is one of these.
One "method," or type, of HTTP request: the one used for sending data to create or record something (as opposed to just asking for information back). Every ping to FlowProofs is a POST.
A URL that a tool calls automatically when something happens, instead of you having to check back manually. FlowProofs's ping is a webhook call your system makes to FlowProofs.
The specific URL a request is sent to. FlowProofs has one ingestion endpoint for all events; which side ("source" or "destination") it belongs to is named inside the request itself.
Extra information sent alongside a request, separate from its main content, commonly used to identify who's sending it. FlowProofs's Authorization header is how a ping proves which account it belongs to.
The actual content of a request. For a FlowProofs ping, a small block of structured data (JSON) naming the record, like { "external_id": "call_123" }.
A secret value that proves a request is allowed to act on your account, used in place of a username and password for machine-to-machine calls. Shown once when created, so copy it somewhere safe, since FlowProofs only ever stores a scrambled version afterward.
A plain, widely-used text format for structured data, the { "key": "value" } shape you'll see in every ping body and code example on this site.