Pending Transactions
PATCH
/transactions/{externalId}
Modify a particular pending transaction identified by its externalId
Name | Description | Data Type | Required |
---|---|---|---|
state |
This specifies the transaction state. Valid value is pending. If this parameter is not passed the default state of transactions being created is pending. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
Authorization |
access_token value obtained from the Token endpoint.This is passed as "Bearer access_token" |
string |
|
AppKey |
This is the Consumer Key provided during the App Registration process and is used to identify the user's application. |
string |
|
content-type |
Valid value is application/json-patch+json. This defines the content type of the request payload accepted by the API. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
externalId |
Proxy will receive this id in the path and inject it in the body payload before calling the target API. |
string |
-
CodeDescription
-
202
Accepted-The request has been accepted for processing, but the processing may not be complete.
-
400
Bad request - The server cannot or will not process the request due to an inaccurate request submitted by the client application. Please resubmit the request after making the required corrections indicated in the error response. For more Info on SEI Error Standards please refer to the API Standards FAQ under Support.
-
401
Unauthorized - Invalid authentication details have been provided. Also useful to trigger an authorization pop up if the API is used from a browser.
-
403
Forbidden-The SEI Server understood the request but refuses to fulfill it.
-
404
Not Found- The requested resource or the underlying resource does not exist. Please resubmit the request after making the required corrections
-
500
Internal Server Error - The SEI server was unable to fulfill the request due to an unknown condition. Please contact SEI for support. For More Info please refer to the "Response & Errors" FAQ under support.
state |
This specifies the transaction state. Valid value is pending. If this parameter is not passed the default state of transactions being created is pending. |
Authorization |
access_token value obtained from the Token endpoint.This is passed as "Bearer access_token" |
AppKey |
This is the Consumer Key provided during the App Registration process and is used to identify the user's application. |
content-type |
Valid value is application/json-patch+json. This defines the content type of the request payload accepted by the API. |
Request Body
externalId Proxy will receive this id in the path and inject it in the body payload before calling the target API. true
Working...
Pending Transactions
PATCH
/transactions/{externalId}
Modify a particular pending transaction identified by its externalId
Name | Description | Data Type | Required |
---|---|---|---|
state |
This specifies the transaction state. Valid value is pending. If this parameter is not passed the default state of transactions being created is pending. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
Authorization |
access_token value obtained from the Token endpoint.This is passed as "Bearer access_token" |
string |
|
AppKey |
This is the Consumer Key provided during the App Registration process and is used to identify the user's application. |
string |
|
content-type |
Valid value is application/json-patch+json. This defines the content type of the request payload accepted by the API. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
externalId |
Proxy will receive this id in the path and inject it in the body payload before calling the target API. |
string |
-
CodeDescription
-
202
Accepted-The request has been accepted for processing, but the processing may not be complete.
-
400
Bad request - The server cannot or will not process the request due to an inaccurate request submitted by the client application. Please resubmit the request after making the required corrections indicated in the error response. For more Info on SEI Error Standards please refer to the API Standards FAQ under Support.
-
401
Unauthorized - Invalid authentication details have been provided. Also useful to trigger an authorization pop up if the API is used from a browser.
-
403
Forbidden-The SEI Server understood the request but refuses to fulfill it.
-
404
Not Found- The requested resource or the underlying resource does not exist. Please resubmit the request after making the required corrections
-
500
Internal Server Error - The SEI server was unable to fulfill the request due to an unknown condition. Please contact SEI for support. For More Info please refer to the "Response & Errors" FAQ under support.
state |
This specifies the transaction state. Valid value is pending. If this parameter is not passed the default state of transactions being created is pending. |
Authorization |
access_token value obtained from the Token endpoint.This is passed as "Bearer access_token" |
AppKey |
This is the Consumer Key provided during the App Registration process and is used to identify the user's application. |
content-type |
Valid value is application/json-patch+json. This defines the content type of the request payload accepted by the API. |
Request Body
externalId Proxy will receive this id in the path and inject it in the body payload before calling the target API. true
Working...
Pass the oAuth Token and the App key to invoke this endpoint for a particular application.
Pending Transactions
PATCH
/transactions/{externalId}
Modify a particular pending transaction identified by its externalId
Name | Description | Data Type | Required |
---|---|---|---|
state |
This specifies the transaction state. Valid value is pending. If this parameter is not passed the default state of transactions being created is pending. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
Authorization |
access_token value obtained from the Token endpoint.This is passed as "Bearer access_token" |
string |
|
AppKey |
This is the Consumer Key provided during the App Registration process and is used to identify the user's application. |
string |
|
content-type |
Valid value is application/json-patch+json. This defines the content type of the request payload accepted by the API. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
externalId |
Proxy will receive this id in the path and inject it in the body payload before calling the target API. |
string |
-
CodeDescription
-
202
Accepted-The request has been accepted for processing, but the processing may not be complete.
-
400
Bad request - The server cannot or will not process the request due to an inaccurate request submitted by the client application. Please resubmit the request after making the required corrections indicated in the error response. For more Info on SEI Error Standards please refer to the API Standards FAQ under Support.
-
401
Unauthorized - Invalid authentication details have been provided. Also useful to trigger an authorization pop up if the API is used from a browser.
-
403
Forbidden-The SEI Server understood the request but refuses to fulfill it.
-
404
Not Found- The requested resource or the underlying resource does not exist. Please resubmit the request after making the required corrections
-
500
Internal Server Error - The SEI server was unable to fulfill the request due to an unknown condition. Please contact SEI for support. For More Info please refer to the "Response & Errors" FAQ under support.
state |
This specifies the transaction state. Valid value is pending. If this parameter is not passed the default state of transactions being created is pending. |
Authorization |
access_token value obtained from the Token endpoint.This is passed as "Bearer access_token" |
AppKey |
This is the Consumer Key provided during the App Registration process and is used to identify the user's application. |
content-type |
Valid value is application/json-patch+json. This defines the content type of the request payload accepted by the API. |
Request Body
externalId Proxy will receive this id in the path and inject it in the body payload before calling the target API. true
Working...
# The application developer can update any field by using the PATCH request. The only mandatory fields is the transactions's "externalId" Described below is an example with a sample payload representing all the fields that can be updated: curl -X PATCH\ https://api.seic.com/v1/transactions/123 \ -H 'appkey: gsedgaerhDSHGRSH' \ -H 'authorization: Bearer ADsgdnnkjnfdIKJN' \ -H 'content-type: application/json-patch+json' \ -d ' [{ "status": "string", "type": "string", "subType": "string", "amount": 0, "currencyIsoCode": "string", "unitType": "string", "unitAmount": 0, "proceedsAmountReceived": 0, "placementFees": 0, "notionalAmount": 0, "redemptionFee": 0, "interestEarned": 0, "notesFromFirm": "string", "notesFromSei": "string", "clientType": "string", "copyNumber": "string", "product": { "productExternalId": "string", "productType": "string", "shareClass": "string", "subProductExternalId": "string", "subProductType": "string", "subProductSubType": "string" }, "investor": { "investorExternalId": "string" }, "dates": { "tradeDate": "2018-07-05T14:11:40.079Z", "docReceivedDate": "2018-07-05T14:11:40.079Z", "proceedsReceivedDate": "2018-07-05T14:11:40.079Z", "proceedsReleaseDate": "2018-07-05T14:11:40.079Z" }, "attributes": { "investmentTermType": "", "standardDate": "", "instPcgType": "" }, "transferInSubProduct": { "subProductExternalId": "", "subProductType": "", "subProductSubType": "" }, "transferInInvestor": { "investorExternalId": "" }, "switchInProduct": { "productExternalId": "", "productType": "" }, "switchInSubProduct": { "subProductExternalId": "", "subProductType": "", "subProductSubType": "" }, "switchInPendingTransaction": { "subType": "", "tradeDate": "" } }]'
Authorization: Bearer ADsgdnnkjnfdIKJN AppKey: gsedgaerhDSHGRSH Content-type: application/json
Content-Type: application/json Status: 202 Accepted requesttrackingid: 67e1ff68-164f-03ad-0f2d-5cbbfda56ec9
{ "data": { "jobStatusQueryKey": "string" } }
Pending Transactions
PATCH
/transactions/{externalId}
Modify a particular pending transaction identified by its externalId
Name | Description | Data Type | Required |
---|---|---|---|
state |
This specifies the transaction state. Valid value is pending. If this parameter is not passed the default state of transactions being created is pending. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
Authorization |
access_token value obtained from the Token endpoint.This is passed as "Bearer access_token" |
string |
|
AppKey |
This is the Consumer Key provided during the App Registration process and is used to identify the user's application. |
string |
|
content-type |
Valid value is application/json-patch+json. This defines the content type of the request payload accepted by the API. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
externalId |
Proxy will receive this id in the path and inject it in the body payload before calling the target API. |
string |
-
CodeDescription
-
202
Accepted-The request has been accepted for processing, but the processing may not be complete.
-
400
Bad request - The server cannot or will not process the request due to an inaccurate request submitted by the client application. Please resubmit the request after making the required corrections indicated in the error response. For more Info on SEI Error Standards please refer to the API Standards FAQ under Support.
-
401
Unauthorized - Invalid authentication details have been provided. Also useful to trigger an authorization pop up if the API is used from a browser.
-
403
Forbidden-The SEI Server understood the request but refuses to fulfill it.
-
404
Not Found- The requested resource or the underlying resource does not exist. Please resubmit the request after making the required corrections
-
500
Internal Server Error - The SEI server was unable to fulfill the request due to an unknown condition. Please contact SEI for support. For More Info please refer to the "Response & Errors" FAQ under support.
state |
This specifies the transaction state. Valid value is pending. If this parameter is not passed the default state of transactions being created is pending. |
Authorization |
access_token value obtained from the Token endpoint.This is passed as "Bearer access_token" |
AppKey |
This is the Consumer Key provided during the App Registration process and is used to identify the user's application. |
content-type |
Valid value is application/json-patch+json. This defines the content type of the request payload accepted by the API. |
Request Body
externalId Proxy will receive this id in the path and inject it in the body payload before calling the target API. true
Working...
Pending Transactions
PATCH
/transactions/{externalId}
Modify a particular pending transaction identified by its externalId
Name | Description | Data Type | Required |
---|---|---|---|
state |
This specifies the transaction state. Valid value is pending. If this parameter is not passed the default state of transactions being created is pending. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
Authorization |
access_token value obtained from the Token endpoint.This is passed as "Bearer access_token" |
string |
|
AppKey |
This is the Consumer Key provided during the App Registration process and is used to identify the user's application. |
string |
|
content-type |
Valid value is application/json-patch+json. This defines the content type of the request payload accepted by the API. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
externalId |
Proxy will receive this id in the path and inject it in the body payload before calling the target API. |
string |
-
CodeDescription
-
202
Accepted-The request has been accepted for processing, but the processing may not be complete.
-
400
Bad request - The server cannot or will not process the request due to an inaccurate request submitted by the client application. Please resubmit the request after making the required corrections indicated in the error response. For more Info on SEI Error Standards please refer to the API Standards FAQ under Support.
-
401
Unauthorized - Invalid authentication details have been provided. Also useful to trigger an authorization pop up if the API is used from a browser.
-
403
Forbidden-The SEI Server understood the request but refuses to fulfill it.
-
404
Not Found- The requested resource or the underlying resource does not exist. Please resubmit the request after making the required corrections
-
500
Internal Server Error - The SEI server was unable to fulfill the request due to an unknown condition. Please contact SEI for support. For More Info please refer to the "Response & Errors" FAQ under support.
state |
This specifies the transaction state. Valid value is pending. If this parameter is not passed the default state of transactions being created is pending. |
Authorization |
access_token value obtained from the Token endpoint.This is passed as "Bearer access_token" |
AppKey |
This is the Consumer Key provided during the App Registration process and is used to identify the user's application. |
content-type |
Valid value is application/json-patch+json. This defines the content type of the request payload accepted by the API. |
Request Body
externalId Proxy will receive this id in the path and inject it in the body payload before calling the target API. true
Working...
Pass the oAuth Token and the App key to invoke this endpoint for a particular application.
Pending Transactions
PATCH
/transactions/{externalId}
Modify a particular pending transaction identified by its externalId
Name | Description | Data Type | Required |
---|---|---|---|
state |
This specifies the transaction state. Valid value is pending. If this parameter is not passed the default state of transactions being created is pending. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
Authorization |
access_token value obtained from the Token endpoint.This is passed as "Bearer access_token" |
string |
|
AppKey |
This is the Consumer Key provided during the App Registration process and is used to identify the user's application. |
string |
|
content-type |
Valid value is application/json-patch+json. This defines the content type of the request payload accepted by the API. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
externalId |
Proxy will receive this id in the path and inject it in the body payload before calling the target API. |
string |
-
CodeDescription
-
202
Accepted-The request has been accepted for processing, but the processing may not be complete.
-
400
Bad request - The server cannot or will not process the request due to an inaccurate request submitted by the client application. Please resubmit the request after making the required corrections indicated in the error response. For more Info on SEI Error Standards please refer to the API Standards FAQ under Support.
-
401
Unauthorized - Invalid authentication details have been provided. Also useful to trigger an authorization pop up if the API is used from a browser.
-
403
Forbidden-The SEI Server understood the request but refuses to fulfill it.
-
404
Not Found- The requested resource or the underlying resource does not exist. Please resubmit the request after making the required corrections
-
500
Internal Server Error - The SEI server was unable to fulfill the request due to an unknown condition. Please contact SEI for support. For More Info please refer to the "Response & Errors" FAQ under support.
state |
This specifies the transaction state. Valid value is pending. If this parameter is not passed the default state of transactions being created is pending. |
Authorization |
access_token value obtained from the Token endpoint.This is passed as "Bearer access_token" |
AppKey |
This is the Consumer Key provided during the App Registration process and is used to identify the user's application. |
content-type |
Valid value is application/json-patch+json. This defines the content type of the request payload accepted by the API. |
Request Body
externalId Proxy will receive this id in the path and inject it in the body payload before calling the target API. true
Working...
# The application developer can update any field by using the PATCH request. The only mandatory fields is the transactions's "externalId" Described below is an example with a sample payload representing all the fields that can be updated: curl -X PATCH\ https://api.seic.com/v1/transactions/123 \ -H 'appkey: gsedgaerhDSHGRSH' \ -H 'authorization: Bearer ADsgdnnkjnfdIKJN' \ -H 'content-type: application/json-patch+json' \ -d ' [{ "status": "string", "type": "string", "subType": "string", "amount": 0, "currencyIsoCode": "string", "unitType": "string", "unitAmount": 0, "proceedsAmountReceived": 0, "placementFees": 0, "notionalAmount": 0, "redemptionFee": 0, "interestEarned": 0, "notesFromFirm": "string", "notesFromSei": "string", "clientType": "string", "copyNumber": "string", "product": { "productExternalId": "string", "productType": "string", "shareClass": "string", "subProductExternalId": "string", "subProductType": "string", "subProductSubType": "string" }, "investor": { "investorExternalId": "string" }, "dates": { "tradeDate": "2018-07-05T14:11:40.079Z", "docReceivedDate": "2018-07-05T14:11:40.079Z", "proceedsReceivedDate": "2018-07-05T14:11:40.079Z", "proceedsReleaseDate": "2018-07-05T14:11:40.079Z" }, "attributes": { "investmentTermType": "", "standardDate": "", "instPcgType": "" }, "transferInSubProduct": { "subProductExternalId": "", "subProductType": "", "subProductSubType": "" }, "transferInInvestor": { "investorExternalId": "" }, "switchInProduct": { "productExternalId": "", "productType": "" }, "switchInSubProduct": { "subProductExternalId": "", "subProductType": "", "subProductSubType": "" }, "switchInPendingTransaction": { "subType": "", "tradeDate": "" } }]'
Authorization: Bearer ADsgdnnkjnfdIKJN AppKey: gsedgaerhDSHGRSH Content-type: application/json
Content-Type: application/json Status: 202 Accepted requesttrackingid: 67e1ff68-164f-03ad-0f2d-5cbbfda56ec9
{ "data": { "jobStatusQueryKey": "string" } }
Pending Transactions
PATCH
/transactions/{externalId}
Modify a particular pending transaction identified by its externalId
Name | Description | Data Type | Required |
---|---|---|---|
state |
This specifies the transaction state. Valid value is pending. If this parameter is not passed the default state of transactions being created is pending. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
Authorization |
access_token value obtained from the Token endpoint.This is passed as "Bearer access_token" |
string |
|
AppKey |
This is the Consumer Key provided during the App Registration process and is used to identify the user's application. |
string |
|
content-type |
Valid value is application/json-patch+json. This defines the content type of the request payload accepted by the API. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
externalId |
Proxy will receive this id in the path and inject it in the body payload before calling the target API. |
string |
-
CodeDescription
-
202
Accepted-The request has been accepted for processing, but the processing may not be complete.
-
400
Bad request - The server cannot or will not process the request due to an inaccurate request submitted by the client application. Please resubmit the request after making the required corrections indicated in the error response. For more Info on SEI Error Standards please refer to the API Standards FAQ under Support.
-
401
Unauthorized - Invalid authentication details have been provided. Also useful to trigger an authorization pop up if the API is used from a browser.
-
403
Forbidden-The SEI Server understood the request but refuses to fulfill it.
-
404
Not Found- The requested resource or the underlying resource does not exist. Please resubmit the request after making the required corrections
-
500
Internal Server Error - The SEI server was unable to fulfill the request due to an unknown condition. Please contact SEI for support. For More Info please refer to the "Response & Errors" FAQ under support.
state |
This specifies the transaction state. Valid value is pending. If this parameter is not passed the default state of transactions being created is pending. |
Authorization |
access_token value obtained from the Token endpoint.This is passed as "Bearer access_token" |
AppKey |
This is the Consumer Key provided during the App Registration process and is used to identify the user's application. |
content-type |
Valid value is application/json-patch+json. This defines the content type of the request payload accepted by the API. |
Request Body
externalId Proxy will receive this id in the path and inject it in the body payload before calling the target API. true
Working...