# Endpoint Definition Request Table (Subtable)

**URL:** <https://community.nextw.com/t/endpoint-definition-request-table-subtable/1857>\
**Category:** Nextworld Platform\
**Created:** [March 23, 2026, 7:19pm UTC](https://community.nextw.com/t/endpoint-definition-request-table-subtable/1857 "2026-03-23T19:19:48Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![daniel.lopez](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/daniel.lopez/32/331_2.png) [@daniel.lopez](https://community.nextw.com/u/daniel.lopez)\
**Post date:** [March 23, 2026, 7:19pm UTC](https://community.nextw.com/t/endpoint-definition-request-table-subtable/1857/1 "2026-03-23T19:19:49Z")

</div>

Hi community,

Is it possible two handle two subtables in a request mapping table (temporary table)?

Thanks,  
Daniel

---

<div class="post-metadata">

**Author:** ![kendra.b](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/kendra.b/32/110_2.png) [@kendra.b](https://community.nextw.com/u/kendra.b)\
**Post date:** [March 24, 2026, 2:43pm UTC](https://community.nextw.com/t/endpoint-definition-request-table-subtable/1857/2 "2026-03-24T14:43:17Z")

</div>

Yes, but has some caveats depending on your case. Can you give more info about the json shape you are trying to fill and the Nextworld shape you are trying to fill it from?

I just looked through all the shipped Nextworld endpoints and couldn’t find an example where someone needed that kind of mapping. There are test cases for it though. The convoluted test case metadata is unlikely to be useful to you so I won’t confuse things with that.

---

<div class="post-metadata">

**Author:** ![daniel.lopez](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/daniel.lopez/32/331_2.png) [@daniel.lopez](https://community.nextw.com/u/daniel.lopez)\
**Post date:** [March 24, 2026, 5:10pm UTC](https://community.nextw.com/t/endpoint-definition-request-table-subtable/1857/3 "2026-03-24T17:10:11Z")

</div>

Hi Kendra,

Here’s a sample payload illustrating the type of request I need. As you can see, it contains multiple list objects, which means the request table must support several subtables within the same structure.

```auto
{
  "accountId": "123456",
  "invoiceHeader": {
    "taxes": [
      {
        "taxName": "SALES_TAX",
        "taxRate": 0.111111,
        "taxType": "SALES",
        "taxAmount": {
          "amount": 30,
          "currencyCode": "USD"
        },
        "taxableBasisAmount": {
          "amount": 300,
          "currencyCode": "USD"
        }
      },
      {
        "taxName": "SALES_TAX",
        "taxRate": 0.222222,
        "taxType": "SALES",
        "taxAmount": {
          "amount": 20,
          "currencyCode": "USD"
        },
        "taxableBasisAmount": {
          "amount": 200,
          "currencyCode": "USD"
        }
      },
      {
        "taxName": "SALES_TAX",
        "taxRate": null,
        "taxType": "SALES",
        "taxAmount": {
          "amount": null,
          "currencyCode": null
        },
        "taxableBasisAmount": {
          "amount": null,
          "currencyCode": null
        }
      }
    ]
  },
  "invoiceLineItems": [
    {
      "charges": [
        {
          "taxes": [
            {
              "taxName": "SALES_TAX",
              "taxRate": 0.111111,
              "taxType": "SALES",
              "taxAmount": {
                "amount": 9.05,
                "currencyCode": "USD"
              },
              "taxableBasisAmount": {
                "amount": 95.05,
                "currencyCode": "USD"
              }
            }
          ]
        }
      ],
      "quantity": {
        "quantity": 2,
        "quantityUnit": "EA"
      }
    },
    {
      "charges": [
        {
          "taxes": [
            {
              "taxName": "SALES_TAX",
              "taxRate": 0.222222,
              "taxType": "SALES",
              "taxAmount": {
                "amount": 20,
                "currencyCode": "USD"
              },
              "taxableBasisAmount": {
                "amount": 200,
                "currencyCode": "USD"
              }
            }
          ]
        }
      ],
      "quantity": {
        "quantity": 4,
        "quantityUnit": "EA"
      }
    },
    {
      "charges": [
        {
          "taxes": [
            {
              "taxName": "SALES_TAX",
              "taxRate": 0.111111,
              "taxType": "SALES",
              "taxAmount": {
                "amount": 20.95,
                "currencyCode": "USD"
              },
              "taxableBasisAmount": {
                "amount": 204.95,
                "currencyCode": "USD"
              }
            }
          ]
        }
      ],
      "quantity": {
        "quantity": 6,
        "quantityUnit": "EA"
      }
    }
  ]
}

```

---

<div class="post-metadata">

**Author:** ![kendra.b](https://sea1.discourse-cdn.com/flex001/user_avatar/community.nextw.com/kendra.b/32/110_2.png) [@kendra.b](https://community.nextw.com/u/kendra.b)\
**Post date:** [March 24, 2026, 9:57pm UTC](https://community.nextw.com/t/endpoint-definition-request-table-subtable/1857/4 "2026-03-24T21:57:06Z")

</div>

Simplifying so it’s easier to reason about:

 ![image](https://us1.discourse-cdn.com/flex001/uploads/nextworld/original/2X/8/8f3bff0534fd9b8f57876aea440cdab73e1db7a4.png)

the json paths of invoiceHeader.taxes as one subtable and invoiceLineItems.charges as another - easy. Two sibling lists can be mapped. But your case has my caveat. Where the mapping will struggle is with invoiceLineItems.charges[].taxes[]. For those, it is _much_ more plausible to use the JSON Array and JSON Object constructs in Logic Block builder to create the shapes exactly as you need it. I believe there is good help text/doc on how to use those options for advanced payload body options.