Laminar
  • Laminar
  • Platform
    • Overview
    • Getting Started
    • Advanced
      • Configurations
      • HTTP Request Batching
      • Workflow Exit Points
      • Invoke Secondary Workflows
      • Managing Notifications
    • Best Practices
    • Keywords
      • lam.resolveThenExecute
      • lam.exit
      • lam.execute
      • lam.asyncExecute
      • lam.httpRequest
      • lam.httpRequests
  • Concepts
    • Workflows
      • Global Workflow Object
    • Flows
      • Flow Types
        • HTTP Request
        • Data Transformations
      • Flow Runs
      • Supported Languages
    • API Key
    • Configurations
    • API
      • Reference
        • Workspaces
          • Issues
          • Users
          • Invitations
            • Decline
            • Accept
            • Received
            • Created
          • Workflows
          • Flows
          • Auth credentials
          • Api keys
          • Api descriptions
        • Workflow
          • Execute
            • External
          • Flows
          • Executions
        • Users
        • Flows
          • Runs
          • Versions
          • Stats
          • Recent runs
          • Read
        • Configurations
          • Properties
          • Flow credentials
          • Workspace
        • Auth credentials
        • Api descriptions
        • Api keys
        • Transform
          • Test
        • Lami
          • Public
          • Direct
        • Auth
          • Signin
          • Register
          • Refresh
          • Me
          • Users
            • Password
    • Changelog
  • External Links
    • Book a Demo
    • Playground
    • Sign In
  • Specification
Powered by GitBook
On this page
  • Functionality
  • Invocation
  • Examples

Was this helpful?

  1. Platform
  2. Keywords

lam.httpRequests

Learn more about the httpRequests Keyword

Functionality

The httpRequests keyword makes multiple HTTP requests in parallel. Each request in the array follows the same format as lam.httpRequest. The responses will be stored in the flow's response object in the same order as the requests.

Invocation

Data transformation must output:

{
  "lam.httpRequests": [
    {
      "method": "GET",
      "url": "https://api.example.com/inventory/{{itemId}}",
      "pathParams": { "itemId": "123" }
    },
    {
      "method": "GET", 
      "url": "https://api.example.com/pricing/{{itemId}}",
      "pathParams": { "itemId": "123" }
    }
  ]
}
Key
Description
Type
Required

method

HTTP method (GET, POST, PUT, DELETE)

String

Yes

url

Destination URL

String

Yes

pathParams

URL path parameters

Object

No

queryParams

URL query parameters

Object

No

headers

HTTP headers

Object

No

body

Request body

Object

No

Examples

(payload) => {
  const { input } = payload;
  
  return {
    "lam.httpRequests": input.items.map(item => ({
      "method": "GET",
      "url": "{{props.baseUrl}}/items/{{itemId}}",
      "pathParams": {
        "itemId": item.id
      },
      "headers": {
        "Authorization": "Bearer {{props.apiKey}}"
      }
    }))
  };
}

Previouslam.httpRequestNextWorkflows

Last updated 1 month ago

Was this helpful?