Common AtomSphere API Errors

Document created by thanh_n88 Employee on Mar 1, 2018Last modified by thanh_n88 Employee on Jun 20, 2018
Version 3Show Document
  • View in full screen mode

Using the AtomSphere API provides programmatic access to functionality that is normally accessed through the AtomSphere application. You might run into some errors along the way, here are some common ones when using the Boomi Atomsphere connector.

Related Documentation

 

Common Errors

Sometimes errors supersede or show up before one another if there are multiple errors. For example, not having permissions to access a certain atom will supersede using an incorrect atom ID. If your atom is missing, that's more important to resolve that than not having permissions to access it. 

 

The specified user does not have API privileges on account

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

 

The authenticated user does not have access rights to this functionality

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

 

You do not have access to any containers

Full Error: [You do not have access to any containers] You do not have access to any containers

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

 

Could not find container for id {some_ID}

Full error: [Could not find container for id {some_ID}] Could not find container for id {some_ID}

Cause: You entered the wrong atom ID (or another ID) where applicable, like in the ExecutionRecord object (or equivalent)

Solution: Make sure the atom ID is correct or the corresponding thing the ID is referencing, exists

 

User Name or Password were invalid

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 AtomSphere API

 

Error invoking soap operation; Unsupported Content-Type: text/html; charset=ISO-8859-1

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

 

Nothing is happening and stops at the AtomSphere API shape

Full error: The process just stops and does not get any data

Possible causes:

  • Your parameter for the query or action do not have a corresponding result i.e. you are searching for atom D when only atom A, B, and C exist
  • Your value(s) for the parameter(s) are wrong or there's a typo
  • You are using an Action that doesn't apply to the specific object e.g. The AtomStartupProperties object only supports a GET, but you try to use a QUERY or CREATE call

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 Operations documentation

 

Unknown filter field: {property_name}

Full error: Unknown filter field: {property_name}, such as atomID

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 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 "atomId" so the property will be "atomId", however you will get the unknown filter field if you tried to use "atomID"

Attachments

    Outcomes