Find us at our new Help Center where we've combined our documentation and knowledgebase articles in one easy-to-search location.
We aren't updating the Developer Portal anymore, except for the Element Docs — all updates happen in the Help Center. We're retiring the Developer Portal as you know it in:
You can now order search results from GET /search
and GET /folders/{id}/contents
requests by name
, createdDate
, and modifiedDate
. For example:
We updated the Google suite element to support background and foreground colors.
We added the Microsoft Graph element to access the Microsoft Graph API and manage calendars and other objects.
recipients
endpoint to the envelopes
resourceYou can now GET all the recipients of an envelope using GET /envelopes/{id}/recipients
.
The following types of custom fields can be included in the POST request on Netsuite elements:
We added a new access-level
query parameter for the following endpoints:
Beginning with the Winter '18 Release, Sugar will prevent REST API access to Sugar from unknown platform types. When you authenticate an element instance, you can now pass the sugar.platform
to prevent any connection issues related to platform. See Sugar's documentation for more information.
We made several changes to security in this release including:
PUT /organizations/me
.PATCH /accounts/{id}?permanent=true { "active": false }
) behaves the same as a deletion, and all of the account users will be deleted.Previously, if you attempted to create a transformation using only Custom JS, you received an error indicating at least one field level transformation was required. You can now create a transformation exclusively through Custom JS.
files
endpoints to the folders
resourceWe added the following endpoints to the folders resource so you can manage attachments:
customers
endpointYou can now manage the customers associated with your Square element. We added the following endpoints:
bill-payments
resource included duplicate fieldsWe removed the duplicate fields. When you map bill-payments
to a common resource, you will no longer encounter duplicate fields.
placements
resourceIn the placements
resource models the clientContact
field was shown as clientcontact
. We updated the model to show the correct value.
We added a response header to indicate the total Intacct records when querying.
When you authenticate an element instance, you can now include the credentials from a converged app — an app that accepts both MSA & Azure AD sign-in. To authenticate using a converged app, you must authenticate an element instance using the APIs.
project-codes
resourceYou can now fin projects using the project-codes
resource.
You can now override the default US URLs for Authentication URL and Base URL with European URLs.
tax-rates
and tax-codes
resourcesYou can now perform CRUD operations on the tax rates and tax codes in QuickBooks Enterprise.
We enhanced POST /files
to accept a thumbnail file to associate with a file. We also added the following endpoints to update thumbnails:
Previously, authenticating via Cloud Elements 2.0 resulted in errors. You can now authenticate an instance of the Intacct. element in Cloud Elements 2.0.
To enable hash verification for bulk job callbacks, we updated the Event Notification Signature Key which is currently used to add an extra layer of security when receiving event callbacks.
In the UI, we renamed Callback Notification Signature Key to Callback Notification Signature Key. The Callback Notification Signature Key property is now available as an optional field, rather than part of event setup. If you configure the Callback Notification Signature Key, it will be used to provide hash verification in the header of bulk job and event callbacks.
The name of the configuration property event.notification.signature.key
remains unchanged. If you set it, it will be used for bulk job and event callbacks.