Box Events

Axway AMPLIFY supports events via polling or webhooks depending on the API provider. For more information about our Events framework, see Events Overview.

Supported Events and Resources

Axway AMPLIFY supports webhook events for Box. For more information about webhooks at Box including the currently available webhooks, see their webhooks documentation.


To configure webhooks through the UI, follow the same steps to authenticate a connector instance, and then turn on events. Enter the webhook information, and then click Create Instance. For more information, see Authenticate a Connector Instance with Events (UI) or the connector-specific authentication topic.

Configure Webhooks Through API

Use the /instances endpoint to authenticate with Box and create a connector instance with webhooks enabled.


The endpoint returns a connector instance token and ID upon successful completion. Retain the token and ID for all subsequent requests involving this connector instance.

To authenticate a connector instance with webhooks:

  1. Get an authorization grant code by completing the steps in authenticating and authenticate.
  2. Construct a JSON body as shown below (see Parameters):

      "element": {
        "key": "box"
      "providerData": {
        "code": "<AUTHORIZATION_GRANT_CODE>"
      "configuration": {
        "oauth.callback.url": "<CALLBACK_URL>",
        "oauth.api.key": "<CONSUMER_KEY>",
        "oauth.api.secret": "<CONSUMER_SECRET>",
        "event.notification.enabled": true,
        "event.notification.callback.url": "<CALLBACK_URL>",
        "events.list.ids": "<LIST_IDS>"
      "tags": [
      "name": "<INSTANCE_NAME>"
  3. Call the following, including the JSON body you constructed in the previous step:

    POST /instances

    Make sure that you include the User and Organization keys in the header. For more information, see Authorization Headers, Organization Secret, and User Secret.

  4. Locate the token and id in the response and save them for all future requests using the connector instance.

Example cURL

curl -X POST \ \
  -H 'authorization: User <USER_SECRET>, Organization <ORGANIZATION_SECRET>' \
  -H 'content-type: application/json' \
  -d '{
  "element": {
    "key": "box"
  "providerData": {
    "code": "xoz8AFqScK2ngM04kSSM"
  "configuration": {
    "oauth.callback.url": "",
    "oauth.api.key": "xxxxxxxxxxxxxxxxxx",
    "oauth.api.secret": "xxxxxxxxxxxxxxxxxxxxxx"
    "event.notification.enabled": true,
    "event.notification.callback.url": "",
    "event.notification.signature.key": "xxxxxxxxxxxxxxxxxxxxxxxxx"
  "tags": [
  "name": "API Instance"


API parameters not shown in the Axway AMPLIFY are in code formatting.

Parameter Description Data Type
key The connector key. string
code The authorization grant code returned from the API provider in an OAuth2 authentication workflow. string
The name for the connector instance created during authentication. Body
oauth.callback.url The URL where you want to redirect users after they grant access. This is the Callback URL that you noted in the API Provider Setup section.  
oauth.api.key The Client ID from Box. This is the Client ID that you noted in the API Provider Setup section. string
oauth.api.secret The Client Secret from Box. This is the Client Secret that you noted in the API Provider Setup section. string
Events Enabled
Optional. Identifies that events are enabled for the connector instance.
Default: false.
Event Notification Callback URL
The URL where you want Axway AMPLIFY to send the events. string
Callback Notification Signature Key
Optional. A user-defined key for added security to show that events have not been tampered with. string
tags Optional. User-defined tags to further identify the instance. string

Related Links