Make HTTP requests

Make HTTP API calls from your flows to set up test data or verify backend state.

Maestro includes a built-in JavaScript HTTP client that allows you to interact with external APIs directly from your test flows. This is particularly useful for setting up test data, authenticating users, or verifying backend state without navigating through the UI.

Making Requests

The Maestro HTTP client is a wrapper around okhttp3 and provides simple methods for common HTTP verbs.

You can use the following shorthand methods for standard requests:

• http.get(url, config)

• http.post(url, config)

• http.put(url, config)

• http.delete(url, config)

For other methods (like PATCH or OPTION), use the generic request function:

const response = http.request('https://example.com', {
    method: "PATCH",
    body: JSON.stringify({ status: "active" })
});

Working with JSON

Maestro provides a global json() function to parse HTTP response bodies into JavaScript objects.

For example, assume that https://api.example.com/user/1 returns the following JSON response:

{
  "id": 1,
  "email": "[email protected]",
  "profile": {
    "name": "Jane Doe",
    "age": 32
  }
}

You can parse the response body and access fields directly:

// script.js
const response = http.get('https://api.example.com/user/1');

// Parse the body and access fields directly
const userData = json(response.body);
output.username = userData.profile.name;

In this example, the user’s name is read from profile.name and assigned to output.username.

Configuration Options

When making a request, you can pass a configuration object to define headers, bodies, or form data.

Headers

Pass custom headers, such as authentication tokens or content types, using the headers property.

const response = http.get('https://example.com', {
    headers: {
        'Authorization': 'Bearer ' + output.token,
        'Content-Type': 'application/json'
    }
});

Request Body

For POST, PUT, or PATCH requests, provide the payload in the body parameter. Remember to stringify JSON objects.

const response = http.post('https://example.com/login', {
    body: JSON.stringify({
        username: "test_user",
        password: "password123"
    })
});

Multipart Form Data

To upload files or send multipart data, use the multipartForm parameter. When sending files, the following parameters are available:

• filePath: The path to the file. It is required for file uploads.

• mediaType: The MIME type of the file (optional).

// script.js
const response = http.post('https://example.com/myEndpoint', {
    multipartForm: {
      "uploadType": "import",
      "data": {
        "filePath": filePath,
        "mediaType": "text/csv"
      }
    },
})

If both body and multipartForm are provided in one request, the body parameter will be ignored.

The response object

Every HTTP call returns a response object containing the following fields:

Field Name	Type	Description
ok	Boolean	true if the request was successful (status 200-299).
status	Number	The HTTP status code (e.g., 200, 404).
body	String	The raw string body of the response.
headers	Object	HTTP response headers (multiple values are comma-separated).

Usage example

A common pattern is to use the API to seed test data before executing UI interactions. This ensures that the specific data you need is present in the environment without relying on manual UI setup steps, which are often slow and flaky.

In this example, we create a new appointment via a POST request and then verify that it appears in the app.

The following script sends a request to an appointments API and stores the appointmentTitle in the output object to be used by the main flow.

// create_appointment.js
const response = http.post('https://my-api.com/v1/appointments', {
    body: JSON.stringify({ 
        title: "Maestro Health Check",
        date: "2026-02-10"
    }),
    headers: { 'Content-Type': 'application/json' }
});

const data = json(response.body);

// Store the title globally so the Flow can assert on it
output.appointmentTitle = data.title;

Once the script has run, the stored values can be accessed from any subsequent step in the Flow:

# flow.yaml
appId: com.example.app
---
- launchApp
- runScript: create_appointment.js
- tapOn: "My Appointments"
# Assert that the data we just created via API is now visible in the UI
- assertVisible: ${output.appointmentTitle}

Next step

Learn how to generate synthetic test data to create dynamic, realistic data at runtime, making your tests more flexible, reusable, and less dependent on hard-coded values.