Skip to main content

AppFigures Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to an AppFigures location.
appfigures_api.png

AppFigures

Create an AppFigures Destination​

  1. Click the + icon on the Nexset that will be sent to the AppFigures destination, and select the Send to Destination option from the menu.

  2. Select the AppFigures connector from the list of available destination connectors. Then, select the credential that will be used to connect to the AppFigures account, and click Next; or, create a new AppFigures credential for use in this flow.

  3. In Nexla, AppFigures destinations can be created using pre-built endpoint templates, which expedite destination setup for common AppFigures endpoints. Each template is designed specifically for the corresponding AppFigures endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    AppFigures destinations can also be configured manually, allowing you to send data to AppFigures endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common AppFigures endpoints. Each template is designed specifically for the corresponding AppFigures endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Create External Account

    This endpoint creates a new external account connection in AppFigures — for example, an iTunes Connect, Google Play, or ad-network account that AppFigures will pull data from. Use it to programmatically onboard new store and ad-network connections from upstream systems.

    • Each record in the upstream Nexset must include the fields AppFigures requires to register an external account — typically a store or network identifier, the credentials needed to authenticate to that store/network (for example, a username and password, an API key, or an issuer/key pair), and any optional metadata such as a label.
    • The full record is sent as the JSON body of the POST /external_accounts call. Use the Nexla transform layer to shape upstream attributes into the field names expected by AppFigures.

    External-account credentials are sensitive. Ensure upstream Nexsets are sourced from a secure secret manager and that the destination is restricted to authorized users. For full details, see the AppFigures External Accounts reference.

    Update External Account

    This endpoint updates an existing external account in AppFigures — for example, to rotate credentials or change a label. Use it as part of a credential-rotation workflow that keeps AppFigures connections current.

    • Enter the AppFigures external account ID in the Id field. This identifies which account to update and can be obtained from the List External Accounts source endpoint or from an upstream Nexla flow.
    • The body of each PUT call is the upstream record (as JSON). Include only the fields that should be changed — omitted fields are left untouched.

    Updating credentials on an external account may temporarily interrupt data collection for the associated store or network. For complete details, see the AppFigures External Accounts reference.

    Update User Status

    This endpoint updates the active status of a specific user in your AppFigures account. Use it to drive deprovisioning or reactivation from an identity directory — for example, deactivating an AppFigures user when their account is offboarded in your IdP.

    • Enter the AppFigures user ID in the Id field. User IDs can be obtained from the List Users source endpoint.
    • The body of each PUT call is the upstream record carrying the new status fields (for example, an active boolean or a role assignment) expected by AppFigures.

    For complete details about user properties and the fields accepted on update, see the AppFigures Users API reference.

    Update a Product

    This endpoint updates properties on a specific AppFigures product — for example, toggling active status, visibility, or display metadata. Use it to keep product configuration in AppFigures in sync with a downstream system of record.

    • Enter the AppFigures product ID in the Product ID field. Product IDs can be obtained from the List My Products or Search Products source endpoints.
    • The body of each PUT call is the upstream record (as JSON). Include only the fields that should be changed.

Configure Manually​

AppFigures destinations can be manually configured to send data to any valid AppFigures API endpoint under https://api.appfigures.com/v2/. Manual configuration provides maximum flexibility for endpoints not covered by the pre-built templates — for example, account-level write endpoints or newly released API operations.

Using manual configuration, you can also configure Nexla to automatically send the response received from the AppFigures API after each call to a new Nexla webhook data source. This is useful for capturing the IDs returned by POST operations (for example, the new external account ID from Create External Account).

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the AppFigures API from the Method pulldown menu. AppFigures write endpoints use:

    • POST: For creating new resources (for example, POST /external_accounts)
    • PUT: For updating existing resources (for example, PUT /products/{'{id}'}, PUT /users/{'{id}'})
    • DELETE: For removing resources

Data Format​

  1. Select the format in which the Nexset data will be sent to the AppFigures API from the Content Format pulldown menu. The AppFigures API expects application/json for all write endpoints, so JSON is the appropriate choice for every AppFigures destination.

API Endpoint URL​

  1. Enter the URL of the AppFigures API endpoint to which you want to send the Nexset data in the URL field. All AppFigures API URLs use the base https://api.appfigures.com/v2/ followed by the resource path. For update operations, include the resource ID at the end of the URL — Nexla macros can substitute the ID from each upstream record (for example, {'https://api.appfigures.com/v2/products/{id}'}).

AppFigures only accepts requests over HTTPS. Confirm that the URL begins with https:// before testing.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (for example, header1:value1,header2:value2).

    You do not need to include any headers already present in the credentials. The Authorization header for OAuth 2.0 is added automatically based on your AppFigures credential, and Content-Type: application/json is added based on the selected Content Format.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this AppFigures destination, select the attributes from the Exclude Attributes pulldown menu. This is useful for stripping internal Nexla bookkeeping fields, or for omitting upstream IDs that AppFigures would reject as unknown.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

The AppFigures write endpoints documented above (Create External Account, Update External Account, Update User Status, Update a Product) operate on a single resource per request and do not natively support batched create/update calls. Record batching is therefore best left disabled for AppFigures destinations.

  1. To override the default and group records into a single batched payload anyway, check the box next to Would you like to batch your records together?.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings.

Response Webhook​

Optional

Nexla can automatically send the response received from the AppFigures API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and to capture returned IDs or status fields for downstream branching.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

    Enabling the response webhook is particularly useful for Create External Account (to capture the new account ID), and for any update operation where you need to confirm success and capture the updated resource state.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the AppFigures API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.

  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing​

After all endpoint settings have been configured, Nexla can send a test payload to the AppFigures API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the AppFigures API using the current settings.

Important

Test payloads sent to write endpoints (such as Create External Account, Update External Account, Update User Status, or Update a Product) will make real changes in your AppFigures account. Use a test or non-production AppFigures account before sending test data against a production account.

Save & Activate the Destination​

  • Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to AppFigures, open the destination resource menu, and select Activate.

    The Nexset data will not be sent to AppFigures until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.