Create an API token
Create a token in the dashboard. Keep its secret in your application’s secure configuration.
Outgoing HTTP requests
Send HTTP requests through the Adal API.
Submit an HTTP request, choose a region and let Adal execute it asynchronously. Inspect attempts and results in the dashboard or through the API. An incoming Server is not required.
Your application → Adal API → External HTTP service
Submit a request. Track the result.
The API accepts a job; execution and its outcome are tracked separately.
Submit an HTTP request
Choose a region and provide the method, URL, headers and base64-encoded body.
Follow execution
A 202 response confirms acceptance of the job, not successful delivery. Use its request ID to inspect the result.
Execution with a visible history
Keep outbound delivery separate from your application’s request lifecycle.
Queue and retries
Adal executes accepted jobs and retries failed attempts according to its delivery rules.
Region selection
Read the available regions through the API and choose where to execute each request.
Request idempotency
Provide an idempotency key to protect against resubmitting the same job. Recipients must still handle duplicate HTTP calls.
Optional response storage
Response bodies are not saved by default. Enable saving when you need to inspect them; saved response bytes from every attempt count toward traffic usage.
Acceptance is the start of execution
Use the journal and attempt history to distinguish queued jobs, execution and final outcomes. Adal does not turn an asynchronous API call into a synchronous response from the destination.