Partner Integration Definitions Administration v0.4.1
Scroll down for code samples, example requests and responses. Select a language for code samples from the tabs above or the mobile navigation menu.
This API allows Apiture Developer Portal (Dev Portal) administrators and manage partner integration definitions submitted by Developer Portal users. An integration definition defines a third party (fintech) integration into the Apiture Digital Banking platform. Initially, such integrations are for single-sign-on integrations (using SAML). This API allows administrators to review and approve/activate or reject integration definitions, or to deactivate integrations which Apiture or the financial institution suspects of fraudulent use or has a security risk or exposure.
Like client applications, an owner of an integration definition can invite other owners.
Owners may promote integration definitions (change from staged to live/active), disable them, and if there are no active instances, delete an integration definition.
Download OpenAPI Definition (YAML)
Base URLs:
License: Apiture API License
Authentication
- OpenID Connect authentication (
adminAccessToken
)- OpenId Connect (OIDC) authentication/authorization for an administrative user, such as financial institution staff or Apiture administrators. The client uses the
authorization_endpoint
andtoken_endpoint
to obtain an access token to pass in theAuthorization
header. Those endpoints are available via the OIDC Configuration URL. The actual URL may vary with each financial institution. See details at Secure Access. - OIDC Configuration URL =
https://auth.apiture.com/oidc/.well-known/openid-configuration
- OpenId Connect (OIDC) authentication/authorization for an administrative user, such as financial institution staff or Apiture administrators. The client uses the
Partner Integration Definitions
Partner (Third Party) Integration Definitions
listPartnerIntegrationDefinitions
Code samples
# You can also use wget
curl -X GET https://api.apiture.com/devAdmin/integrationDefinitions \
-H 'Accept: application/json' \
-H 'Authorization: Bearer {access-token}'
GET https://api.apiture.com/devAdmin/integrationDefinitions HTTP/1.1
Host: api.apiture.com
Accept: application/json
const fetch = require('node-fetch');
const headers = {
'Accept':'application/json',
'Authorization':'Bearer {access-token}'
};
fetch('https://api.apiture.com/devAdmin/integrationDefinitions',
{
method: 'GET',
headers: headers
})
.then(function(res) {
return res.json();
}).then(function(body) {
console.log(body);
});
var headers = {
'Accept':'application/json',
'Authorization':'Bearer {access-token}'
};
$.ajax({
url: 'https://api.apiture.com/devAdmin/integrationDefinitions',
method: 'get',
headers: headers,
success: function(data) {
console.log(JSON.stringify(data));
}
})
require 'rest-client'
require 'json'
headers = {
'Accept' => 'application/json',
'Authorization' => 'Bearer {access-token}'
}
result = RestClient.get 'https://api.apiture.com/devAdmin/integrationDefinitions',
params: {
}, headers: headers
p JSON.parse(result)
import requests
headers = {
'Accept': 'application/json',
'Authorization': 'Bearer {access-token}'
}
r = requests.get('https://api.apiture.com/devAdmin/integrationDefinitions', params={
}, headers = headers)
print r.json()
URL obj = new URL("https://api.apiture.com/devAdmin/integrationDefinitions");
HttpURLConnection con = (HttpURLConnection) obj.openConnection();
con.setRequestMethod("GET");
int responseCode = con.getResponseCode();
BufferedReader in = new BufferedReader(
new InputStreamReader(con.getInputStream()));
String inputLine;
StringBuffer response = new StringBuffer();
while ((inputLine = in.readLine()) != null) {
response.append(inputLine);
}
in.close();
System.out.println(response.toString());
package main
import (
"bytes"
"net/http"
)
func main() {
headers := map[string][]string{
"Accept": []string{"application/json"},
"Authorization": []string{"Bearer {access-token}"},
}
data := bytes.NewBuffer([]byte{jsonReq})
req, err := http.NewRequest("GET", "https://api.apiture.com/devAdmin/integrationDefinitions", data)
req.Header = headers
client := &http.Client{}
resp, err := client.Do(req)
// ...
}
Return a collection of integrations
GET https://api.apiture.com/devAdmin/integrationDefinitions
Return a collection of integration definitions.
Parameters
Parameter | Description |
---|---|
staged in: query | boolean Filter the response to only include integrations whose staged property matches this value. |
partnerId in: query | resourceId Filter the response to only include integrations whose partnerId matches the this value.minLength: 6 maxLength: 48 pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$" |
institutionId in: query | institutionId Filter the response to only include integrations whose institutionId matches the this value. When availability is not specifically filtered to return only definitions available to a single institution, definitions available to all institutions will also be returned.minLength: 2 maxLength: 8 pattern: "^[A-Z0-9_]{2,8}$" |
environmentId in: query | resourceId Filter the response to only include integrations whose environmentId matches the this value.minLength: 6 maxLength: 48 pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$" |
availability in: query | array[string] Filter the response to only include integration definitions with the specified availability. unique items minItems: 1 maxItems: 4 pipe-delimited items: string » enum values: web , mobile , business , personal , singleInstitution , allInstitutions |
Example responses
200 Response
{
"items": [
{
"id": "ULTRA_PAY",
"createdAt": "2021-10-30T19:06:04.250Z",
"updatedAt": "2021-10-30T19:06:04.250Z",
"partnerId": "3rdpartybank.com",
"state": "active",
"staged": false,
"activeInstanceCount": 14,
"description": "string",
"availability": {
"web": true,
"mobile": true,
"retail": true,
"commercial": true,
"institutions": "single"
},
"createdBy": "fintechdev_01",
"assertionEncryptionSupported": true,
"serviceProviderMetadataUrl": "https://my.audience.com/saml/metadata.xml",
"serviceProviderHostsMetadata": true
}
]
}
Responses
Status | Description |
---|---|
200 | OK |
OK. | |
Schema: integrationDefinitions |
Status | Description |
---|---|
400 | Bad Request |
Bad Request. The request body, request headers, and/or query parameters are not well-formed. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
401 | Unauthorized |
Unauthorized. The operation requires authentication but no authentication or insufficient authentication was given. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
403 | Forbidden |
Forbidden. The authenticated caller is not authorized to perform the requested operation. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
422 | Unprocessable Entity |
Unprocessable Entity. The request body and/or query parameters were well-formed but otherwise invalid. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
429 | Too Many Requests |
Too Many Requests. The client has sent too many requests in a given amount of time. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
4XX | Unknown |
Client Request Problem. The client request had a problem not listed under another specific 400-level HTTP response code. View the detail in the problem response for additional details. | |
Schema: Inline |
Status | Description |
---|---|
5XX | Unknown |
Server Problem. The server encountered a problem not listed under another specific 500-level HTTP response code. View the detail in the problem response for additional details. | |
Schema: Inline |
Response Schema
Status Code 400
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 401
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 403
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 422
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 429
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 4XX
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 5XX
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
getPartnerIntegrationDefinition
Code samples
# You can also use wget
curl -X GET https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId} \
-H 'Accept: application/json' \
-H 'Authorization: Bearer {access-token}'
GET https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId} HTTP/1.1
Host: api.apiture.com
Accept: application/json
const fetch = require('node-fetch');
const headers = {
'Accept':'application/json',
'Authorization':'Bearer {access-token}'
};
fetch('https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}',
{
method: 'GET',
headers: headers
})
.then(function(res) {
return res.json();
}).then(function(body) {
console.log(body);
});
var headers = {
'Accept':'application/json',
'Authorization':'Bearer {access-token}'
};
$.ajax({
url: 'https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}',
method: 'get',
headers: headers,
success: function(data) {
console.log(JSON.stringify(data));
}
})
require 'rest-client'
require 'json'
headers = {
'Accept' => 'application/json',
'Authorization' => 'Bearer {access-token}'
}
result = RestClient.get 'https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}',
params: {
}, headers: headers
p JSON.parse(result)
import requests
headers = {
'Accept': 'application/json',
'Authorization': 'Bearer {access-token}'
}
r = requests.get('https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}', params={
}, headers = headers)
print r.json()
URL obj = new URL("https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}");
HttpURLConnection con = (HttpURLConnection) obj.openConnection();
con.setRequestMethod("GET");
int responseCode = con.getResponseCode();
BufferedReader in = new BufferedReader(
new InputStreamReader(con.getInputStream()));
String inputLine;
StringBuffer response = new StringBuffer();
while ((inputLine = in.readLine()) != null) {
response.append(inputLine);
}
in.close();
System.out.println(response.toString());
package main
import (
"bytes"
"net/http"
)
func main() {
headers := map[string][]string{
"Accept": []string{"application/json"},
"Authorization": []string{"Bearer {access-token}"},
}
data := bytes.NewBuffer([]byte{jsonReq})
req, err := http.NewRequest("GET", "https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}", data)
req.Header = headers
client := &http.Client{}
resp, err := client.Do(req)
// ...
}
Fetch a representation of this integration
GET https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}
Return a representation of the integration definition.
Parameters
Parameter | Description |
---|---|
integrationDefinitionId in: path | integrationDefinitionId (required) The integration identifier path parameter. This is a human-readable, but globally unique identifier. minLength: 2 maxLength: 16 pattern: "^[A-Z0-9_]{2,16}$" |
Example responses
200 Response
{
"id": "FINTECH1_MODEL",
"description": "Fintech1 Financial Modeling Integration",
"staged": false,
"state": "active",
"activeInstanceCount": 14,
"label": "Fintech1 Financial Modeling",
"mobileLabel": "Fintech1 Financial Modeling",
"usesSpecificCustomerId": true,
"specificCustomerIdLabel": "Customer Id",
"specificCustomerIdDescription": "Customer Id",
"availability": {
"web": true,
"mobile": true,
"retail": true,
"commercial": true,
"institutions": "single"
},
"environmentId": "04833ea3-fbe0-43ac-95f8-188f59461ad5",
"institutionId": "TCF",
"partnerId": "3rdpartybank.com",
"code": "createSAMLRequest(user: UserData, param: Parameters, integration: Integration) {\n integration.assertions.add('answer', '42');\n}",
"audienceUrl": "https://my.audience.com/",
"defaultRelayState": "RelStat123",
"signatureAlgorithm": "RSA-SHA256",
"digestAlgorithm": "SHA256",
"encryptionAlgorithm": "AES256-GCM",
"assertionEncryptionSupported": true,
"serviceProviderMetadataUrl": "https://my.audience.com/saml/metadata.xml",
"serviceProviderHostsMetadata": true,
"targetMethod": "SAML-POST",
"targetUrlTemplate": "https://my-integration.example.com/sp/saml?cust=%7B%7BinstitutionId%7D%7D",
"parameterSchema": {
"type": "object",
"properties": {
"value1": {
"description": "...",
"type": "string",
"format": "text",
"minLength": 1,
"maxLength": 200
},
"value2": {
"description": "...",
"type": "integer",
"format": "int32",
"minimum": 1,
"maximum": 100
},
"value3": {
"description": "...",
"type": "string",
"enum": [
"a",
"b",
"c"
]
}
}
},
"owners": [
"walter.white@example.com",
"walter.grey@example.com",
"walter.black@example.com"
]
}
Responses
Status | Description |
---|---|
200 | OK |
OK. | |
Schema: integrationDefinition |
Status | Description |
---|---|
400 | Bad Request |
Bad Request. The request body, request headers, and/or query parameters are not well-formed. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
401 | Unauthorized |
Unauthorized. The operation requires authentication but no authentication or insufficient authentication was given. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
403 | Forbidden |
Forbidden. The authenticated caller is not authorized to perform the requested operation. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
404 | Not Found |
Not found. There is no such resource at the request URL. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
429 | Too Many Requests |
Too Many Requests. The client has sent too many requests in a given amount of time. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
4XX | Unknown |
Client Request Problem. The client request had a problem not listed under another specific 400-level HTTP response code. View the detail in the problem response for additional details. | |
Schema: Inline |
Status | Description |
---|---|
5XX | Unknown |
Server Problem. The server encountered a problem not listed under another specific 500-level HTTP response code. View the detail in the problem response for additional details. | |
Schema: Inline |
Response Schema
Status Code 400
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 401
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 403
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 404
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 429
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 4XX
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 5XX
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Partner Integration Definition Actions
Actions on Integration Definitions
deactivatePartnerIntegrationDefinition
Code samples
# You can also use wget
curl -X POST https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/inactive \
-H 'Accept: application/json' \
-H 'Authorization: Bearer {access-token}'
POST https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/inactive HTTP/1.1
Host: api.apiture.com
Accept: application/json
const fetch = require('node-fetch');
const headers = {
'Accept':'application/json',
'Authorization':'Bearer {access-token}'
};
fetch('https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/inactive',
{
method: 'POST',
headers: headers
})
.then(function(res) {
return res.json();
}).then(function(body) {
console.log(body);
});
var headers = {
'Accept':'application/json',
'Authorization':'Bearer {access-token}'
};
$.ajax({
url: 'https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/inactive',
method: 'post',
headers: headers,
success: function(data) {
console.log(JSON.stringify(data));
}
})
require 'rest-client'
require 'json'
headers = {
'Accept' => 'application/json',
'Authorization' => 'Bearer {access-token}'
}
result = RestClient.post 'https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/inactive',
params: {
}, headers: headers
p JSON.parse(result)
import requests
headers = {
'Accept': 'application/json',
'Authorization': 'Bearer {access-token}'
}
r = requests.post('https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/inactive', params={
}, headers = headers)
print r.json()
URL obj = new URL("https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/inactive");
HttpURLConnection con = (HttpURLConnection) obj.openConnection();
con.setRequestMethod("POST");
int responseCode = con.getResponseCode();
BufferedReader in = new BufferedReader(
new InputStreamReader(con.getInputStream()));
String inputLine;
StringBuffer response = new StringBuffer();
while ((inputLine = in.readLine()) != null) {
response.append(inputLine);
}
in.close();
System.out.println(response.toString());
package main
import (
"bytes"
"net/http"
)
func main() {
headers := map[string][]string{
"Accept": []string{"application/json"},
"Authorization": []string{"Bearer {access-token}"},
}
data := bytes.NewBuffer([]byte{jsonReq})
req, err := http.NewRequest("POST", "https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/inactive", data)
req.Header = headers
client := &http.Client{}
resp, err := client.Do(req)
// ...
}
Deactivate an integration definition.
POST https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/inactive
Mark a disabled integration definition as inactive. This allows Apiture (perhaps on behalf of the financial institution) to prevent new integrations being created from an integration definition, for example, if there is suspicion of fraud or a security vulnerability. This sets the state
to inactive
.
Deactivated integration definitions are also unregistered in the System Integration Definitions API.
Only inactive
, disabled
, or active
integration definition may be deactivated. Inactive integration definition can be activated again (by and administrator) with the activatePartnerIntegrationDefinition
.
This operation is idempotent: it does nothing if the integration definition's state
is already `inactive'.
Parameters
Parameter | Description |
---|---|
integrationDefinitionId in: path | integrationDefinitionId (required) The integration identifier path parameter. This is a human-readable, but globally unique identifier. minLength: 2 maxLength: 16 pattern: "^[A-Z0-9_]{2,16}$" |
Example responses
200 Response
{
"id": "FINTECH1_MODEL",
"description": "Fintech1 Financial Modeling Integration",
"staged": false,
"state": "active",
"activeInstanceCount": 14,
"label": "Fintech1 Financial Modeling",
"mobileLabel": "Fintech1 Financial Modeling",
"usesSpecificCustomerId": true,
"specificCustomerIdLabel": "Customer Id",
"specificCustomerIdDescription": "Customer Id",
"availability": {
"web": true,
"mobile": true,
"retail": true,
"commercial": true,
"institutions": "single"
},
"environmentId": "04833ea3-fbe0-43ac-95f8-188f59461ad5",
"institutionId": "TCF",
"partnerId": "3rdpartybank.com",
"code": "createSAMLRequest(user: UserData, param: Parameters, integration: Integration) {\n integration.assertions.add('answer', '42');\n}",
"audienceUrl": "https://my.audience.com/",
"defaultRelayState": "RelStat123",
"signatureAlgorithm": "RSA-SHA256",
"digestAlgorithm": "SHA256",
"encryptionAlgorithm": "AES256-GCM",
"assertionEncryptionSupported": true,
"serviceProviderMetadataUrl": "https://my.audience.com/saml/metadata.xml",
"serviceProviderHostsMetadata": true,
"targetMethod": "SAML-POST",
"targetUrlTemplate": "https://my-integration.example.com/sp/saml?cust=%7B%7BinstitutionId%7D%7D",
"parameterSchema": {
"type": "object",
"properties": {
"value1": {
"description": "...",
"type": "string",
"format": "text",
"minLength": 1,
"maxLength": 200
},
"value2": {
"description": "...",
"type": "integer",
"format": "int32",
"minimum": 1,
"maximum": 100
},
"value3": {
"description": "...",
"type": "string",
"enum": [
"a",
"b",
"c"
]
}
}
},
"owners": [
"walter.white@example.com",
"walter.grey@example.com",
"walter.black@example.com"
]
}
Responses
Status | Description |
---|---|
200 | OK |
OK. The integration definition was marked as enabled. | |
Schema: integrationDefinition | |
202 | Accepted |
Accepted. The request to enabled an integration definition was accepted. | |
Schema: integrationDefinition |
Status | Description |
---|---|
400 | Bad Request |
Bad Request. The request body, request headers, and/or query parameters are not well-formed. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
401 | Unauthorized |
Unauthorized. The operation requires authentication but no authentication or insufficient authentication was given. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
403 | Forbidden |
Forbidden. The authenticated caller is not authorized to perform the requested operation. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
404 | Not Found |
Not found. There is no such resource at the request URL. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
409 | Conflict |
Conflict. This problem responsemay have one of the following
| |
Schema: problemResponse |
Status | Description |
---|---|
429 | Too Many Requests |
Too Many Requests. The client has sent too many requests in a given amount of time. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
4XX | Unknown |
Client Request Problem. The client request had a problem not listed under another specific 400-level HTTP response code. View the detail in the problem response for additional details. | |
Schema: Inline |
Status | Description |
---|---|
5XX | Unknown |
Server Problem. The server encountered a problem not listed under another specific 500-level HTTP response code. View the detail in the problem response for additional details. | |
Schema: Inline |
Response Schema
Status Code 400
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 401
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 403
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 404
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 429
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 4XX
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 5XX
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
activatePartnerIntegrationDefinition
Code samples
# You can also use wget
curl -X POST https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/active \
-H 'Accept: application/json' \
-H 'Authorization: Bearer {access-token}'
POST https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/active HTTP/1.1
Host: api.apiture.com
Accept: application/json
const fetch = require('node-fetch');
const headers = {
'Accept':'application/json',
'Authorization':'Bearer {access-token}'
};
fetch('https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/active',
{
method: 'POST',
headers: headers
})
.then(function(res) {
return res.json();
}).then(function(body) {
console.log(body);
});
var headers = {
'Accept':'application/json',
'Authorization':'Bearer {access-token}'
};
$.ajax({
url: 'https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/active',
method: 'post',
headers: headers,
success: function(data) {
console.log(JSON.stringify(data));
}
})
require 'rest-client'
require 'json'
headers = {
'Accept' => 'application/json',
'Authorization' => 'Bearer {access-token}'
}
result = RestClient.post 'https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/active',
params: {
}, headers: headers
p JSON.parse(result)
import requests
headers = {
'Accept': 'application/json',
'Authorization': 'Bearer {access-token}'
}
r = requests.post('https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/active', params={
}, headers = headers)
print r.json()
URL obj = new URL("https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/active");
HttpURLConnection con = (HttpURLConnection) obj.openConnection();
con.setRequestMethod("POST");
int responseCode = con.getResponseCode();
BufferedReader in = new BufferedReader(
new InputStreamReader(con.getInputStream()));
String inputLine;
StringBuffer response = new StringBuffer();
while ((inputLine = in.readLine()) != null) {
response.append(inputLine);
}
in.close();
System.out.println(response.toString());
package main
import (
"bytes"
"net/http"
)
func main() {
headers := map[string][]string{
"Accept": []string{"application/json"},
"Authorization": []string{"Bearer {access-token}"},
}
data := bytes.NewBuffer([]byte{jsonReq})
req, err := http.NewRequest("POST", "https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/active", data)
req.Header = headers
client := &http.Client{}
resp, err := client.Do(req)
// ...
}
Activate an integration definition.
POST https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/active
Mark an inactive or disabled integration definition as active. Note: Approving an integration definition is performed by activating a submitted integration definition. Only submitted
, inactive
, disabled
, or active
integration definition may be activated. This sets the state
to active
and also provisions the integration definition in the back end (using the System Integration Definitions API).
This operation is idempotent: it does nothing if the integration definition's state
is already `active'.
Parameters
Parameter | Description |
---|---|
integrationDefinitionId in: path | integrationDefinitionId (required) The integration identifier path parameter. This is a human-readable, but globally unique identifier. minLength: 2 maxLength: 16 pattern: "^[A-Z0-9_]{2,16}$" |
Example responses
200 Response
{
"id": "FINTECH1_MODEL",
"description": "Fintech1 Financial Modeling Integration",
"staged": false,
"state": "active",
"activeInstanceCount": 14,
"label": "Fintech1 Financial Modeling",
"mobileLabel": "Fintech1 Financial Modeling",
"usesSpecificCustomerId": true,
"specificCustomerIdLabel": "Customer Id",
"specificCustomerIdDescription": "Customer Id",
"availability": {
"web": true,
"mobile": true,
"retail": true,
"commercial": true,
"institutions": "single"
},
"environmentId": "04833ea3-fbe0-43ac-95f8-188f59461ad5",
"institutionId": "TCF",
"partnerId": "3rdpartybank.com",
"code": "createSAMLRequest(user: UserData, param: Parameters, integration: Integration) {\n integration.assertions.add('answer', '42');\n}",
"audienceUrl": "https://my.audience.com/",
"defaultRelayState": "RelStat123",
"signatureAlgorithm": "RSA-SHA256",
"digestAlgorithm": "SHA256",
"encryptionAlgorithm": "AES256-GCM",
"assertionEncryptionSupported": true,
"serviceProviderMetadataUrl": "https://my.audience.com/saml/metadata.xml",
"serviceProviderHostsMetadata": true,
"targetMethod": "SAML-POST",
"targetUrlTemplate": "https://my-integration.example.com/sp/saml?cust=%7B%7BinstitutionId%7D%7D",
"parameterSchema": {
"type": "object",
"properties": {
"value1": {
"description": "...",
"type": "string",
"format": "text",
"minLength": 1,
"maxLength": 200
},
"value2": {
"description": "...",
"type": "integer",
"format": "int32",
"minimum": 1,
"maximum": 100
},
"value3": {
"description": "...",
"type": "string",
"enum": [
"a",
"b",
"c"
]
}
}
},
"owners": [
"walter.white@example.com",
"walter.grey@example.com",
"walter.black@example.com"
]
}
Responses
Status | Description |
---|---|
200 | OK |
OK. The integration definition was marked as activated and provisioned. | |
Schema: integrationDefinition | |
202 | Accepted |
Accepted. The request to activate and provision an integration definition was accepted. | |
Schema: integrationDefinition |
Status | Description |
---|---|
400 | Bad Request |
Bad Request. The request body, request headers, and/or query parameters are not well-formed. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
401 | Unauthorized |
Unauthorized. The operation requires authentication but no authentication or insufficient authentication was given. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
403 | Forbidden |
Forbidden. The authenticated caller is not authorized to perform the requested operation. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
404 | Not Found |
Not found. There is no such resource at the request URL. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
409 | Conflict |
Conflict. This problem responsemay have one of the following
| |
Schema: problemResponse |
Status | Description |
---|---|
429 | Too Many Requests |
Too Many Requests. The client has sent too many requests in a given amount of time. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
4XX | Unknown |
Client Request Problem. The client request had a problem not listed under another specific 400-level HTTP response code. View the detail in the problem response for additional details. | |
Schema: Inline |
Status | Description |
---|---|
5XX | Unknown |
Server Problem. The server encountered a problem not listed under another specific 500-level HTTP response code. View the detail in the problem response for additional details. | |
Schema: Inline |
Response Schema
Status Code 400
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 401
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 403
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 404
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 429
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 4XX
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 5XX
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
rejectPartnerIntegrationDefinition
Code samples
# You can also use wget
curl -X POST https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/rejected \
-H 'Accept: application/json' \
-H 'Authorization: Bearer {access-token}'
POST https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/rejected HTTP/1.1
Host: api.apiture.com
Accept: application/json
const fetch = require('node-fetch');
const headers = {
'Accept':'application/json',
'Authorization':'Bearer {access-token}'
};
fetch('https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/rejected',
{
method: 'POST',
headers: headers
})
.then(function(res) {
return res.json();
}).then(function(body) {
console.log(body);
});
var headers = {
'Accept':'application/json',
'Authorization':'Bearer {access-token}'
};
$.ajax({
url: 'https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/rejected',
method: 'post',
headers: headers,
success: function(data) {
console.log(JSON.stringify(data));
}
})
require 'rest-client'
require 'json'
headers = {
'Accept' => 'application/json',
'Authorization' => 'Bearer {access-token}'
}
result = RestClient.post 'https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/rejected',
params: {
}, headers: headers
p JSON.parse(result)
import requests
headers = {
'Accept': 'application/json',
'Authorization': 'Bearer {access-token}'
}
r = requests.post('https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/rejected', params={
}, headers = headers)
print r.json()
URL obj = new URL("https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/rejected");
HttpURLConnection con = (HttpURLConnection) obj.openConnection();
con.setRequestMethod("POST");
int responseCode = con.getResponseCode();
BufferedReader in = new BufferedReader(
new InputStreamReader(con.getInputStream()));
String inputLine;
StringBuffer response = new StringBuffer();
while ((inputLine = in.readLine()) != null) {
response.append(inputLine);
}
in.close();
System.out.println(response.toString());
package main
import (
"bytes"
"net/http"
)
func main() {
headers := map[string][]string{
"Accept": []string{"application/json"},
"Authorization": []string{"Bearer {access-token}"},
}
data := bytes.NewBuffer([]byte{jsonReq})
req, err := http.NewRequest("POST", "https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/rejected", data)
req.Header = headers
client := &http.Client{}
resp, err := client.Do(req)
// ...
}
Reject an integration definition.
POST https://api.apiture.com/devAdmin/integrationDefinitions/{integrationDefinitionId}/rejected
Mark an inactive or disabled integration definition as rejected. Only submitted
, inactive
, disabled
, or rejected
integration definition may be marked as rejected. This sets the state
to rejected
and notifies the owners of the change.
This operation is idempotent: it does nothing if the integration definition's state
is already `rejected'.
Parameters
Parameter | Description |
---|---|
integrationDefinitionId in: path | integrationDefinitionId (required) The integration identifier path parameter. This is a human-readable, but globally unique identifier. minLength: 2 maxLength: 16 pattern: "^[A-Z0-9_]{2,16}$" |
Example responses
200 Response
{
"id": "FINTECH1_MODEL",
"description": "Fintech1 Financial Modeling Integration",
"staged": false,
"state": "active",
"activeInstanceCount": 14,
"label": "Fintech1 Financial Modeling",
"mobileLabel": "Fintech1 Financial Modeling",
"usesSpecificCustomerId": true,
"specificCustomerIdLabel": "Customer Id",
"specificCustomerIdDescription": "Customer Id",
"availability": {
"web": true,
"mobile": true,
"retail": true,
"commercial": true,
"institutions": "single"
},
"environmentId": "04833ea3-fbe0-43ac-95f8-188f59461ad5",
"institutionId": "TCF",
"partnerId": "3rdpartybank.com",
"code": "createSAMLRequest(user: UserData, param: Parameters, integration: Integration) {\n integration.assertions.add('answer', '42');\n}",
"audienceUrl": "https://my.audience.com/",
"defaultRelayState": "RelStat123",
"signatureAlgorithm": "RSA-SHA256",
"digestAlgorithm": "SHA256",
"encryptionAlgorithm": "AES256-GCM",
"assertionEncryptionSupported": true,
"serviceProviderMetadataUrl": "https://my.audience.com/saml/metadata.xml",
"serviceProviderHostsMetadata": true,
"targetMethod": "SAML-POST",
"targetUrlTemplate": "https://my-integration.example.com/sp/saml?cust=%7B%7BinstitutionId%7D%7D",
"parameterSchema": {
"type": "object",
"properties": {
"value1": {
"description": "...",
"type": "string",
"format": "text",
"minLength": 1,
"maxLength": 200
},
"value2": {
"description": "...",
"type": "integer",
"format": "int32",
"minimum": 1,
"maximum": 100
},
"value3": {
"description": "...",
"type": "string",
"enum": [
"a",
"b",
"c"
]
}
}
},
"owners": [
"walter.white@example.com",
"walter.grey@example.com",
"walter.black@example.com"
]
}
Responses
Status | Description |
---|---|
200 | OK |
OK. The integration definition was marked as rejected. | |
Schema: integrationDefinition | |
202 | Accepted |
Accepted. The request to reject an integration definition was accepted. | |
Schema: integrationDefinition |
Status | Description |
---|---|
400 | Bad Request |
Bad Request. The request body, request headers, and/or query parameters are not well-formed. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
401 | Unauthorized |
Unauthorized. The operation requires authentication but no authentication or insufficient authentication was given. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
403 | Forbidden |
Forbidden. The authenticated caller is not authorized to perform the requested operation. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
404 | Not Found |
Not found. There is no such resource at the request URL. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
409 | Conflict |
Conflict. This problem responsemay have one of the following
| |
Schema: problemResponse |
Status | Description |
---|---|
429 | Too Many Requests |
Too Many Requests. The client has sent too many requests in a given amount of time. This problem responsemay have one of the following
| |
Schema: Inline |
Status | Description |
---|---|
4XX | Unknown |
Client Request Problem. The client request had a problem not listed under another specific 400-level HTTP response code. View the detail in the problem response for additional details. | |
Schema: Inline |
Status | Description |
---|---|
5XX | Unknown |
Server Problem. The server encountered a problem not listed under another specific 500-level HTTP response code. View the detail in the problem response for additional details. | |
Schema: Inline |
Response Schema
Status Code 400
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 401
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 403
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 404
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 429
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 4XX
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Status Code 5XX
Property Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
» type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" . maxLength: 2048 |
» title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type . maxLength: 120 |
» status | The HTTP status code for this occurrence of the problem. minimum: 100 maximum: 599 |
» detail | A human-readable explanation specific to this occurrence of the problem. maxLength: 256 |
» instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment maxLength: 2048 |
» id | The unique identifier for this problem. This is an immutable opaque string. minLength: 6 maxLength: 48 pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$ |
» occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. minLength: 20 maxLength: 30 |
» problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 |
» attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
Schemas
apiProblem
{
"id": "3fbad566-be86-4b22-9ba6-3ca99fdc0799",
"type": "https://production.api.apiture.com/errors/accountNotFound/v1.0.0",
"title": "Account Not Found",
"status": 422,
"occurredAt": "2022-04-25T12:42:21.375Z",
"detail": "No account exists at the given account_url",
"instance": "https://production.api.apiture.com/banking/transfers/bb709151-575041fcd617"
}
API Problem (v1.2.1)
API problem or error, as per RFC 7807 application/problem+json.
Properties
Name | Description |
---|---|
API Problem (v1.2.1) | API problem or error, as per RFC 7807 application/problem+json. |
type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" .format: uri-reference maxLength: 2048 |
title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type .format: text maxLength: 120 |
status | The HTTP status code for this occurrence of the problem. format: int32 minimum: 100 maximum: 599 |
detail | A human-readable explanation specific to this occurrence of the problem. format: text maxLength: 256 |
instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment format: uri-reference maxLength: 2048 |
id | The unique identifier for this problem. This is an immutable opaque string. read-only minLength: 6 maxLength: 48 pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$" |
occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC.read-only format: date-time minLength: 20 maxLength: 30 |
problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 items: object |
challengeFactor
{
"type": "sms",
"labels": [
"9876"
]
}
Challenge Factor (v1.2.1)
A challenge factor. See requiredIdentityChallenge
for multiple examples.
Properties
Name | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Challenge Factor (v1.2.1) | A challenge factor. See requiredIdentityChallenge for multiple examples. | ||||||||||||
id | The ID of an a challenge factor. This ID is unique within the challenge factors associated with a challenge. The client should pass this id value as the factorId when starting or verifying a challenge factor. Note: The | ||||||||||||
type | (required) The name of challenge factor.
enum values: sms , email , voice , securityQuestions , authenticatorToken | ||||||||||||
labels | array: [ A list of text label which identifies the channel(s) through which the user completes the challenge. For an sms or voice challenge, the only label item is the last four digits of the corresponding phone number. For an email challenge, each label is the masked email address.minItems: 1 maxItems: 4 items: string(text) » format: text » maxLength: 300 | ||||||||||||
securityQuestions | Describes a securityQuestions challenge. This is omitted if the challenge type is not securityQuestions . |
challengeFactorId
"string"
Challenge Factor ID (v1.0.0)
The ID of an a challenge factor. This ID is unique within the factors offered with a challenge.
type:
string
minLength: 3
maxLength: 48
pattern: "^[-a-zA-Z0-9$_]{3,48}$"
challengeFactorType
"sms"
Challenge Factor Type (v1.0.0)
The name of challenge factor.
challengeFactorType
strings may have one of the following enumerated values:
Value | Description |
---|---|
sms | SMS: One-time passcode sent to the primary mobile phone number |
email | Email: One-time passcode sent to the primary email address |
voice | Voice: One-time passcode communicated via automated voice phone call |
authenticatorToken | authenticator Token: One-time passcode issued by a pre-registered hardware device, such as a token key fob, or an authenticator app |
securityQuestions | Security Questions: Prompt with the user's security questions registered with their security profile |
type:
string
enum values: sms
, email
, voice
, securityQuestions
, authenticatorToken
challengeOperationId
"string"
Challenge Operation ID (v1.0.1)
The ID of an operation/action for which the user must verify their identity via an identity challenge. This is passed when starting a challenge factor or when validating the identity challenge responses.
type:
string
minLength: 6
maxLength: 48
pattern: "^[-a-zA-Z0-9$_]{6,48}$"
challengePromptId
"string"
Challenge Prompt ID (v1.0.0)
The unique ID of a prompt (such as a security question) in a challenge factor.
type:
string
minLength: 1
maxLength: 48
pattern: "^[-_:.~$a-zA-Z0-9]+$"
challengeSecurityQuestion
{
"id": "74699fa628911e762ea5",
"prompt": "What is your mother's maiden name?"
}
Challenge Security Question (v1.0.1)
A single security question within the questions
array of the challengeSecurityQuestions
Properties
Name | Description |
---|---|
Challenge Security Question (v1.0.1) | A single security question within the questions array of the challengeSecurityQuestions |
id | (required) The unique ID of security question prompt. This should be included in the challengeVerification response as the promptId .minLength: 1 maxLength: 48 pattern: "^[-_:.~$a-zA-Z0-9]+$" |
prompt | (required) The text prompt of this security question. format: text maxLength: 80 |
challengeSecurityQuestions
{
"questions": [
{
"id": "q1",
"prompt": "What is your mother's maiden name?"
},
{
"id": "q4",
"prompt": "What is your high school's name?"
},
{
"id": "q9",
"prompt": "What is the name of your first pet?"
}
]
}
Challenge Security Questions (v1.0.1)
Describes a securityQuestions
challenge. This is omitted if the challenge type
is not securityQuestions
.
Properties
Name | Description |
---|---|
Challenge Security Questions (v1.0.1) | Describes a securityQuestions challenge. This is omitted if the challenge type is not securityQuestions . |
questions | array: (required) The array of security questions. minItems: 1 maxItems: 8 items: object |
institutionId
"TIBURON"
Institution ID (v1.1.0)
The unique immutable identifier of a financial institution.
type:
string
minLength: 2
maxLength: 8
pattern: "^[A-Z0-9_]{2,8}$"
integrationDefinition
{
"id": "FINTECH1_MODEL",
"description": "Fintech1 Financial Modeling Integration",
"staged": false,
"state": "active",
"activeInstanceCount": 14,
"label": "Fintech1 Financial Modeling",
"mobileLabel": "Fintech1 Financial Modeling",
"usesSpecificCustomerId": true,
"specificCustomerIdLabel": "Customer Id",
"specificCustomerIdDescription": "Customer Id",
"availability": {
"web": true,
"mobile": true,
"retail": true,
"commercial": true,
"institutions": "single"
},
"environmentId": "04833ea3-fbe0-43ac-95f8-188f59461ad5",
"institutionId": "TCF",
"partnerId": "3rdpartybank.com",
"code": "createSAMLRequest(user: UserData, param: Parameters, integration: Integration) {\n integration.assertions.add('answer', '42');\n}",
"audienceUrl": "https://my.audience.com/",
"defaultRelayState": "RelStat123",
"signatureAlgorithm": "RSA-SHA256",
"digestAlgorithm": "SHA256",
"encryptionAlgorithm": "AES256-GCM",
"assertionEncryptionSupported": true,
"serviceProviderMetadataUrl": "https://my.audience.com/saml/metadata.xml",
"serviceProviderHostsMetadata": true,
"targetMethod": "SAML-POST",
"targetUrlTemplate": "https://my-integration.example.com/sp/saml?cust=%7B%7BinstitutionId%7D%7D",
"parameterSchema": {
"type": "object",
"properties": {
"value1": {
"description": "...",
"type": "string",
"format": "text",
"minLength": 1,
"maxLength": 200
},
"value2": {
"description": "...",
"type": "integer",
"format": "int32",
"minimum": 1,
"maximum": 100
},
"value3": {
"description": "...",
"type": "string",
"enum": [
"a",
"b",
"c"
]
}
}
},
"owners": [
"walter.white@example.com",
"walter.grey@example.com",
"walter.black@example.com"
]
}
Integration Definition (v4.0.0)
The definition of a third party integration.
Properties
Name | Description | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Integration Definition (v4.0.0) | The definition of a third party integration. | ||||||||||||||
description | (required) The description of the client application. format: text minLength: 4 maxLength: 4000 | ||||||||||||||
label | (required) The label to be used in the online banking web client menu. format: text minLength: 4 maxLength: 128 | ||||||||||||||
mobileLabel | The label to be used in the mobile banking application, if different from the label .format: text minLength: 4 maxLength: 128 | ||||||||||||||
availability | (required) Defines the run-time contexts in which this integration is available. | ||||||||||||||
audienceUrl | The audience URL for the SAML request. format: uri maxLength: 255 | ||||||||||||||
defaultRelayState | (required) The default relay state for the SAML request. format: text maxLength: 255 | ||||||||||||||
signatureAlgorithm | The signature algorithm used for the SAML request. The value has to match one of the signatureAlgorithms returned by getSupportedIntegrationParameters .maxLength: 15 pattern: "^[-a-zA-Z0-9-_ ]{0,15}$" | ||||||||||||||
digestAlgorithm | The digest / hash algorithm used for the SAML request. The value has to match one of the digestAlgorithms returned by getSupportedIntegrationParameters .maxLength: 15 pattern: "^[-a-zA-Z0-9-_ ]{0,15}$" | ||||||||||||||
encryptionAlgorithm | The encryption algorithm used for the SAML request. The value has to match one of the encryptionAlgorithms returned by getSupportedIntegrationParameters .maxLength: 15 pattern: "^[-a-zA-Z0-9-_ ]{0,15}$" | ||||||||||||||
assertionEncryptionSupported | true if this integration supports assertion value encryption. | ||||||||||||||
serviceProviderHostsMetadata | If true , the SAML metadata at the serviceProviderMetadataUrl is hosted by the service provider. If false , the serviceProviderMetadataUrl represents a relative path. | ||||||||||||||
serviceProviderMetadataUrl | The SAML Metadata URL for the service provider integration target. When serviceProviderHostsMetadata is false , this is assumed to point to an URL hosted by the Apiture platform provider,format: uri-reference minLength: 1 maxLength: 255 | ||||||||||||||
parameterSchema | JSON schema defining custom integration parameters required by the integration. The integration instance values for these parameters are configured in the financial institution admin application. | ||||||||||||||
requiredProperties | array: Additional properties, separate from customer, institution, integration and environment properties, that this integration requires to be set. Each value has to match the name of one of the additionalProperties returned by getSupportedIntegrationParameters .maxItems: 100 items: string » minLength: 2 » maxLength: 32 » pattern: "^[a-zA-Z][a-zA-Z0-9]{1,31}$" | ||||||||||||||
usesSpecificCustomerId | (required) If true , the integration uses an integration-specific customer identifier. A value for an integration-specific customer identifier has to be provided when defining an integration instance in the administation API. | ||||||||||||||
specificCustomerIdLabel | Label for the integration-specific customer identifier shown in the financial institution admin application. when defining an integration instance in the administation API. Required if usesSpecificCustomerId is true .format: text minLength: 1 maxLength: 255 | ||||||||||||||
specificCustomerIdDescription | Description for the integration-specific customer identifier when defining an integration instance in the administation API. Required if usesSpecificCustomerId is true .format: text minLength: 1 maxLength: 255 | ||||||||||||||
targetUrlTemplate | The URL template to redirect or post to (depending on the targetMethod ). The URL template string may contain one or more of the substitution variables {<span/>{base64Saml}<span/>} , {<span/>{institutionId}<span/>} , {<span/>{configuration.<name>}<span/>} ,{<span/>{vendorCustId}<span/>} . The respective value(s) for the variable is replaced at runtime. For example, when the configuration for vendorCustomerId for an instance is set to fin in the financial institution admin application, The URL https://{<span/>{configuration.vendorCustomerId}<span/>}.foo.com/ translates to https://fin.foo.com/ .format: uri minLength: 1 maxLength: 255 | ||||||||||||||
targetMethod | The method used to provide the data to the integration target. The value has to match one of the targetMethods returned by getSupportedIntegrationParameters .minLength: 1 maxLength: 15 pattern: "^[-a-zA-Z0-9-_ ]{0,15}$" | ||||||||||||||
owners | array: [ A list of people who are owners of this webhook client. Only owners may update (including modifying the list of owners) or delete a webhook client. The array elements are email addresses (normalized to lowercase). minItems: 1 maxItems: 8 items: string(email) » format: email » maxLength: 255 | ||||||||||||||
createdAt | The date-time when this resource was created, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. This is derived and immutable.read-only format: date-time minLength: 20 maxLength: 30 | ||||||||||||||
updatedAt | The date-time when the resource was last updated, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. This is derived and immutable.read-only format: date-time minLength: 20 maxLength: 30 | ||||||||||||||
partnerId | (required) Opaque partner identifier associated with the integration definition. The identifier is only used for logging and filtering purposes. minLength: 6 maxLength: 48 pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$" | ||||||||||||||
state | (required) The state of a partner's integration definition. The default state is
enum values: pending , disabled , active , submitted , inactive , rejected | ||||||||||||||
activeInstanceCount | The number of active (not disabled) integration instances configured for this integration definition. Integration definitions that have an activeInstanceCount greater than 0 cannot be deleted.format: int32 minimum: 0 maximum: 10000 | ||||||||||||||
environmentId | The unique identifier of the API Environment (financial institution and stage) where the integration is to be deployed. Only applicable if availability.institutions is single . The caller must have permission to deploy integrations in the environment.minLength: 6 maxLength: 48 pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$" | ||||||||||||||
institutionId | The unique identifier of the financial institution the integration definition is executed for. The identifier is used for logging purposes. Only applicable if availability.institutions is single . This is derived from the institutionId .minLength: 2 maxLength: 8 pattern: "^[A-Z0-9_]{2,8}$" | ||||||||||||||
id | (required) The unique, human-readable identifier for the integration definition. minLength: 2 maxLength: 16 pattern: "^[A-Z0-9_]{2,16}$" | ||||||||||||||
staged | (required) If true , the integration definition is staged for deployemnt but not live in production. If false , this is the live, deployed version of an integration definition. | ||||||||||||||
code | TypeScript code to compute the SAML request assertion values from input data. format: text maxLength: 102400 |
integrationDefinitionAvailability
{
"web": true,
"mobile": true,
"retail": true,
"commercial": true,
"institutions": "single"
}
Integration Definition Availability (v2.0.0)
Defines the run-time contexts in which this integration is available.
Properties
Name | Description | ||||||
---|---|---|---|---|---|---|---|
Integration Definition Availability (v2.0.0) | Defines the run-time contexts in which this integration is available. | ||||||
web | (required) The integration is available within the online banking (web) client application. | ||||||
mobile | (required) The integration is available within the mobile application. | ||||||
retail | (required) The integration is available to retail (personal) banking customers. | ||||||
commercial | (required) The integration is available to commercial (business and small business) customers. | ||||||
institutions | (required) Integration Definition Visibility.
enum values: single , all |
integrationDefinitionId
"ULTRA_PAY"
Integration Definition Identifier (v1.0.0)
The unique, human-readable identifier for the integration definition.
type:
string
minLength: 2
maxLength: 16
pattern: "^[A-Z0-9_]{2,16}$"
integrationDefinitionInstitutionAvailability
"single"
Integration Definition Visibility (v1.0.0)
Integration Definition Visibility.
integrationDefinitionInstitutionAvailability
strings may have one of the following enumerated values:
Value | Description |
---|---|
single | Single Institution: The integration is only available to a single financial institution |
all | All Institutions: The integration is available to all financial institutions |
type:
string
enum values: single
, all
integrationDefinitionItem
{
"id": "ULTRA_PAY",
"description": "Fintech1 SSO Integration",
"staged": false,
"state": "active",
"activeInstanceCount": 14,
"label": "Fintech1 SSO Integration",
"mobileLabel": "Fintech1 feature",
"usesSpecificCustomerId": true,
"specificCustomerIdLabel": "Customer ID",
"specificCustomerIdDescription": "Unique Fintech1 Customer ID (GUID)",
"availability": {
"web": true,
"mobile": true,
"retail": true,
"commercial": true,
"institutions": "single"
},
"environmentId": "04833ea3-fbe0-43ac-95f8-188f59461ad5",
"institutionId": "TCF",
"partnerId": "3rdpartybank.com",
"code": "createSAMLRequest(user: UserData, param: Parameters, integration: Integration) {\n integration.assertions.add('answer', '42');\n}",
"audienceUrl": "https://my.audience.com/",
"defaultRelayState": "RelStat123",
"signatureAlgorithm": "RSA-SHA256",
"digestAlgorithm": "SHA256",
"encryptionAlgorithm": "AES256-GCM",
"assertionEncryptionSupported": true,
"serviceProviderMetadataUrl": "https://my.audience.com/saml/metadata.xml",
"serviceProviderHostsMetadata": true,
"targetMethod": "SAML-POST",
"targetUrlTemplate": "https://my-integration.example.com/sp/saml?cust=%7B%7BinstitutionId%7D%7D",
"parameterSchema": {
"type": "object",
"properties": {
"value1": {
"description": "...",
"type": "string",
"format": "text",
"minLength": 1,
"maxLength": 200
},
"value2": {
"description": "...",
"type": "integer",
"format": "int32",
"minimum": 1,
"maximum": 100
},
"value3": {
"description": "...",
"type": "string",
"enum": [
"a",
"b",
"c"
]
}
}
},
"owners": [
"walter.white@example.com",
"walter.grey@example.com",
"walter.black@example.com"
],
"createdAt": "2021-10-30T19:06:04.250Z",
"updatedAt": "2021-10-30T19:06:04.250Z",
"createdBy": "fintechdev_01"
}
Integration Definition Item (v3.0.0)
Integration definition item within collections/lists.
Properties
Name | Description | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Integration Definition Item (v3.0.0) | Integration definition item within collections/lists. | ||||||||||||||
createdAt | (required) The date-time when this resource was created, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. This is derived and immutable.read-only format: date-time minLength: 20 maxLength: 30 | ||||||||||||||
updatedAt | The date-time when the resource was last updated, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC. This is derived and immutable.read-only format: date-time minLength: 20 maxLength: 30 | ||||||||||||||
description | (required) The description of the client application. format: text maxLength: 4000 | ||||||||||||||
label | The label to be used in the online banking web client menu. format: text minLength: 4 maxLength: 128 | ||||||||||||||
mobileLabel | The label to be used in the mobile banking application, if different from the label .format: text minLength: 4 maxLength: 128 | ||||||||||||||
availability | Indicates if the integration definition can be used by any institution. or only one institution. | ||||||||||||||
audienceUrl | The audience URL for the SAML request. format: uri maxLength: 255 | ||||||||||||||
defaultRelayState | The default relay state for the SAML request. format: text maxLength: 255 | ||||||||||||||
signatureAlgorithm | The signature algorithm used for the SAML request. The value has to match one of the signatureAlgorithms returned by getSupportedIntegrationParameters .maxLength: 15 pattern: "^[-a-zA-Z0-9-_ ]{0,15}$" | ||||||||||||||
digestAlgorithm | The digest / hash algorithm used for the SAML request. The value has to match one of the digestAlgorithms returned by getSupportedIntegrationParameters .maxLength: 15 pattern: "^[-a-zA-Z0-9-_ ]{0,15}$" | ||||||||||||||
encryptionAlgorithm | The encryption algorithm used for the SAML request. The value has to match one of the encryptionAlgorithms returned by getSupportedIntegrationParameters .maxLength: 15 pattern: "^[-a-zA-Z0-9-_ ]{0,15}$" | ||||||||||||||
assertionEncryptionSupported | true if this integration supports assertion value encryption. | ||||||||||||||
serviceProviderHostsMetadata | (required) If true , the SAML metadata at the serviceProviderMetadataUrl is hosted by the service provider. If false , the serviceProviderMetadataUrl represents a relative path. | ||||||||||||||
serviceProviderMetadataUrl | The SAML Metadata URL for the service provider integration target. When serviceProviderHostsMetadata is false , this is assumed to point to an URL hosted by the Apiture platform provider,format: uri-reference minLength: 1 maxLength: 255 | ||||||||||||||
parameterSchema | JSON schema defining custom integration parameters required by the integration. The integration instance values for these parameters are configured in the financial institution admin application. | ||||||||||||||
requiredProperties | array: Additional properties, separate from customer, institution, integration and environment properties, that this integration requires to be set. Each value has to match the name of one of the additionalProperties returned by getSupportedIntegrationParameters .maxItems: 100 items: string » minLength: 2 » maxLength: 32 » pattern: "^[a-zA-Z][a-zA-Z0-9]{1,31}$" | ||||||||||||||
usesSpecificCustomerId | If true , the integration uses an integration-specific customer identifier. A value for an integration-specific customer identifier has to be provided when defining an integration instance in the administation API. | ||||||||||||||
specificCustomerIdLabel | Label for the integration-specific customer identifier shown in the financial institution admin application. when defining an integration instance in the administation API. Required if usesSpecificCustomerId is true .format: text minLength: 1 maxLength: 255 | ||||||||||||||
specificCustomerIdDescription | Description for the integration-specific customer identifier when defining an integration instance in the administation API. Required if usesSpecificCustomerId is true .format: text minLength: 1 maxLength: 255 | ||||||||||||||
targetUrlTemplate | The URL template to redirect or post to (depending on the targetMethod ). The URL template string may contain one or more of the substitution variables {<span/>{base64Saml}<span/>} , {<span/>{institutionId}<span/>} , {<span/>{configuration.<name>}<span/>} ,{<span/>{vendorCustId}<span/>} . The respective value(s) for the variable is replaced at runtime. For example, when the configuration for vendorCustomerId for an instance is set to fin in the financial institution admin application, The URL https://{<span/>{configuration.vendorCustomerId}<span/>}.foo.com/ translates to https://fin.foo.com/ .format: uri minLength: 1 maxLength: 255 | ||||||||||||||
targetMethod | The method used to provide the data to the integration target. The value has to match one of the targetMethods returned by getSupportedIntegrationParameters .minLength: 1 maxLength: 15 pattern: "^[-a-zA-Z0-9-_ ]{0,15}$" | ||||||||||||||
owners | array: [ A list of people who are owners of this webhook client. Only owners may update (including modifying the list of owners) or delete a webhook client. The array elements are email addresses (normalized to lowercase). minItems: 1 maxItems: 8 items: string(email) » format: email » maxLength: 255 | ||||||||||||||
partnerId | (required) Opaque partner identifier associated with the integration definition. The identifier is only used for logging and filtering purposes. minLength: 6 maxLength: 48 pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$" | ||||||||||||||
state | (required) The state of a partner's integration definition. The default state is
enum values: pending , disabled , active , submitted , inactive , rejected | ||||||||||||||
activeInstanceCount | The number of active (not disabled) integration instances configured for this integration definition. Integration definitions that have an activeInstanceCount greater than 0 cannot be deleted.format: int32 minimum: 0 maximum: 10000 | ||||||||||||||
environmentId | The unique identifier of the API Environment (financial institution and stage) where the integration is to be deployed. Only applicable if availability.institutions is single . The caller must have permission to deploy integrations in the environment.minLength: 6 maxLength: 48 pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$" | ||||||||||||||
institutionId | The unique identifier of the financial institution the integration definition is executed for. The identifier is used for logging purposes. Only applicable if availability.institutions is single . This is derived from the institutionId .minLength: 2 maxLength: 8 pattern: "^[A-Z0-9_]{2,8}$" | ||||||||||||||
id | (required) The unique, human-readable identifier for the integration definition. minLength: 2 maxLength: 16 pattern: "^[A-Z0-9_]{2,16}$" | ||||||||||||||
staged | (required) If true , the integration definition is a staged for deployemnt. If false , this is the live, deployed version of an integration definition. | ||||||||||||||
createdBy | (required) Opaque identifier representing the partner user that created the integration definition. The identifier is only used for logging and filtering purposes. minLength: 6 maxLength: 48 pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$" |
integrationDefinitions
{
"items": [
{
"id": "ULTRA_PAY",
"createdAt": "2021-10-30T19:06:04.250Z",
"updatedAt": "2021-10-30T19:06:04.250Z",
"partnerId": "3rdpartybank.com",
"state": "active",
"staged": false,
"activeInstanceCount": 14,
"description": "string",
"availability": {
"web": true,
"mobile": true,
"retail": true,
"commercial": true,
"institutions": "single"
},
"createdBy": "fintechdev_01",
"assertionEncryptionSupported": true,
"serviceProviderMetadataUrl": "https://my.audience.com/saml/metadata.xml",
"serviceProviderHostsMetadata": true
}
]
}
Integration definition collection (v3.0.0)
Collection of integration definition items.
Properties
Name | Description |
---|---|
Integration definition collection (v3.0.0) | Collection of integration definition items. |
items | array: (required) An array containing integration summary items. maxItems: 1000 items: object |
integrationPropertyName
"string"
Integration Property Name (v1.0.0)
The name of a data property that may be assigned in an integration.
type:
string
minLength: 2
maxLength: 32
pattern: "^[a-zA-Z][a-zA-Z0-9]{1,31}$"
jsonObject
{}
JSON Object (v1.0.0)
A JSON object.
Properties
Name | Description |
---|---|
JSON Object (v1.0.0) | A JSON object. |
partnerIntegrationDefinitionState
"pending"
Partner Integration Definition State (v1.0.0)
The state of a partner's integration definition. The default state is pending
. The definition state must be active
before integration instances may be created from it.
partnerIntegrationDefinitionState
strings may have one of the following enumerated values:
Value | Description |
---|---|
pending | Pending: A new integration definition that has not been submitted, approved, or rejected. |
disabled | Disabled: Disabled by the integration definition owner. No new integration instances may be created until the owner enables the integration definition. |
rejected | Rejected: An integration definition that has been rejected by an administrator. Owners cannot change the state of a rejected integration definition. |
active | Active: The integration definition has been approved and is available for creating new integration instances. |
inactive | Inactive: An integration definition that has been marked as inactive by an administrator, for potential fraud, security, or other reasons. Owners cannot change the state of an inactive integration definition. |
submitted | Submitted: The integration definition has been submitted for Apiture and financial institution review. |
type:
string
enum values: pending
, disabled
, active
, submitted
, inactive
, rejected
problemResponse
{
"id": "3fbad566-be86-4b22-9ba6-3ca99fdc0799",
"type": "https://production.api.apiture.com/errors/noSuchAccount/v1.0.0",
"title": "Account Not Found",
"status": 422,
"occurredAt": "2022-04-25T12:42:21.375Z",
"detail": "No account exists for the given account reference",
"instance": "https://production.api.apiture.com/banking/transfers/bb709151-575041fcd617"
}
Problem Response (v0.4.1)
API problem or error response, as per RFC 9457 application/problem+json.
Properties
Name | Description |
---|---|
Problem Response (v0.4.1) | API problem or error response, as per RFC 9457 application/problem+json. |
type | A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank" .format: uri-reference maxLength: 2048 |
title | A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type .format: text maxLength: 120 |
status | The HTTP status code for this occurrence of the problem. format: int32 minimum: 100 maximum: 599 |
detail | A human-readable explanation specific to this occurrence of the problem. format: text maxLength: 256 |
instance | A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment format: uri-reference maxLength: 2048 |
id | The unique identifier for this problem. This is an immutable opaque string. read-only minLength: 6 maxLength: 48 pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$" |
occurredAt | The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC.read-only format: date-time minLength: 20 maxLength: 30 |
problems | array: Optional root-causes if there are multiple problems in the request or API call processing. maxItems: 128 items: object |
attributes | Additional optional attributes related to the problem. This data conforms to the schema associated with the error type. |
readOnlyResourceId
"string"
Read-only Resource Identifier (v1.0.1)
The unique, opaque system-assigned identifier for a resource. This case-sensitive ID is also used in URLs as path parameters or in other properties or parameters that reference a resource by ID rather than URL. Resource IDs are immutable.
type:
string
read-only
minLength: 6
maxLength: 48
pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$"
readOnlyTimestamp
"2021-10-30T19:06:04.250Z"
Read-Only Timestamp (v1.0.0)
A readonly or derived timestamp (an instant in time) formatted in RFC 3339 date-time
UTC format: YYYY-MM-DDThh:mm:ss.sssZ
.
type:
string(date-time)
read-only
format: date-time
minLength: 20
maxLength: 30
requiredIdentityChallenge
{
"operationId": "createTransfer",
"challengeId": "0504076c566a3cf7009c",
"factors": [
{
"type": "sms",
"labels": [
"9876"
],
"id": "85c0ee5753fcd0b0953f"
},
{
"type": "voice",
"labels": [
"9876"
],
"id": "d089e10a80a8627df37b"
},
{
"type": "voice",
"labels": [
"6754"
],
"id": "10506ecf9d1c2ee00403"
},
{
"type": "email",
"labels": [
"an****nk@example.com",
"an****98@example.com"
],
"id": "e917d671cb2f030b56f1"
},
{
"type": "authenticatorToken",
"labels": [
"Acme fob"
],
"id": "fe6c452d7da0bbb4e407"
},
{
"type": "securityQuestions",
"securityQuestions": {
"questions": [
{
"id": "q1",
"prompt": "What is your mother's maiden name?"
},
{
"id": "q4",
"prompt": "What is your high school's name?"
},
{
"id": "q9",
"prompt": "What is the name of your first pet?"
}
]
},
"id": "df33c6f88a37d6b3f0a6"
}
]
}
Required Challenge (v1.2.3)
A request from the service for the user to verify their identity. This contains a challenge ID, the corresponding operation ID, and a list of challenge factors for identity verification. The user must complete one of these challenge factors to satisfy the challenge. This schema defines the attributes in the 401 Unauthorized problem response when the 401 problem type name is challengeRequired
. See the "Challenge API" for details.
Properties
Name | Description |
---|---|
Required Challenge (v1.2.3) | A request from the service for the user to verify their identity. This contains a challenge ID, the corresponding operation ID, and a list of challenge factors for identity verification. The user must complete one of these challenge factors to satisfy the challenge. This schema defines the attributes in the 401 Unauthorized problem response when the 401 problem type name is challengeRequired . See the "Challenge API" for details. |
operationId | (required) The ID of an operation/action for which the user must verify their identity via an identity challenge. This is passed when starting a challenge factor or when validating the identity challenge responses. minLength: 6 maxLength: 48 pattern: "^[-a-zA-Z0-9$_]{6,48}$" |
challengeId | (required) The unique ID of this challenge instance. This is an opaque string. This is passed when starting a challenge factor or when validating the identity challenge responses. read-only minLength: 6 maxLength: 48 pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$" |
factors | array: (required) A list of challenge factors. The user must complete one of these challenge factors. The labels in each factor identify one or more channels the user may use, such as a list of email addresses the system may use to send a one-time passcode to the user. *Note: The same channel may be used by multiple factors in the array of factors. For example, the user's primary mobile phone number may be used for both an sms factor and a voice factor.minItems: 1 maxItems: 8 items: object |
resourceId
"string"
Resource Identifier (v1.0.1)
The unique, opaque system identifier for a resource. This case-sensitive ID is also used as path parameters in URLs or in other properties or parameters that reference a resource by ID rather than URL.
type:
string
minLength: 6
maxLength: 48
pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$"
@apiture/api-doc
3.2.4 on Wed Mar 26 2025 19:42:37 GMT+0000 (Coordinated Universal Time).