These APIs return a product name, unique identifier(s) and additional identifying data for a particular product or list of products.
Relationships
POST
/{externalId}/relationships
Creates a product relationship with the desired investor
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. This defines the content type of the request payload accepted by the API. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
externalId |
The pneumonic of the lookup name |
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.
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. This defines the content type of the request payload accepted by the API. |
Request Body
externalId The pneumonic of the lookup name true
Working...
Relationships
POST
/{externalId}/relationships
Creates a product relationship with the desired investor
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. This defines the content type of the request payload accepted by the API. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
externalId |
The pneumonic of the lookup name |
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.
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. This defines the content type of the request payload accepted by the API. |
Request Body
externalId The pneumonic of the lookup name true
Working...
Pass the oAuth Token and the App key to invoke this endpoint for a particular application.
Relationships
POST
/{externalId}/relationships
Creates a product relationship with the desired investor
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. This defines the content type of the request payload accepted by the API. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
externalId |
The pneumonic of the lookup name |
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.
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. This defines the content type of the request payload accepted by the API. |
Request Body
externalId The pneumonic of the lookup name true
Working...
#Described below is a sample request with a sample payload representing the required fields you would need in a POST request to create the product relationship. curl -X POST\ https://api.seic.com/v1/products/TestLP/relationships\ -H 'appkey: gsedgaerhDSHGRSH' \ -H 'authorization: Bearer ADsgdnnkjnfdIKJN' \ -H 'content-type: application/json' \ -d '[ { "investorExternalId": "0337", "type": "Fund", "relationshipStatus": "Inactive", "inceptionDate": "2014-05-01" } ]' #Described below is a sample request with a sample payload representing all the fields you can pass in a POST request to create the product relationship. curl -X POST\ https://api.seic.com/v1/products/TestLP/relationships\ -H 'appkey: gsedgaerhDSHGRSH' \ -H 'authorization: Bearer ADsgdnnkjnfdIKJN' \ -H 'content-type: application/json' \ -d ' [ { "investorExternalId": "0337", "type": "Fund", "alternateId": "12345-ABC", "channel": "Onshore", "subChannel": "", "sourceOfFunds": "text", "dividendDistribution": "Reinvest", "commitmentElection": "Prepay", "relationshipStatus": "Active", "inceptionDate": "2014-05-01", "terminationDate": "", "eligibility": { "managementFee": false, "incentiveFee": false, "feeBreakEligible": false, "sidePocket": true, "sideLetter": false, "employee": false }, "subProduct": { "externalId": "TestLPA1", "type": "Series", "subType": "Standard", "alternateId": "99999", "active": true } } ]
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" } }
Relationships
POST
/{externalId}/relationships
Creates a product relationship with the desired investor
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. This defines the content type of the request payload accepted by the API. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
externalId |
The pneumonic of the lookup name |
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.
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. This defines the content type of the request payload accepted by the API. |
Request Body
externalId The pneumonic of the lookup name true
Working...
Relationships
POST
/{externalId}/relationships
Creates a product relationship with the desired investor
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. This defines the content type of the request payload accepted by the API. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
externalId |
The pneumonic of the lookup name |
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.
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. This defines the content type of the request payload accepted by the API. |
Request Body
externalId The pneumonic of the lookup name true
Working...
Pass the oAuth Token and the App key to invoke this endpoint for a particular application.
Relationships
POST
/{externalId}/relationships
Creates a product relationship with the desired investor
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. This defines the content type of the request payload accepted by the API. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
externalId |
The pneumonic of the lookup name |
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.
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. This defines the content type of the request payload accepted by the API. |
Request Body
externalId The pneumonic of the lookup name true
Working...
#Described below is a sample request with a sample payload representing the required fields you would need in a POST request to create the product relationship. curl -X POST\ https://api.seic.com/v1/products/TestLP/relationships\ -H 'appkey: gsedgaerhDSHGRSH' \ -H 'authorization: Bearer ADsgdnnkjnfdIKJN' \ -H 'content-type: application/json' \ -d '[ { "investorExternalId": "0337", "type": "Fund", "relationshipStatus": "Inactive", "inceptionDate": "2014-05-01" } ]' #Described below is a sample request with a sample payload representing all the fields you can pass in a POST request to create the product relationship. curl -X POST\ https://api.seic.com/v1/products/TestLP/relationships\ -H 'appkey: gsedgaerhDSHGRSH' \ -H 'authorization: Bearer ADsgdnnkjnfdIKJN' \ -H 'content-type: application/json' \ -d ' [ { "investorExternalId": "0337", "type": "Fund", "alternateId": "12345-ABC", "channel": "Onshore", "subChannel": "", "sourceOfFunds": "text", "dividendDistribution": "Reinvest", "commitmentElection": "Prepay", "relationshipStatus": "Active", "inceptionDate": "2014-05-01", "terminationDate": "", "eligibility": { "managementFee": false, "incentiveFee": false, "feeBreakEligible": false, "sidePocket": true, "sideLetter": false, "employee": false }, "subProduct": { "externalId": "TestLPA1", "type": "Series", "subType": "Standard", "alternateId": "99999", "active": true } } ]
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" } }
Relationships
POST
/{externalId}/relationships
Creates a product relationship with the desired investor
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. This defines the content type of the request payload accepted by the API. |
string |
Name | Description | Data Type | Required |
---|---|---|---|
externalId |
The pneumonic of the lookup name |
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.
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. This defines the content type of the request payload accepted by the API. |
Request Body
externalId The pneumonic of the lookup name true
Working...