Enhanced interface

Web Services authorizations

Take control of who makes Web Services requests to your company with Web Services authorizations.

To change your company security features and settings, go to Company > Setup > Configuration > Company > Security tab, then select Edit.

About Web Services authorizations

Use the Web Services authorizations list to control which sender IDs can and cannot make Web Services requests to your company. If a sender ID is not on this list, any Web Services requests they make to your company will fail. For this reason, it is important to review your regular Web Services activity and integrations to ensure the proper sender IDs are on your authorization list.

You may also run into Web Services authorization problems when running page scripts from Platform Services using the AJAX gateway. To remedy this problem, simply add the sender ID ajax to your Web Services authorization list so your page scripts can continue uninterrupted.

To see who has been making Web Services requests to your company in the last 63 days, build an API Usage Detail report.

Add Web Services authorizations

You authorize specific sender IDs to make Web Services requests to your company by adding them to this list. If a sender ID is not on this list, any Web Services requests they make to your company will fail.

Companies that use the AJAX gateway from Platform Services should add ajax to their sender IDs so that their Web Services activities continue uninterrupted.

Additionally, companies that create printed document templates using the Sage Intacct Printed Document Toolbar should add the sender ID cdocs_v2 to their authorizations list. If this sender ID is not added, then users will fail to log in to the toolbar.

To add a Web Services authorization:

In the Web Services authorizations section, select Add.
On the Web Services sender information pop-up, enter a Sender ID.
Sender IDs are case sensitive and cannot be changed after the authorization is added.
Optionally, add a Description for the sender.
Be sure the status is set to Active. Inactive sender IDs aren't able to make Web Services requests to your company.
Select Save.

Deactivate or activate a Web Services authorization

Instead of completely removing a Web Services authorization record, you can instead simply inactivate. Inactive sender IDs aren't able to make Web Services requests to your company, but retains the record for your historical purposes.

Inactivating a sender ID also gives you the option to activate it again later, if your needs change. This is easier than having to re-create the record again in the future.

To inactivate or activate a Web Services authorization:

In the Web Services authorizations section, select the pencil icon along the same row as the Sender ID you want to change.
In the pop-up window, change the Status to either Inactive or Active depending on your needs.
Select Save.

Remove a Web Services authorization

If you don't recognize a sender ID on the list or you need to remove an old sender ID, you can remove the sender ID from the Web Services authorizations list. Run an API Usage Detail report to see who has made Web Services requests to your company in the last 63 days.

Some sender IDs in your list may have been from a support action of some sort in the past. Before you remove unknown sender IDs from the Web Services authorizations list, open a case in the Community and work with support to determine the source of the sender ID.

To remove a Web Services authorization:

In the Web Services authorizations section, find the sender ID you want to remove, then select the trash can icon at the end of the same row.
Select OK on the delete confirmation pop-up.

Field descriptions

Web Services authorizations field descriptions
Field	Description
Sender ID	The ID used when passing Web Services requests. Sender IDs are case sensitive and cannot be changed after creation.
Description	Describes the purpose of the sender ID authorization.
Status	The status determines if the authorization is active or inactive. Inactive sender IDs aren't able to make Web Services requests to your company.