Enterprise Data Federation Service (EDFS)
Download API definition:
This API is a Technical Preview and is available for testing purposes only. Do not use in production.
POST https://api.bentley.com/edfs/itwins/{iTwinId}/packages/{uniqueName}

Execute the specified integration package for the specified iTwin. Other integration package specific variables can be provided in the body.

To get an example of input for each integration package you can retrieve the details

Authentication

Requires Authorization header with valid Bearer token for scope itwin-platform.

For more documentation on authorization and how to get access token visit OAUTH2 Authorization page.

Authorization

User must have the EDFS Execute Integration Package role assigned at the iTwin level or be an Organization Administrator for the Organization that owns a given iTwin. Package role assignments can be set

Request parameters

Name
Required?
Description
iTwinId
Yes

The iTwin project ID

uniqueName
Yes

The unique name of integration package

Request headers

Name
Required?
Description
Authorization
Yes

OAuth access token with itwin-platform scope

Accept
Yes

Setting to application/vnd.bentley.itwin-platform.v1+json is recommended.

Request body

ExecuteProjectPost

Name
Type
Required?
Description
returnAsXml
Boolean
No

If true, the response will be returned as XML. If false, the response will be returned as JSON.

variables
No

List of possible input variables to be passed to the integration package. Described in integration package input example.

Example

json
{
    "returnAsXml": false,
    "variables": [{
            "name": "Parameter",
            "value": "Value"
        },
        {
            "name": "Setting",
            "value": "Value2"
        }
    ]
}

Response 200 OK

OK

json
{
    "data": [{
        "customerID": "ACME ",
        "companyName": "ACME Ltd.",
        "contactName": "Joe Bloggs"
    }]
}

Response 401 Unauthorized

This response indicates that request lacks valid authentication credentials. Access token might not been provided, issued by the wrong issuer, does not have required scopes or request headers were malformed.

json
{
    "error": {
        "code": "HeaderNotFound",
        "message": "Header Authorization was not found in the request. Access denied."
    }
}

Response 403 Forbidden

The user has insufficient permissions for the requested operation.

json
{
    "error": {
        "code": "InsufficientPermissions",
        "message": "The user has insufficient permissions for the requested operation."
    }
}

Response 422 Unprocessable Entity

The 422 (Unprocessable Entity) status code indicates that the request cannot be processed by the server due to a client error (e.g. malformed request syntax)

json
{
    "error": {
        "code": "InvalidPackageDataRequest",
        "message": "Cannot retrieve PackageData.",
        "details": [{
                "code": "InvalidValue",
                "message": "Provided iTwin ID value is not valid.",
                "target": "iTwinId"
            },
            {
                "code": "InvalidValue",
                "message": "Provided Unique Name value contains invalid characters.",
                "target": "uniqueName"
            }
        ]
    }
}

Response 429 Too many requests

This response indicates that the user has sent too many requests in a given amount of time.

json
{
    "error": {
        "code": "TooManyRequests",
        "message": "More requests were received than the subscription rate-limit allows."
    }
}

Response headers

Name
Description
retry-after

The number of requests exceeds the rate-limit for the client subscription.

ExecuteProjectVariable

Name
Type
Description
name
String

Name of the input variable described in integration package input example.

value
String

Value of the input variable.

ExecuteProjectPost

Name
Type
Description
returnAsXml
Boolean

If true, the response will be returned as XML. If false, the response will be returned as JSON.

variables

List of possible input variables to be passed to the integration package. Described in integration package input example.

ExecutePostExample

Name
Type
Description
data
Object[]

Data result. Described in integration package response example.

DetailedError

Contains error information and an array of more specific errors.

Name
Type
Description
code
String

One of a server-defined set of error codes.

message
String

A human-readable representation of the error.

target
String, null

The target of the error.

details

Optional array of more specific errors.

Detailed Error Response

Gives details for an error that occurred while handling the request. Note that clients MUST NOT assume that every failed request will produce an object of this schema, or that all of the properties in the response will be non-null, as the error may have prevented this response from being constructed.

Name
Type
Description
error

Error Detailed information.

Error

Contains error information.

Name
Type
Description
code
String

One of a server-defined set of error codes.

message
String

A human-readable representation of the error.

target
String, null

The target of the error.

Error Response

Gives details for an error that occurred while handling the request. Note that clients MUST NOT assume that every failed request will produce an object of this schema, or that all of the properties in the response will be non-null, as the error may have prevented this response from being constructed.

Name
Type
Description
error

Error information.

Was this page helpful?