---
category: [Administration & Integrations, Platform and Product Extensions, Platform and Product Extensions/Integration, Administration & Integrations/Custom Integrations & Apps, Platform and Product Extensions/Workday Extend]
keyword: [Extend, Presentation Components, widgets, tags, UI components]
nav: wcp_docs
parent_url: /wcp_docs/
title: outboundEndPoints
layout: subsection
wd_wcptag: outboundEndPoints
---

<a id="section_N10021_N1001E_N10001"></a>
Contains outbound endpoints and variables for persisting data on an edit page. The `outboundEndPoints` is an array containing combinations of these tags:

-   <b>outboundDataURI</b>

    The default tag for an outbound endpoint. When the user submits the page, Presentation Components invoke all outbound endpoints as ordered in `outboundEndPoints[]`.

    For details about using outbound endpoints, see [Concept: Submitting Data](/wcp_docs/rmd1572291186381.html).

    For details about the attributes, methods, and events on an outbound endpoint, see [outboundDataURI](/wcp_docs/yzz1530025276777.html).

-   <b>outboundVariable</b>

    Contains variables sent to other pages.

    For details about usage and attributes, see [outboundVariable](/wcp_docs/lmd1529983805787.html).



Use `outboundEndPoints` only on edit pages.

<b>Note:</b> Presentation Components impose a 24-second timeout on each endpoint on a page. Individual endpoints exceeding the 24-second limit return a timeout error. In addition to the endpoint limit, Presentation Components also impose a 60-second timeout on a request. A request can include initial page loads, page submissions, and remote validations. (A single request can call multiple endpoints.) All of these operations must complete within 60 seconds, otherwise the page returns a timeout error. This measure protects the Workday tenant from poor performance. When a timeout error has occurred, the <b>Submit</b> button remains disabled to prevent users from submitting duplicate data. To avoid the request timeout, consider limiting the number of endpoints and ensure that you call performant endpoints on each page.

## <a id="section_a14_1dx_g2b"></a>Example

This sample `outboundEndPoints[]` contains an `outboundDataURI` tag, which is the default tag.

```
"outboundData": {
  "outboundEndPoints": [
      {
        "name": "submitRequisition",
        "url": "/requisitions",
        "authType": "sso",
        "baseUrlType": "workday-procurement"
      }
  ]
}
```

You can only use HTTP/HTTPS as the URL protocol for an endpoint.

This next sample `outboundEndPoints[]` contains a combination of `outboundDataURI` and `outboundVariable` tags.

```
"outboundData": {
 "outboundEndPoints": [
  {
   "name": "outboundDataURIExample",
   "baseUrlType": "workday-procurement",
   "url": "<% '/requisitions/' + queryParams.requisitionId %>"
  },
  {
   "type": "outboundVariable",
   "name": "outboundFlowVariableExample",
   "variableScope": "flow",
   "values": [
    {
     "outboundPath": "someFlowVariable",
     "value": "<% someWidget.value %>"
    }
   ]
  }
 ]
}
```

## <a id="section_mobileSupport"></a>Mobile Support

Android, iOS

### Related Information

[Concept: Submitting Data](/wcp_docs/rmd1572291186381.html)

[outboundDataURI](/wcp_docs/yzz1530025276777.html)

[outboundVariable](/wcp_docs/lmd1529983805787.html)