Using the Boomi Enterprise Platform API provides programmatic access to functionality that is normally accessed through the Boomi Enterprise Platform application. You might run into some errors along the way, here are some common ones when using the Boomi Enterprise Platform connector.
Sometimes errors supersede or show up before one another if there are multiple errors. For example, not having permissions to access a certain basic runtime will supersede using an incorrect basic runtime ID. If your basic runtime is missing, that's more important to resolve that than not having permissions to access it.
Full error: [The specified user does not have API privileges on account: {account_ID}] The specified user does not have API privileges on account: {account_ID}
Cause: The user's (the credentials provided to authenticate the API request) role does not have the API Access privilege
Solution: Add the API Access privilege to the user's role
Full error: [The authenticated user does not have access rights to this functionality] The authenticated user does not have access rights to this functionality
Cause: The user's role does not have the appropriate privilege for the object. For example, a user trying to query the ExecutionRecord object but does not have the View Results privilege will get the error
Solution: Make sure the user has the appropriate privilege for the API object
Full Error: [You do not have access to any runtimes] You do not have access to any runtimes
Cause: The user's role does not have access to the environment i.e. the role is not listed in the "Roles" field in the environment information
Solution: Add the user's role to the "Roles" field in the environment information page
Full error: [Could not find runtime for id {some_ID}] Could not find runtime for id {some_ID}
Cause: You entered the wrong basic runtime ID (or another ID) where applicable, like in the ExecutionRecord object (or equivalent)
Solution: Make sure the basic runtime ID is correct or the corresponding thing the ID is referencing, exists
Full error: [User Name or Password were invalid] User Name or Password were invalid
Cause: The username or password in the connection is wrong
Solution: Make sure it's the correct username and password combination. You cannot use the users listed in the shared web server to access the Boomi Enterprise Platform API
Full error: Error invoking soap operation; Caused by: Unsupported Content-Type: text/html; charset=ISO-8859-1 Supported ones are: [text/xml]
Cause: Your WSDL URL is incorrect in the connection, either there is a typo or the account ID doesn't exist
Solution: Make sure your WSDL looks like this, https://api.boomi.com/api/soap/v1/{Account_ID}?wsdl and/or make sure the account ID is correct/exists
Full error: The process just stops and does not get any data
Possible causes:
Solution: Make sure the information you are trying to get exists and/or check the values for the parameters are correct. See if your action exists for that object in the API Objects and Object Based Operations documentation
Full error: Unknown filter field: {property_name}, such as basic runtimeID
Cause: Your request body is using the wrong property or field for the filter
Solution: Look for your specific API object in the API Objects and Object Based Operations documentation and make sure the property you are using exists as a field listed in the documentation. For example, the ExecutionRecord object has a field called "basic runtimeId" so the property will be "basic runtimeId", however you will get the unknown filter field if you tried to use "basic runtimeID"